Unfortunately there are changes to the inter-node protocol which which make it impossible to run a mixed cluster.
The TTL feature is one of the things that mean you also have to upgrade the client. The Columns returned and accepted by Cassandra will now expect to have a TTL field.
AFAIK in theory Thrift is designed to handle these sorts of changes, but I do not know if thats how things have turned out in the real world. If you want to test a 0.6 client against a 0.7 server, first disable the thrift_framed_transport_size_in_mb setting as 0.6 did not use framed transport http://wiki.apache.org/cassandra/StorageConfiguration?highlight=(framed)
Let me know if you can working. Obviously it should be a temporary solution and others will have a better understanding of the implications of running a 0.6 client against 0.7
Hope that helps.
Aaron
On 20 Jan, 2011,at 01:55 AM, Daniel Josefsson <jid...@gmail.com> wrote:
Hi,
I've been looking around for how to upgrade from 0.6 to 0.7, and it looks like you need to shut down the whole cluster, plus upgrade the clients at the same time.
Our live cassandra instances are currently running 0.6.4 with an ever growing database and need the new TTL feature available in 0.7. For client we use Pelops
Has anyone done a similar upgrade of a live cluster? How did you go about?
Is there at least a way to avoid having to upgrade both server side and client side simultaneously?
Thanks,
Daniel
