Db Upgrade

Database upgrade configuration includes cluster-wide policies that affect default database upgrades.

Edit upgrade configuration

To edit database upgrade configuration using the Cluster Manager UI:

1. On the Databases screen, select {{< image filename="/images/rs/buttons/button-toggle-actions-vertical.png#no-click" alt="Toggle actions button" width="22px" class="inline" >}} to open a list of additional actions.

2. Select Upgrade configuration.

3. Change database upgrade configuration settings.

4. Select Save.

Upgrade configuration settings {#upgrade-config-settings}

Database shard parallel upgrade

To change the number of shards upgraded in parallel during database upgrades, use one of the following methods:

• Cluster Manager UI – Edit Database shard parallel upgrade in Upgrade configuration

• [rladmin tune cluster]({{< relref "/operate/rs/7.8/references/cli-utilities/rladmin/tune#tune-cluster" >}}):

  shCopy

  rladmin tune cluster parallel_shards_upgrade { all | <integer> }
  

• [Update cluster policy]({{< relref "/operate/rs/7.8/references/rest-api/requests/cluster/policy#put-cluster-policy" >}}) REST API request:

  shCopy

  PUT /v1/cluster/policy 
  { "parallel_shards_upgrade": <integer> }
  

RESP3 support

The cluster-wide option resp3_default determines the default value of the resp3 option, which enables or deactivates RESP3 for a database, upon upgrading a database to version 7.2 or later. resp3_default is set to enabled by default.

To change resp3_default to disabled, use one of the following methods:

• Cluster Manager UI – Edit RESP3 support in Upgrade configuration

• [rladmin tune cluster]({{< relref "/operate/rs/7.8/references/cli-utilities/rladmin/tune#tune-cluster" >}}):

  shCopy

  rladmin tune cluster resp3_default { enabled | disabled }
  

• [Update cluster policy]({{< relref "/operate/rs/7.8/references/rest-api/requests/cluster/policy#put-cluster-policy" >}}) REST API request:

  shCopy

  PUT /v1/cluster/policy 
  { "resp3_default": <boolean> }