Question on online upgrade with swap rebalance

[jens]

Continuing the discussion from CBlite local database size considerations on devices:

@heretyk

Still about scaling/sizing…but not about bandwith. If in a few months, i want to upgrade my 3 current nodes (2 vCPUs , 2 GB) to 3 nodes of another configuration (8vCPU, 32 GB, SSD drives).

Can i use the same method as described in your documentation : Online upgrade with swap rebalance ?
Couchbase SDKs

So basically add 1 of the new servers to my cluster, put all the data on it, remove the 3 olds nodes from the cluster, then add the 2 others “new” servers to the cluster.

If yes, can i do this if my 3 old servers are under Couchbase 3.0 and the new under 4.0 ?

Moving this to Couchbase Server forum where it’s more likely that someone who knows the answer will see it.

[heretyk]

@jens

Moving this to Couchbase Server forum where it’s more likely that someone who knows the answer will see it.

Thanks…great initiative

[daves]

I upgraded a 3.1 cluster to a 4.0 cluster using this method, and there was no issue with mixed version types whilst performing the rebalance.

I also tested the situation of running an upgrade on another cluster whilst it was running. That also worked - it just dropped the node for a few seconds whilst the upgrade happened. Not ideal when running in production, but it works if you need it to.

[heretyk]

@daves

I upgraded a 3.1 cluster to a 4.0 cluster using this method, and there was no issue with mixed version types whilst performing the rebalance.

I also tested the situation of running an upgrade on another cluster whilst it was running. That also worked - it just dropped the node for a few seconds whilst the upgrade happened. Not ideal when running in production, but it works if you need it to.

Okay thanks so actually, i can both upgrade my server’s hardware configuration and capabilities, at the same time i upgrade CouchBase…