Before beginning any upgrade, a backup should be taken as a best practice (Section 4.7, “Backup and Restore with Membase”)
In-Place upgrades to 1.7.1, 188.8.131.52, or 1.7.2 are supported from all versions, but please note the version-specific information at the end.
Rolling upgrades to 184.108.40.206 are supported from 1.7.0 only.
It's important to ensure that your disk write queue (Monitoring your disk write queue) has been completely drained before shutting down the Membase Server service. This will ensure that all data has been persisted to disk and will be available after the upgrade. It is a best practice to turn off the application and allow the queue to drain prior to beginning the upgrade.
edition_and_arch _220.127.116.11 and copy it
to every node in your cluster.
Turn off your application, so that no requests are going to your Membase cluster.
Ensure that Disk Write Queue size reaches zero (all data has been persisted to disk).
Next, on each individual node (and this may be concurrent):
Backup each node's data using mbbackup
Backup each node's configuration files - While the upgrade script will perform a backup of the configuration and data files, it is our recommended best practice to take your own backup of the files located at:
If you have multiple version subdirectories in your /etc/opt/membase directory, you must first cleanup the directory so only the last, most recent version remains. This can happen if you've been regularly upgrading, such as from 1.6.5 to 18.104.22.168 to 22.214.171.124. In this case, move the /etc/opt/membase/1.6.5 and /etc/opt/membase/126.96.36.199 subdirectories to a different place. That is, only the /etc/opt/membase/188.8.131.52 subdirectory should remain when you "ls /etc/opt/membase".
Use platform specific upgrade commands to upgrade each node to 1.7.1, as root or using sudo:
Red Hat / CentOS:
rpm -U membase-server-
dpkg -i membase-server-
The previous upgrade command will stop membase, install 184.108.40.206, upgrade configuration files and data records, uninstall the previous version, and restart the membase server.
If your previous version was < 1.6.5 (such as 1.6.0, 1.6.1, 1.6.3), you will need to also run the following of manually creating a symbolic-link:
/etc/init.d/membase-server stop mkdir -p /opt/membase/1.6.1 ln -s /var/opt/membase/1.6.1/data /opt/membase/1.6.1/data /etc/init.d/membase-server start
This step is not applicable to Windows
After every node has been upgraded and restarted, and you can follow the steps below to monitor its progress of "warming up"
Turn your application back on.