Setting Receive-buffer in Data Insight to Align with NetApp Filer Send-buffer on High Sustained Latency Relating to EAGAIN error
Description
In reference to EAGAIN errors caused by high sustained latency post ONTAP upgrade to 9.7 P14 or higher, NetApp recommends additional settings for the send-buffer.
NetApp has suggested that Data Insight also implement a configurable receive-buffer for Fpolicy server at both Device and Collector Level.
Post 6.3.1, Data Inight has implemented configurable settings for receive-buffer as follow.
Command to set receive buffer on the individual filer:
configdb -o -T filer -k <device_id> -J "vserver.sok.rcv.buf.sz" -j <buffer_value_in_bytes>
i.e. to set the receive buffer for device id 3 of size 6MB refer below command line
configdb -o -T filer -k 3 -J "vserver.sok.rcv.buf.sz" -j 6291456
Command to check what the value was set for previously
configdb -p -T objattr |findstr vserver.sok.rcv.buf.sz
Command to set receive buffer on the Collector Node:
configdb -o -T node -k <collector_node_id> -J "fpolicydcmod.tcp.lstn.rcv.buf.sz" -j <buffer_value_in_bytes>
i.e. to set the receive buffer on collector node 3 of size 6MB refer below command line
configdb -o -T node -k 3 -J "fpolicydcmod.tcp.lstn.rcv.buf.sz" -j 6291456
Command to check what the value was set for previously
configdb -p -T objattr |findstr fpolicydcmod.tcp.lstn.rcv.buf.sz
Related Articles
High sustained latency after ONTAP upgrade to 9.7 P14 and above due to FPolicy EAGAIN (veritas.com)
Related Knowledge Base Articles
Was this content helpful?
Translated Content
Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information.