Skip to main content
NetApp Knowledge Base

Impact of Rebooting a CVO Mediator Node During AWS Planned Maintenance

Views:
11
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
ds_cvo
Last Updated:

Applies to

  • Cloud Volumes ONTAP
  • AWS Mediator

Answer

Cluster Functionality:

  • The cluster will continue to function but will operate in a degraded state until the mediator node is back online.
  • The mediator is primarily responsible for managing failover operations in HA configurations. If the mediator is unavailable, automatic failover between the nodes won't occur during the reboot period.

No Automatic Failover:

  • Without the mediator, in the event of a node failure, automatic failover between the HA nodes will not happen. This means manual intervention might be required to restore services if a node failure occurs during the reboot window.

Degraded State:

  •  While the mediator is offline, the HA pair operates in a degraded mode, which means the redundancy provided by the mediator is temporarily lost. However, the primary data-serving operations of the cluster should remain unaffected unless there is a simultaneous failure of one of the HA nodes.

Post-Reboot Checks:

  • After the reboot, check if the mediator is back online, validate its status, and confirm that the HA pair has returned to its normal operating state.

Additional Information

additionalInformation_text
NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.