Definitely knew that for major releases, didn't expect it for a minor release at all.
On Sat, May 4, 2013 at 5:41 AM, Philippe <firstname.lastname@example.org> wrote:
> After trying every possible combination of parameters, config and the rest,
> I ended up downgrading the new node from 1.1.11 to 1.1.2 to match the
> existing 3 nodes. And that solved the issue immediately : the schema was
> propagated and the node started handling reads & writes.
As you have discovered...
Trying to upgrade Cassandra by :
1) Adding new node at new version
2) Upgrading old nodes
Is far less likely to work than :
1) Add new node at old version
2) Upgrade all nodes