Skip to main content
NetApp Knowledge Base

CONTAP-646150: Incorrect Buffer Accounting for Cross-Node S3 GET Responses

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

Issue

When native S3 GET requests access a bucket volume on a different node from the S3 data LIF, ONTAP incorrectly accounts for the response buffers as HTTP traffic rather than S3 traffic. This can make diagnostic buffer statistics misleading, including when HTTP access is disabled.
In an affected environment with slow or stalled S3 clients, response data accumulated in network buffers and the node restarted with the following message:
PANIC: Resource large_mbuf_flowcontrol had 100% stranded capacity for 720 seconds

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.