Not sure this will be useful for you but "nodetool drain" doesn't work properly well for a while. If you are using counters I recommend you to remove commit logs after you drained ans stopped the node, before restarting the node to avoid replaying counts.
https://issues.apache.org/jira/browse/CASSANDRA-4446 Hope this will help, Alain 2013/2/11 Michal Michalski <mich...@opera.com> > > 2) Upgrade one node at a time, running the clustered in a mixed >> 1.1.2->1.1.9 configuration for a number of days. >> > > I'm about to upgrade my 1.1.0 cluster and > http://www.datastax.com/docs/**1.1/install/upgrading#info<http://www.datastax.com/docs/1.1/install/upgrading#info>says: > > "If you are upgrading to Cassandra 1.1.9 from a version earlier than > 1.1.7, all nodes must be upgraded before any streaming can take place. > Until you upgrade all nodes, you cannot add version 1.1.7 nodes or later to > a 1.1.7 or earlier cluster." > > Which one is correct then? Can I run mixed 1.1.2 (in my case 1.1.0) & > 1.1.9 cluster or not? > > M. >
