Skip to main content
NetApp Knowledge Base

CONTAP-500025: ONTAP may panic with "Resource large_mbuf_flowcontrol had 100% stranded capacity" when ONTAP S3 clients are slow or unresponsive during connection shutdown

Views:
3
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
CORE
Last Updated:

Issue

In rare conditions, an ONTAP node serving S3 requests can panic when many client TCP connections stop making progress during connection shutdown. The affected connections can remain in the FIN_WAIT_1 state while retaining socket send-buffer resources, eventually causing resource exhaustion.
When this occurs, the node may panic with a message similar to:
PANIC: Resource large_mbuf_flowcontrol had 100% stranded capacity for 720 seconds
This has been observed when S3 clients become slow or unresponsive: they stop reading data, advertise zero receive windows, and fail to acknowledge connection shutdown after ONTAP initiates a normal TCP close. With a large number of such stalled connections, each holding buffered data in its send queue, network memory buffers (mbufs) accumulate until the large_mbuf_flowcontrol resource pool is exhausted and nodewatchdog triggers a panic.

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.