I pulled this information from an older discussion.
I'd like to change the keepidle setting on my cluster but want to know what impact is required to change/set the value? Are node reboots required or services restart processes?
The current setting can be reviewed with the following command
isi_for_array -s 'sysctl net.inet.tcp.keepidle'
To set the value -- isi_sysctl_cluster net.inet.tcp.keepidle=300000 (5 minutes, value in milliseconds)
The next sysctl that would be of interest is the ping interval with is currently set at 75000 (75 Seconds). The cluster will send 8 pings at a 75 second interval resulting in a 5 minute window for the client to respond.
To view the setting -- isi_for_array -s 'sysctl net.inet.tcp.keepintvl'
Solved! Go to Solution.
What are you trying to accomplish with this tweak? Is there a specific behavior you are trying to get out of the cluster?
we made a fundamental networking change in our environment by adding in palo alto firewalls between the users and the isilon. The timeout values for traffic is 1 hour on the palo altos and 2 hours on the isilon and I believe it's causing us issues.
we want to drop the keepalive down to, say 30 minutes.