Keeping the business application running 24/7 is a priority, and going offline for a few minutes to a few hours during planned or unplanned software upgrade is not an acceptable option.
With Oracle NoSQL Database you can upgrade your NoSQL cluster in a rolling fashion. There is a smart administration utility that calculates the safest combination of storage nodes that can be brought down in parallel and upgraded, keeping all the shards in the database available for read/write operations at all the time.
For example if you have deployed 1x3 database cluster (i.e. 1 shards, with 3 replicas each shard) on three physical storage nodes and you want to find out what is the safest order to upgrade your cluster. Log on to the administration console and from the prompt run ‘show upgrade’ command, which will show you storage node IDs in multiple rows, for example:
kv-> show upgrade
Calculating upgrade order, target version: 18.104.22.168.8, prerequisite: 22.214.171.124.23
Storage nodes (SNs) that can all be upgraded in parallel will be represented in the same row and multiple rows represent the order in which upgrade should take place. There is also an example shell script that can be used to automate the whole process of upgrade.<KVROOT>/examples/upgrade/onlineUpgrade
Figure 1: Showing Storage Node 1 getting upgraded and all the shards in the cluster still available for read and write operation during the process.