How your system is affected during the upgrade

You must understand how your StorageGRID system will be affected during the upgrade.

Client applications might experience short-term disruptions

The StorageGRID system can ingest and retrieve data from client applications throughout the upgrade process except for a short period of time when services are restarting and the client connections to individual Gateway Nodes or Storage Nodes are disrupted. Connectivity will be restored after the upgrade finishes and services resume on the individual nodes.

Every node in your StorageGRID system will be brought down one at a time for several minutes each during the upgrade. You might need to schedule downtime for the upgrade if loss of connectivity for a short period is not acceptable.

You must decide when to upgrade Gateway Nodes based on your grid's configuration. If your StorageGRID system has multiple Gateway Nodes, you must sequence the upgrade so that client applications are always directed to an available Gateway Node. If your StorageGRID system has only one Gateway Node, you must plan a downtime for the upgrade because client applications will not be able to access the system while the Gateway Node is being upgraded.

Alarms might be triggered

Alarms might be triggered when services start and stop and when the StorageGRID system is operating as a mixed-version environment (some grid nodes running an earlier version, while others have been upgraded to a later version). In general, these alarms will clear when the upgrade completes.

Many emails are generated

When you upgrade grid nodes, email notifications are generated when the node is stopped and restarted. To avoid excessive emails, you can disable email notifications before upgrading the first node and re-enable notifications after the upgrade is completed.

Configuration changes are restricted

While you are upgrading StorageGRID:
  • Do not make any grid configuration changes until the upgrade is complete.
  • Do not change the audit level configuration until the upgrade is complete.
  • Do not enable or disable any new features until the upgrade is complete.
  • Do not update the ILM configuration until the upgrade is complete. Otherwise, you might experience inconsistent and unexpected ILM behavior.

Metadata reserved space increases on larger-capacity Storage Nodes

During upgrade, the metadata reserved space for Storage Nodes that have 128 GB or more of RAM is automatically increased from 3 TB to 4 TB, unless the Metadata Reserved Space (CAWM) setting has been changed from its default value of 3 TB (3000000000000). If you have changed the value of Metadata Reserved Space, or if the Storage Node was installed when the default value for Metadata Reserved Space was different than 3 TB, the amount of space that is reserved for metadata on volume 0 is not changed during upgrade.

To see the current setting for Metadata Reserved Space (CAWM), go to Configuration > Storage Options > Overview. Note that because CAWM is a system-wide setting, its value does not change after the upgrade to reflect the new 4 TB metadata reservation for larger Storage Nodes.

To see the impact of the increased amount of metadata reserved space on larger Storage Nodes, select Nodes > Storage Node > Storage and look at the graph of Storage Used - Object Metadata. The value of the Metadata Used Space (Percent) attribute, or CDLP, decreases after a larger Storage Node is upgraded, due to the increased space reservation.

Changes to open firewall ports

During the upgrade, open firewall ports are reset to the default set.