Re: Help with batch renaming legacy sstable files

Also, did you get to upgrade first to 1.1.x and and then to 1.2.x? That might smoothen the process. Hannu > On 26.6.2014, at 9.04, "Jens Rantil" wrote: > > Hi Todd, > > Maybe the "rename" command line utility could help you? > > Cheers, > Jens > — > Sent from Mailbox > > >> On Thu, Jun 26

Re: Help with batch renaming legacy sstable files

Hi Todd, Maybe the "rename" command line utility could help you? Cheers, Jens — Sent from Mailbox On Thu, Jun 26, 2014 at 6:50 AM, Todd Nine wrote: > Hey guys, > I'm working on migrating some data from 1.0.x clusters to a 1.2.16 > cluster. Part of my testing is (locally) loading the old

Help with batch renaming legacy sstable files

Hey guys, I'm working on migrating some data from 1.0.x clusters to a 1.2.16 cluster. Part of my testing is (locally) loading the old 1.0 sstables into my environment in 1.2.16. Since the 1.0 days, the file format has changes from this format. [Keyspace]-[CF name]-[table number]-Data.db To t

Re: EC2 cassandra cluster node address problem

It should be good to use broadcast_address for my purpose. The only problem is coming from opscenter now because it cannot recognize the datacenter from the ip range. On Wed, Jun 25, 2014 at 7:13 PM, Michael Shuler wrote: > On 06/25/2014 09:05 PM, Huiliang Zhang wrote: > >> Thanks. In 2.0.6, a

Re: EC2 cassandra cluster node address problem

On 06/25/2014 09:05 PM, Huiliang Zhang wrote: Thanks. In 2.0.6, a setting is like this: # Address to broadcast to other Cassandra nodes # Leaving this blank will set it to the same value as listen_address # broadcast_address: 1.2.3.4 If it is changing to elastic ip, it will cause other kinds of

Re: EC2 cassandra cluster node address problem

Thanks. In 2.0.6, a setting is like this: # Address to broadcast to other Cassandra nodes # Leaving this blank will set it to the same value as listen_address # broadcast_address: 1.2.3.4 If it is changing to elastic ip, it will cause other kinds of problem like Unknown Datacenter in opscenter.

Re: repair takes 10x more time in one DC compared to the other

Hmm.. good to find out, thanks for the reference! This explains the time differences between repairs in different DCs. But I think using -local and -pr should still be supported simultaneously, since you may want to repair nodes sequentially in the local DC (-local) without re-repairing ranges of

Re: EC2 cassandra cluster node address problem

On 06/25/2014 08:31 PM, Huiliang Zhang wrote: Thanks, get it. It is working after I translate the private ip to elastic ip. This sounds like a nice way to work around a known networking limitation when using EC2. Glad that worked out OK. In 2.1+, cassandra.yaml includes a broadcast_rpc_addres

Re: EC2 cassandra cluster node address problem

Thanks, get it. It is working after I translate the private ip to elastic ip. On Wed, Jun 25, 2014 at 1:51 PM, Andrey Ilinykh wrote: > yes, of course. Private ip is real ip address of node. Cassandra can > listen on this ip only. elastic ip is external. It belongs to AWS firewall. > It is simil

Re: EC2 cassandra cluster node address problem

yes, of course. Private ip is real ip address of node. Cassandra can listen on this ip only. elastic ip is external. It belongs to AWS firewall. It is similar to your web router. You can forward your external port to local one, but application running on your local node doesn't know anything about

Re: EC2 cassandra cluster node address problem

Thanks. In fact, it is Cassandra that returns private ip of nodes to my program by: client.describe_ring(keyspace) Then the program will start communicate with Cassandra through the private ips. One way is to translate the ips myself. On Tue, Jun 24, 2014 at 10:40 PM, Andrey Ilinykh wrote: >

Re: Does the default LIMIT applies to automatic paging?

Thank you all for your answers and clarification. The reason I mentioned the 1 rows LIMIT is not only because it is the default LIMIT in cqlsh, but also because I found it on the CQL document , specifically the "Spe

Re: Storing values of mixed types in a list

On Tue, Jun 24, 2014 at 11:49 PM, Tuukka Mustonen wrote: > Unfortunately, I need to query per list items. That's why I'm running > Cassandra 2.1rc1 (offers secondary indexes for collections). > As a general statement, if you have to use a just added feature in a pre-release version of the Datast

Re: repair takes 10x more time in one DC compared to the other

I see. Well, you shouldn't use both "-local" and "-pr" together, they don't make sense together. Which is the reason why their combination will be rejected in 2.0.9 (you can check https://issues.apache.org/jira/browse/CASSANDRA-7317 for details). Basically, the result of using both is that lots of

Re: repair takes 10x more time in one DC compared to the other

Thanks for the explanation, but I got slightly confused: >From my understanding, you just described the behavior of the -pr/--partitioner-range option: "Repair only the first range returned by the partitioner for the node." , so I would understand that repairs in the same CFs in different DCs with

Re: repair takes 10x more time in one DC compared to the other

TL;DR, this is not unexpected and this is perfectly fine. For every node, 'repair --local' will repair the "primary" (where primary means "the first range on the ring picked by the consistent hashing for this node given its token", nothing more) range of the node in the ring. And that range will b

repair takes 10x more time in one DC compared to the other

Hello, I'm running repair on a large CF with the "--local" flag in 2 different DCs. In one of the DCs the operation takes about 1 hour per node, while in the other it takes 10 hours per node. I would expect the times to differ, but not so much. The writes on that CF all come from the DC where it

Re: Storing values of mixed types in a list

Actually, come to think of it, of course I cannot run greater/less than queries on list items anyway (would be something like "WHERE items CONTAINS > 4"), so binary encoding should be fine. Thanks for everybody's input! Tuukka On Wed, Jun 25, 2014 at 1:49 PM, Tuukka Mustonen wrote: > Sorry for

Re: Storing values of mixed types in a list

Sorry for confusion, I should have lined my requirements better in the first place. Let me try to summarize: - I can use list and query against it using secondary indexes and by encoding my data on the client side. However, *this only allows exact matches, not greater/lesser than *for numbers at l

Re: Storing values of mixed types in a list

On Wed, Jun 25, 2014 at 8:49 AM, Tuukka Mustonen wrote: > Unfortunately, I need to query per list items. That's why I'm running > Cassandra 2.1rc1 (offers secondary indexes for collections). > Using a list of blobs does not in any way prevent you from doing that. Types are constraints on what va

Re: Does the default LIMIT applies to automatic paging?

On Tue, Jun 24, 2014 at 1:03 AM, ziju feng wrote: > > I was wondering if the default 1 rows LIMIT applies to automatic > pagination in C* 2.0 (I'm using Datastax driver). > There is no "1 rows LIMIT" in CQL. cqlsh does apply a default LIMIT if you don't provide for convenience sake, but