Skip to main content
NetApp Knowledge Base

Elevated Write Latency in MetroCluster Triggered by NVDIMM Failure

Views:
9
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
hw
Last Updated:

Applies to

  • ONTAP 9
  • MetroCluster

Issue

  • A sudden spike in write latency was observed on the cluster during a period when a NVDIMM (Non-Volatile DIMM) was failing. The issue coincided with the following sequence of events:
    [node-01:cf_main:cf.fsm.takeover.panic:alert]: Failover monitor: takeover attempted after partner panic.
    [node-01:cf_takeover:cf.fm.takeoverComplete:notice]: Failover monitor: takeover completed
    [node-01:cf_main:cf.fsm.autoGivebackStarted:info]: Failover monitor: Automatic giveback started
    [node-01:cf_giveback:cf.fm.givebackComplete:notice]: Failover monitor: giveback completed
    [node-02:nphmd:hm.alert.cleared:notice]: AlertId=CriticalCECCCountMemErrAlert, AlertingResource=NVDIMM-11 cleared by monitor controller
  • Node-02 experienced a system panic due to degraded NVRAM, triggering automatic takeover by partner node (Node-01).
  • After the takeover, ONTAP performed an automatic giveback, returning aggregates to the affected node.
  • Post-giveback, Node-02 continued to operate with degraded NVRAM, resulting in elevated write latency across the MetroCluster.

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

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.