You are here: Installing NuoDB > Upgrading to a New Release > After You Upgrade > Tasks After Upgrading to Release 2.4

Tasks After Upgrading to Release 2.4

After upgrading to NuoDB 2.4, perform the following tasks:

Updating Default Templates

The built-in database templates shipped with NuoDB were updated in release 2.4 from version 4 to version 5. The changes in version 5 include:

When creating new databases these changes do not automatically take effect. To see the version for the built-in templates in your domain, you can you use the NuoDB Manager show templates command, for example:

nuodb [domain] > show templates
[ {

  "name" : "Multi Host",
  "version" : 4,
  "summary" : "This template starts up to two Storage Managers and as many 
		Transaction Engines as possible. Each host will have at most one SM and one 
		TE, so this template can be used with any number of hosts. A process will be 
		restarted on a new host if one goes offline and another is available.",
  "options" : {
    "commit" : "${COMMIT:remote:1}",
    "hostLimit" : "${HOST_LIMIT:false}"
  },
  "requirements" : [ {
...

To make version 5 of the built-in automation templates available, execute the NuoDB Manager update defaultTemplates command. See update defaultTemplates.

For databases that use the default setting of the backoff.reqMinUptime database option, execution of the update defaultTemplates command sets the value of the backoff.reqMinUptime option to 30000. This turns on the automation retry and backoff mechanism, which is the default starting with NuoDB 2.4. For databases that have a non-default setting for the backoff.reqMinUptime option, execution of update defaultTemplates does not change the setting of the backoff.reqMinUptime option.

A 2.3 database that used the default setting of the backoff.reqMinUptime option ran with the automation retry and backoff mechanism turned off. NuoDB recommends that a database always have this mechanism turned on. However, if you want to disable this mechanism, then after you run the NuoDB Manager update defaultTemplates command you need to set the database's backoff.reqMinUptime option to -1. You would need to execute this command for each database for which you want to disable the backoff mechanism. SeeUpdate Database . Also see Setting Up Automatic Restart of Processes

Updating the nuodb-rest-api.yml File

Installation of NuoDB 2.4 creates and loads the migrated-configuration.yml file. This file contains some updated settings as compared with the nuodb-rest-api.yml file that was provided with previous releases. Because installation does not overwrite the nuodb-rest-api.yml file from the previous release, you see a warning message such as the following in the REST service log:

WARN  [2015-12-03 10:45:42,548] com.nuodb.NuoDBRestService: Writing migrated drop-wizard settings file 
   to /path/to/migrated-configuration.yml

It is safe to ignore this message. You do not need to do anything.

However, in the following situations, you need to manually update the nuodb-rest-api.yml file:

To manually update the nuodb-rest-api.yml file:

  1. Copy migrated-configuration.yml to nuodb-rest-api.yml.
  2. Optionally, update nuodb-rest-api.yml with any non-NuoDB-specific settings.