<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic NMSDK &amp;amp; Python, bringing a filer to its knees in Software Development Kit (SDK) and API Discussions</title>
    <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/NMSDK-amp-Python-bringing-a-filer-to-its-knees/m-p/8133#M1023</link>
    <description>&lt;P&gt;We've been tracing down for weeks the cause of a serious performance decline of our filer. We have narrowed it down to a python script using the latest NMSDK.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Symptoms:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Sustained high CPU that persist after the NMSDK calls&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; - NFS RPC call take up to 20 times longer, affecting user experience&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; - we have no visibility of memory but a reboot alleviates the issue. So does a cluster takes over.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Method for reproduction:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Make a call for nfs-exportfs-modify-rule-2 using an NaElement previously retrieved via a call for nfs-exportfs-list-rules-2.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In order to modify the export ruleset, we retrieve a list with by calling nfs-exportfs-list-rules-2 and build upon it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Notes on reproduction:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Creating an nfs-exportfs-modify-rule-2 from scratch does not reproduce the issue, an NaElement from a previous nfs-exportfs-list-rules-2 needs to be used&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; - The new ruleset being applied with the nfs-exportfs-modify-rule-2 call needs to be different from the existing ruleset.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Code for reproduction: (see attached file)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; - edit netapp.py&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - update line 11 to point to a filer&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - update line 13 with the proper credentials&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; - launch ./test.py&lt;/P&gt;</description>
    <pubDate>Thu, 05 Jun 2025 06:37:48 GMT</pubDate>
    <dc:creator>BENJAMIN_SERVOZ</dc:creator>
    <dc:date>2025-06-05T06:37:48Z</dc:date>
    <item>
      <title>NMSDK &amp; Python, bringing a filer to its knees</title>
      <link>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/NMSDK-amp-Python-bringing-a-filer-to-its-knees/m-p/8133#M1023</link>
      <description>&lt;P&gt;We've been tracing down for weeks the cause of a serious performance decline of our filer. We have narrowed it down to a python script using the latest NMSDK.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Symptoms:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Sustained high CPU that persist after the NMSDK calls&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; - NFS RPC call take up to 20 times longer, affecting user experience&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; - we have no visibility of memory but a reboot alleviates the issue. So does a cluster takes over.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Method for reproduction:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; Make a call for nfs-exportfs-modify-rule-2 using an NaElement previously retrieved via a call for nfs-exportfs-list-rules-2.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;In order to modify the export ruleset, we retrieve a list with by calling nfs-exportfs-list-rules-2 and build upon it.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Notes on reproduction:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; - Creating an nfs-exportfs-modify-rule-2 from scratch does not reproduce the issue, an NaElement from a previous nfs-exportfs-list-rules-2 needs to be used&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; - The new ruleset being applied with the nfs-exportfs-modify-rule-2 call needs to be different from the existing ruleset.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Code for reproduction: (see attached file)&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; - edit netapp.py&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - update line 11 to point to a filer&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; - update line 13 with the proper credentials&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; - launch ./test.py&lt;/P&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:37:48 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Software-Development-Kit-SDK-and-API-Discussions/NMSDK-amp-Python-bringing-a-filer-to-its-knees/m-p/8133#M1023</guid>
      <dc:creator>BENJAMIN_SERVOZ</dc:creator>
      <dc:date>2025-06-05T06:37:48Z</dc:date>
    </item>
  </channel>
</rss>

