yes, if i wait a second or two all is well. i didn't know about
"check_schema_agreement". is there a wiki page about using the new
keyspace management API? i don't see it on the Thrift API page.
i will apply the other patch you mentioned as well.
i think this is the same scenario,
https://issu
On second thought, that doesn't look like the problem at all.
Have you waited long enough for the schema to propagate? What does
check_schema_agreement tell you?
One thing to make sure about: you should funnel all your schema
updates through a single coordinator node or make sure that the
cluste
It looks like you're running into
https://issues.apache.org/jira/browse/CASSANDRA-1403, which was fixed
last week and will be included in beta2.
If you are experiencing this on trunk, please do file another ticket,
or comment on the existing one.
Gary.
On Mon, Aug 23, 2010 at 13:33, B. Todd Bur
i see the following in my server logs quite closely while doing a lot of
batch_mutations and reads. i create keyspaces and column families using
thrift api, not cassandra.yaml. did not migrate anything from 0.6.
4 node cluster, RF = 3, QUORUM read/write.
happens immediately on a fresh start of
