Alain,We performed a 1.1.3 -> 1.1.6 upgrade and found that all the logs replayed regardless of the drain. After noticing this on the first node, we did the following:* nodetool flush* nodetool drain* service cassandra stop* mv /path/to/logs/*.log /backup/* apt-get install cassandra<restarts automatically>I also agree that starting C* after an upgrade/install seems quite broken if it was already stopped before the install. However annoying, I have found this to be the default for most Ubuntu daemon packages.MikeOn Thu, Nov 15, 2012 at 9:21 AM, Alain RODRIGUEZ <firstname.lastname@example.org> wrote:
We had an issue with counters over-counting even using the nodetool drain command before upgrading...Here is my bash history69 cp /etc/cassandra/cassandra.yaml /etc/cassandra/cassandra.yaml.bak70 cp /etc/cassandra/cassandra-env.sh /etc/cassandra/cassandra-env.sh.bak71 sudo apt-get install cassandra72 nodetool disablethrift73 nodetool drain74 service cassandra stop75 cat /etc/cassandra/cassandra-env.sh /etc/cassandra/cassandra-env.sh.bak76 vim /etc/cassandra/cassandra-env.sh77 cat /etc/cassandra/cassandra.yaml /etc/cassandra/cassandra.yaml.bak78 vim /etc/cassandra/cassandra.yaml79 service cassandra startSo I think I followed these steps http://www.datastax.com/docs/1.1/install/upgrading#upgrade-stepsI merged my conf files with an external tool so consider I merged my conf files on steps 76 and 78.I saw that the "sudo apt-get install cassandra" stop the server and restart it automatically. So it updated without draining and restart before I had the time to reconfigure the conf files. Is this "normal" ? Is there a way to avoid it ?So for the second node I decided to try to stop C*before the upgrade.125 cp /etc/cassandra/cassandra.yaml /etc/cassandra/cassandra.yaml.bak126 cp /etc/cassandra/cassandra-env.sh /etc/cassandra/cassandra-env.sh.bak127 nodetool disablegossip128 nodetool disablethrift129 nodetool drain130 service cassandra stop131 sudo apt-get install cassandra//131 : This restarted cassandra132 nodetool disablethrift133 nodetool disablegossip134 nodetool drain135 service cassandra stop136 cat /etc/cassandra/cassandra-env.sh /etc/cassandra/cassandra-env.sh.bak137 cim /etc/cassandra/cassandra-env.sh138 vim /etc/cassandra/cassandra-env.sh139 cat /etc/cassandra/cassandra.yaml /etc/cassandra/cassandra.yaml.bak140 vim /etc/cassandra/cassandra.yaml141 service cassandra startAfter both of these updates I saw my current counters increase without any reason.Did I do anything wrong ?Alain--
Mike Heffner <email@example.com>Librato, Inc.