Re: Issues with CQLSH in Cassandra 1.2

2013-02-02 Thread Manu Zhang
On Tue 29 Jan 2013 03:55:52 AM CST, aaron morton wrote: I was able to replicate it… $ bin/nodetool -h 127.0.0.1 -p 7100 describering foo Schema Version:253da4a3-e277-35b5-8d04-dbeeb3c9508e TokenRange: TokenRange(start_token:3074457345618258602, end_token:-9223372036854775808,

Re: Issues with CQLSH in Cassandra 1.2

2013-02-02 Thread Gabriel Ciuloaica
Right, at that point either, cassandra-cli or cqlsh will not see any endpoint. Only after you drop the keyspace and re-create it with cassandra-cli will properly work. Thanks, Gabi On 2/3/13 2:15 AM, Manu Zhang wrote: On Tue 29 Jan 2013 03:55:52 AM CST, aaron morton wrote: I was able to

Re: Issues with CQLSH in Cassandra 1.2

2013-01-28 Thread aaron morton
I was able to replicate it… $ bin/nodetool -h 127.0.0.1 -p 7100 describering foo Schema Version:253da4a3-e277-35b5-8d04-dbeeb3c9508e TokenRange: TokenRange(start_token:3074457345618258602, end_token:-9223372036854775808, endpoints:[], rpc_endpoints:[], endpoint_details:[])

Issues with CQLSH in Cassandra 1.2

2013-01-24 Thread Gabriel Ciuloaica
Hi, I have spent half of the day today trying to make a new Cassandra cluster to work. I have setup a single data center cluster, using NetworkTopologyStrategy, DC1:3. I'm using latest version of Astyanax client to connect. After many hours of debug, I found out that the problem may be in

Re: Issues with CQLSH in Cassandra 1.2

2013-01-24 Thread Ivan Velykorodnyy
Hi, Astyanax is not 1.2 compatible yet https://github.com/Netflix/astyanax/issues/191 https://github.com/Netflix/astyanax/issues/191Eran planned to make it in 1.57.x четверг, 24 января 2013 г. пользователь Gabriel Ciuloaica писал: Hi, I have spent half of the day today trying to make a new

Re: Issues with CQLSH in Cassandra 1.2

2013-01-24 Thread Gabriel Ciuloaica
I do not think that it has anything to do with Astyanax, but after I have recreated the keyspace with cassandra-cli, everything is working fine. Also, I have mention below that not even nodetool describering foo, did not showed correct information for the tokens, encoding_details, if the

Re: Issues with CQLSH in Cassandra 1.2

2013-01-24 Thread Tyler Hobbs
Gabriel, It looks like you used DC1 for the datacenter name in your replication strategy options, while the actual datacenter name was DC-1 (based on the nodetool status output). Perhaps that was causing the problem? On Thu, Jan 24, 2013 at 1:57 PM, Gabriel Ciuloaica gciuloa...@gmail.comwrote:

Re: Issues with CQLSH in Cassandra 1.2

2013-01-24 Thread Gabriel Ciuloaica
Hi Tyler, No, it was just a typo in the email, I changed names of DC in the email after copy/paste from output of the tools. It is quite easy to reproduce (assuming you have a correct configuration for NetworkTopologyStrategy, with vNodes(default, 256)): 1. launch cqlsh and create the

Re: Issues with CQLSH in Cassandra 1.2

2013-01-24 Thread aaron morton
Can you provide details of the snitch configuration and the number of nodes you have? Cheers - Aaron Morton Freelance Cassandra Developer New Zealand @aaronmorton http://www.thelastpickle.com On 25/01/2013, at 9:39 AM, Gabriel Ciuloaica gciuloa...@gmail.com wrote: Hi Tyler,

Re: Issues with CQLSH in Cassandra 1.2

2013-01-24 Thread Gabriel Ciuloaica
Hi Aaron, I'm using PropertyFileSnitch, an my cassandra-topology.propertis looks like this: /# Cassandra Node IP=Data Center:Rack// // //# default for unknown nodes// //default=DC1:RAC1// // //# all known nodes// // 10.11.1.108=DC1:RAC1// // 10.11.1.109=DC1:RAC2// // 10.11.1.200=DC1:RAC3