In-Place Upgrades.  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.

Before beginning any upgrade, a backup should be taken as a best practice (Section 4.7, “Backup and Restore with Membase”)

Upgrade Steps

Manually Controlled Upgrade Options

By using environment variable flags, you may also optionally take more control of the upgrade steps. The available environment variables are:

Example flag usage:

Using mbupgrade manually

After using the INSTALL_DONT_AUTO_UPGRADE option, you can use the /opt/membase/bin/mbupgrade program later to fully control the upgrade steps.

It's command-line options include:

Usage: mbupgrade [-c path/to/previous/config/dir] [-a AUTO] [-d FILENAME] [-n] [-s FACTOR]

  -c <path/to/previous/config/dir>
       -- example: -c /etc/opt/membase/1.6.5.3.1

  -a <yes|no>
       -- automatic or non-interactive mode; default is 'no';
          'yes' to force automatic 'yes' answers to all questions

  -d <dbdir_output_file>
       -- retrieve db directory from config file and exit

  -n   -- dry-run; don't actually change anything

  -s <free_disk_space_needed_factor>
       -- free disk space needed, as a factor of current bucket usage
       -- default value is 2.0
       -- example: -s 1.0

Dry-run of mbupgrade

The mbupgrade program can be run using the -n flag, which tells mbupgrade to not modify any files, but just describe the changes it would make. An example dry-run output would be:

[root@Config126VM0 ~]# /opt/membase/bin/mbupgrade -c /etc/opt/membase/1.6.4 -n
Dry-run mode: no actual upgrade changes will be made.
Upgrading your Membase Server to basestar-352-gad964c0.
The upgrade process might take awhile.
Analysing...
Target node: ns_1@127.0.0.1

Membase should not be running.
  Please use: /etc/init.d/membase-server stop
Is the Membase server already stopped? [yes|no]
yes

Database dir: /var/opt/membase/1.6.4/data/ns_1
Is that the expected database directory to upgrade? [yes|no]
yes

Buckets to upgrade: default
Are those the expected buckets to upgrade? [yes|no]
yes

Checking disk space available for buckets in directory:
  /var/opt/membase/1.6.4/data/ns_1
  Free disk bucket space wanted: 98304.0
  Free disk bucket space available: 7306170368
  Free disk space factor: 2.0
  Ok.

Analysis complete.
Proceed with config & data upgrade steps? [yes|no]
yes

SKIPPED (dry-run): Copying /etc/opt/membase/1.6.4/ns_1/config.dat.rpmsave
SKIPPED (dry-run):     cp /etc/opt/membase/1.6.4/ns_1/config.dat.rpmsave /opt/membase/var/lib/membase/config/config.dat
Ensuring bucket data directories.
SKIPPED (dry-run): Ensuring bucket data directory: /var/opt/membase/1.6.4/data/ns_1/default-data
SKIPPED (dry-run):     mkdir -p /var/opt/membase/1.6.4/data/ns_1/default-data
SKIPPED (dry-run): Ensuring dbdir owner/group: /var/opt/membase/1.6.4/data/ns_1
SKIPPED (dry-run):     chown -R membase:membase /var/opt/membase/1.6.4/data/ns_1
Upgrading buckets.
SKIPPED (dry-run): Upgrading bucket: default
SKIPPED (dry-run):     /opt/membase/bin/mbdbupgrade /var/opt/membase/1.6.4/data/ns_1/default /var/opt/membase/1.6.4/data/ns_1/default-data
SKIPPED (dry-run): Ensuring bucket owner/group: /var/opt/membase/1.6.4/data/ns_1/default-data
SKIPPED (dry-run):     chown -R membase:membase /var/opt/membase/1.6.4/data/ns_1/default-data

Done.
[root@Config126VM0 ~]#

Useful commands