It's fixed in the cassandra-0.7 branch (no 0.7.x release, yet) and 0.8-beta2.  You can also use ntp to sync the clocks in your cluster and the problem won't happen again.

On Thu, May 5, 2011 at 3:47 AM, Dikang Gu <dikang85@gmail.com> wrote:
Is this fixed in cassandra-0.7.5 or cassandra-0.8 ?

On Thu, May 5, 2011 at 1:43 PM, Tyler Hobbs <tyler@datastax.com> wrote:
The issue is quite possibly this: https://issues.apache.org/jira/browse/CASSANDRA-2536

A person on the ticket commented that decomissioning and rejoining the node with the disagreeing shema solved the issue.


On Thu, May 5, 2011 at 12:40 AM, Dikang Gu <dikang85@gmail.com> wrote:
I got this exception when I was trying to create a new columnFamily using hector api. 

me.prettyprint.hector.api.exceptions.HInvalidRequestException: InvalidRequestException(why:Cluster schema does not yet agree)

What does this mean and how to resolve this?

I have 3 nodes in the cassandra 0.7.4 cluster.

Thanks.

--
Dikang Gu

0086 - 18611140205




--
Tyler Hobbs
Software Engineer, DataStax
Maintainer of the pycassa Cassandra Python client library




--
Dikang Gu

0086 - 18611140205




--
Tyler Hobbs
Software Engineer, DataStax
Maintainer of the pycassa Cassandra Python client library