Thanks guys!
Yea I am going to do this on a test environment that simulates our
production environment. I was just looking for any potential gotchas, etc.
On Tue, May 27, 2014 at 6:42 PM, Robert Coli wrote:
> On Tue, May 27, 2014 at 1:24 PM, Robert Coli wrote:
>
>> On Tue, May 27, 2014 at 1
On Tue, May 27, 2014 at 1:24 PM, Robert Coli wrote:
> On Tue, May 27, 2014 at 10:57 AM, Eric Plowe wrote:
>
>> i have a cluster that is running 1.2.6. I'd like to upgrade that cluster
>> to 2.0.7
>>
>> Any suggestions/tips that would make the upgrade process smooth?
>>
>
> As indicated in NOTES.
I'd review the CHANGES.txt to see what has changed and the NEWS.txt to see
what you need to do before upgrading (config changes, data storage changes,
etc).
Generally:
- Determine what version you are upgrading to, and why
- Snapshot the data across all nodes
- Upgrade the nodes one at a time (ro
On Tue, May 27, 2014 at 10:57 AM, Eric Plowe wrote:
> i have a cluster that is running 1.2.6. I'd like to upgrade that cluster
> to 2.0.7
>
> Any suggestions/tips that would make the upgrade process smooth?
>
As indicated in NOTES.txt, upgrades to 2.0.x must pass through at least
(iirc?) 1.2.9.
I've written a bit about upgrading from 1.1 to 1.2, non-vnodes:
http://monkeys.chaordic.com.br/operation/zero-downtime-cassandra-upgrade/
Some tips may be valid for a more recent upgrade, but I'm sure the
community has more specific tips regarding the upgrade from 1.2 to 2.0.
On Tue, May 27, 2014
i have a cluster that is running 1.2.6. I'd like to upgrade that cluster to
2.0.7
Any suggestions/tips that would make the upgrade process smooth?
