Skip to main content
NetApp Knowledge Base

Does the FPolicy Send Buffer need increased due to EAGAIN in ONTAP 9.8 or higher?

Last Updated:

Applies to

  • ONTAP 9.8 or newer
  • FPolicy


No, in most cases

Additional Information

  • ONTAP 9.7 and older had a rewind on EAGAIN at a fixed 2 seconds
    • The 2 second window created a loop:
      • FPolicy server would have slowness send buffer would fill
      • I/O stayed in queue for 2 seconds each rewind and may take seconds or tens of seconds to process
      • The queue would never clear because of each 2 second rewind, even if the FPolicy server had a temporary performance problem
      • The only way this would stop is if I/O dropped to near zero periods or manual intervention to disable FPolicy
  • ONTAP 9.8's much smaller EAGAIN rewind window allows the queue to clear when the FPolicy server starts responding
  • The following conditions need to be met to consider increasing send buffer size:
    • Latency must be seen on volumes
    • The FPolicy vendor has seen performance is fine
    • The network between ONTAP and the FPolicy server is clean and responsive as determined in a packet trace
    • NetApp Support may recommend to increase outside of the above conditions in specific cases
    • If none of above are true, please follow the guidance in High sustained latency after ONTAP upgrade to 9.8 and above due to FPolicy EAGAIN
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.