Skip to main content
NetApp Knowledge Base

CONTAP-816141: Node panics with "Failover Monitor: unable to transit - takeover process is hung (wafl)" due to memory leak during object store command retries

  1. Last updated
  2. Save as PDF
Views:
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Issue


An ONTAP node may experience a panic after several weeks of uptime, reporting the following panic string:
{code:java}
PANIC: Failover Monitor: unable to transit - takeover process is hung (wafl) in SK process cf_main
{code}
Conditions for Exposure:
The system is configured to communicate with an object store FabricLink operations.
Object store requests that do not query the HTTP SERVER response header are retried following a closed socket connection from the object store server.
Systems with lower memory footprints are impacted sooner due to available memory constraints.

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.