The most common approach is node-by-node rebalance upgrade. Make sure you use Couchbase Server version 3.0.1. Also, it’s (of course) a good idea to have a backup from the 2.2 cluster with cbbackup before beginning.
You don’t state which client library you’re using. Depending on the version we may offer some specific advice, but the most common advice is to check the release notes for fixes in maintenance releases which could impact your deployment and if possible, update to the most recent within the dot-minor or major you’re using.
Thanks for that. We will be upgrading the client library in lockstep should we go down the upgrade path. To be perfectly frank adding and removing node in couchbase 2.2 has been a painful process for us and has resulted in us losing a large percentage of data 4 times out of 6 so I would rather stay away from rebalancing and swapping in nodes.
We can take downtime to mitigate the problem…If we take down time can we do this all without rebalancing?
Sorry to hear of the troubles. I know 2.5 addressed a lot of the rebalance issues but you shouldn’t have been losing data. In 2.2, there were scenarios where rebalance would fail, but it was re-startable.
If you’re bringing up same v2.2.0 online after offline upgrade to v3.0.1, rebalance isn’t required. I have seen a case where Admin Console UI reports “Rebalance required” after offline upgrade but it’s a false alarm and if you click on “Rebalance” button, it finishes in no time and no vbuckets are transferred. We will get it addressed.
Hi, I have a v2.2 community edition cluster using XDCR to sync data to an Elasticsearch cluster. I am wondering if I can do online upgrade to v3.x by swap rebalance method. It seems upgrading v2.2 to v3 is complicated when XDCR is in place. Is there any step-by-step guide for this? Or does anyone have experience on this?