Skip to main content
NetApp Knowledge Base

CONTAP-281433: mgwd restart unexpectedly over time due to heap manager memory retention behavior

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

Issue

  • On clusters with sustained management API activity, the mgwd process may grow in virtual memory size over time until it exhausts its 4 GB virtual address limit, causing mgwd to crash and restart.

  • The following EMS messages appear as mgwd approaches the virtual memory limit:

kern.vm.mmap.return:notice: mmap(2) by mgwd (pid <pid>) for size <N> failed: VMEM limit exceeded, limit 4294967296, error 12.

  • mgwd may then crash with a message such as:

mgwd: Received SIGABRT (Signal 6) at RIP 0x... (pid <pid>, uid 0, timestamp <N>).

  • After the crash, mgwd is automatically restarted by spmd. The restart resolves the condition temporarily but virtual memory growth resumes. No data loss occurs. Depending on workload, the interval between restarts is typically weeks to months.

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.