cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Renato Bacelar da Silveira <>
Subject Re: Cassandra-cli not able to find CF after fresh CF insert.
Date Fri, 26 Aug 2011 07:13:42 GMT
Thank you kindly Aaron.

It seems that if I insert a fresh CF, the Cassandra-cli is not "aware" 
of the change, though it does
describe the CF fine, when the command "describe keyspace MyKeySpace;" 
is issued.

The error, at least on my side, is reproduced by adding a CF with 
Hector, and having the CLI running
at the same time. As mentioned, the CLI is able to describe the CF, but 
if I list it, it isn't visible.

I have taken your advice before creating a ticket, to restarting the 
CLI, that seems to work. But
I was not yet convinced, so I kept the CLI open, and inserted another 
CF, the issue repeats itself.

In the state of not listing the CF after the last insert, I decided to 
issue the "connect localhost/9160;"
command, that seems to make the CLI aware of the column again, and the 
list command does not fail.

So 2 things will help here

a) Restart the CLI, (works till another fresh column insert)
b) Issue the connect <host>/<port>; command, then use the KeySpace in 
question (works fine even after fresh insert).

Not sure if there should be a ticket created.

What you think?

Regards to All!

On 25/08/2011 23:50, aaron morton wrote:
> What about if you do a get ? What happens if you re-start the 
> cassandra-cli ?
> If you can reproduce the fault with a cli script please create a jira 
> ticket here
> Thanks
> -----------------
> Aaron Morton
> Freelance Cassandra Developer
> @aaronmorton
> On 25/08/2011, at 4:13 AM, Renato Bacelar da Silveira wrote:
>> Hi All
>> Good day,
>> I have again come across a situation where the CF is not being found 
>> by the list command... it would
>> be too painful at this stage to restart the node just to be able to 
>> query the CF...
>> *ColumnFamily: a1307*
>>       Key Validation Class: org.apache.cassandra.db.marshal.BytesType
>>       Default column value validator: 
>> org.apache.cassandra.db.marshal.BytesType
>>       Columns sorted by: org.apache.cassandra.db.marshal.AsciiType
>>       Row cache size / save period in seconds: 0.0/0
>>       Key cache size / save period in seconds: 200000.0/14400
>>       Memtable thresholds: 0.5203125/111/1440 (millions of 
>> ops/MB/minutes)
>>       GC grace seconds: 864000
>>       Compaction min/max thresholds: 4/32
>>       Read repair chance: 1.0
>>       Replicate on write: true
>>       Built indexes: []
>> [default@MyKeyspace] list a1307;
>> *a1307 not found in current keyspace.*
>> I am not sure how this is being caused, but if I add a CF and list it
>> immediately after, it does not find the CF.
>> I had to change my CF names to have a char in it, because I suspect 
>> CF names
>> may not be integer only, not yet proven on that though.
>> I am using Cassandra 0.8.* ---
>> Any ideas?
>> -- 


View raw message