Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

asadm -e info creating too many tcp connections #39

Closed
Entea opened this issue Oct 11, 2017 · 3 comments
Closed

asadm -e info creating too many tcp connections #39

Entea opened this issue Oct 11, 2017 · 3 comments

Comments

@Entea
Copy link

Entea commented Oct 11, 2017

Hey guys,

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.

@Entea
Copy link
Author

Entea commented Oct 18, 2017

Okay, the proper way to do it is:

telnet localhost 3003
namespace/<name_of_your_namespace

Closing the issue :)

@Entea Entea closed this as completed Oct 18, 2017
@hbpatre
Copy link
Contributor

hbpatre commented Oct 18, 2017

Entea,

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.

@Entea
Copy link
Author

Entea commented Oct 18, 2017

Thanks for explanation @hbpatre!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants