2.0 to 4.0 directly isn't supported You will need to upgrade to either 2.5.2 or 3.1.3 and then upgrade to 4.1.
I would recommend upgrading to 3.1.3 first. Note that 2.x to 3.x does have a protocol change and will lead to a cluster wide rebalance once all the nodes in the cluster are at the 3.x version after which TAP will stop being used and DCP will start to be used. - Dipti > On Feb 11, 2016, at 8:30 PM, JZ <[email protected]> wrote: > > We have a couchbase cluster running version 2.0. Now we want to upgrade to > 4.0. > > The upgrade matrix does not say there is a path from 2.0 to 4.0. > > Can we still use the swap balancing approach to directly upgrade to 4.0? > > Or should we first upgrade to 3.0 then to 4.0? > > Thanks for the advice. > -- > You received this message because you are subscribed to the Google Groups > "Couchbase" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Couchbase" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
