You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been trying to use asadm -e info output to monitor for HWM in a nagios check.
I've noticed that whenever asadm -e info is ran, it creates lots of TCP connections. The larger is the cluster, more TCP connections are used and put into TIME_WAIT afterwards. This creates an issue if the check is run every minute or so certain services not being able to create new tcp connections.
This is not really a bug (running checks less frequently solves the issue for me) but something that you might consider as an improvement.
The text was updated successfully, but these errors were encountered:
Output for asadm -e info and telnet command are different. asadm -e info command fetches lot of other stats and configs from all nodes. So it creates more connections. If you want to fetch specific information from specific server you can try asinfo tool.
Hey guys,
I've been trying to use
asadm -e info
output to monitor forHWM
in a nagios check.I've noticed that whenever
asadm -e info
is ran, it creates lots of TCP connections. The larger is the cluster, more TCP connections are used and put intoTIME_WAIT
afterwards. This creates an issue if the check is run every minute or so certain services not being able to create new tcp connections.This is not really a bug (running checks less frequently solves the issue for me) but something that you might consider as an improvement.
The text was updated successfully, but these errors were encountered: