I meant to upgrade them one by one as fast as I can. The end result will be
that all nodes in the cluster are running 2.1.14.
Thanks for the feedback, guys.
On Fri, May 6, 2016 at 10:07 AM, Mark Dewey wrote:
> If by one-by-one you mean you want to upgrade one after the other doing a
> rolling re
If by one-by-one you mean you want to upgrade one after the other doing a
rolling restart of each node along the way, yes, that is doable and
recommended. C* guarantees interoperability between minor versions, ie
2.0.x and 2.1.x in this example. Check your changes.txt file for any
upgrade gotchas l
> When I'm reading code i look for comments to help me understand key
points,
> points that aren't self-evident. If we institute a boilerplate "comment
> everything" rule then I lose that signpost.
Frankly, I don't love the idea of somewhat limiting comments on purpose so
the
sheer presence of a c
Don't do that.
In any case an upgrade between 2.0.x and 2.1.x is not so complex and
difficult to do. And it is "downtime free". I would get the opportunity to
do a full cluster upgrade.
Regards,
Carlos Juzarte Rolo
Cassandra Consultant / Datastax Certified Architect / Cassandra MVP
Pythian - Lo
