Thanks for pointing that out.
Given upgradesstables can only be run on a live node, does anyone know
if there is a danger of having this node in the cluster while this is
being performed? Also, can anyone confirm this only needs to be done on
counter counter column families, or all column families (the former
makes sense, I'm just making sure).
-Mike
On 1/16/2013 11:08 AM, Jason Wee wrote:
always check NEWS.txt for instance for cassandra 1.1.3 you need to
run nodetool upgradesstables if your cf has counter.
On Wed, Jan 16, 2013 at 11:58 PM, Mike <mthero...@yahoo.com
<mailto:mthero...@yahoo.com>> wrote:
Hello,
We are looking to upgrade our Cassandra cluster from 1.1.2 ->
1.1.8 (or possibly 1.1.9 depending on timing). It is my
understanding that rolling upgrades of Cassandra is supported, so
as we upgrade our cluster, we can do so one node at a time without
experiencing downtime.
Has anyone had any gotchas recently that I should be aware of
before performing this upgrade?
In order to upgrade, is the only thing that needs to change are
the JAR files? Can everything remain as-is?
Thanks,
-Mike
