System RestartΒΆ

A kernel upgrade on a Coordinating Node requires a system restart. Restarting a CN requires that the environment is placed in read-only mode to help avoid content inconsistency between the CNs operating within an Environment. Restarting the Primary CN in an Environment requires that the Environment DNS be switched to another CN so the read only service (resolution, retrieval, and search) remain available to clients. The DNS switch is required in the production environment and is optional in the various test environments.

../_images/d51a5afc94907895e5c7348027351717e93228696e33fddd844bd522439f3865.svg

Figure 1. Typical setup of Coordinating Nodes in an environment. When restarting CN-1 it is necessary to change the Environment DNS to point to one of the other nodes so that operations such resolve and external applications (e.g. Search UI) continue to function.

Procedure

  1. Broadcast notification

  2. Set read-only mode

  3. Update non-primary nodes (Indexing CN and Third CN), avoiding an update of DataONE packages:

    #optional hold on DataONE packages
sudo apt-mark hold dataone*
sudo apt-get update
sudo apt-get dist-upgrade
#when ready, restart the server
sudo reboot

    #undo hold on DataONE packages
sudo apt-mark unhold dataone*
# verify new kernel running
uname -r

  4. Switch DNS to a non-primary node. For example, switch the environment DNS entry to point to the Indexing CN.

  5. Update the remaining node. As for #4.

  6. Switch DNS back to the original primary node.

  7. Leave read-only mode

  8. Broadcast notification