How wide rows are structured in CQL3

Hi, My impression from reading docs is that in old versions of Cassandra, you could create very wide rows, say with timestamps as column names for time series data, and read an ordered slice of the row. So, RowKeyColumns === == RowKey1 1:val1 2:val2 3:val3 N:valN With this da

Re: Both nodes own 100% of cluster

That makes sense, thanks. On Mon, Feb 18, 2013 at 2:26 PM, Hiller, Dean wrote: > Yes, for instance I have 6 nodes and have 50% ownership because I have > RF=3, and 6/3 = 2 virtual entities that are written to which means each > node owns 50%.

Re: Both nodes own 100% of cluster

m to has its token as the '0' start value? > At least that is what is said on the tutorials I've read. > > > On Mon, Feb 18, 2013 at 2:55 PM, Boris Solovyov > wrote: > >> What does the it mean that each node owns effective 100% of cluster? Both >&

Re: Nodetool doesn't shows two nodes

s, you spend 10+ hours troubleshooting cloud networking problems. > > On Mon, Feb 18, 2013 at 9:12 AM, Boris Solovyov > wrote: > > I think it is actually more of a problem that there were no error > messages > > or other indication of what went wrong in the setup where the

Re: Nodetool doesn't shows two nodes

-2 for > example) This is kind-of covered in the ticket here: > https://issues.apache.org/jira/browse/CASSANDRA-4026 I wish it could > be fixed properly. > > Good luck! > > > On 17 February 2013 16:16, Boris Solovyov > wrote: > > OK. I got it. I realized that storage_por

Re: Nodetool doesn't shows two nodes

OK. I got it. I realized that storage_port wasn't actually open between the nodes, because it is using the public IP. (I did find this information in the docs, after looking more... it is in section on "Types of snitches." It explains everything I found by try and error.) After opening this port 7

Re: Nodetool doesn't shows two nodes

13 at 4:48 PM, Boris Solovyov wrote: > Aha! I think I might have something breakthrough. I tried setting public > IP in listen_address (and therefore in broadcast_address, because as I > understand it inherits if it is commented out), and in seeds list. Node > fails to start, because Ca

Re: Is C* common nickname for Cassandra?

: > Why do you feel that link is unprofessional? Just wondering. I actually > quite like the abbreviation personally. > > On Feb 17, 2013, at 1:37 PM, "Boris Solovyov" > wrote: > > Thanks. I don't know if anyone cares my opinion, but as a newcomer to the > communit

Re: Is C* common nickname for Cassandra?

is short for Cassandra. > > > On Fri, Feb 8, 2013 at 10:43 AM, Boris Solovyov > wrote: > >> I see people refer to C* and I assume it mean Cassandra, but just wanted >> to check for sure. In case it is somethings else and I miss it :) Do I >> right understand? >

Re: Nodetool doesn't shows two nodes

and end up trying to connect to a private IP that Cassandra is not listening.) Thanks, - Boris On Wed, Feb 13, 2013 at 10:37 AM, Boris Solovyov wrote: > Thank you Alain. I will check the things you suggest and report my results. > > - Boris > > > On Wed, Feb 13, 2013 at 7:54 AM

Re: Seeking suggestions for a use case

Would you mind sharing your schema on the list? It would be useful to see how you modeled your data. Or you could email me privately if you want. Thanks Boris On Tue, Feb 12, 2013 at 4:11 PM, Hiller, Dean wrote: > Yes, the limit of the width of a row is approximately in the millions, > perhaps

Is C* common nickname for Cassandra?

I see people refer to C* and I assume it mean Cassandra, but just wanted to check for sure. In case it is somethings else and I miss it :) Do I right understand?