-
Notifications
You must be signed in to change notification settings - Fork 19
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
High number of active flow counts in load balancer #26
Comments
From Amazon:
So a flow is a unique source IP/port and destination IP/port. Being that UPD is a connectionless protocol, I'm probably not setting the source port. My guess is that's not consistent. Have you used |
Hi Jack, Application to statsrelay traffic 06:07:01.810427 IP 127.0.0.1.37912 > 127.0.0.1.8125: UDP statsrelay to NLB traffic 06:07:35.781796 IP 10.0.X.X.56544 > 10.0.Y.Y.8125: UDP As you said the source port is not set. How can we solve this? |
Find the https://golang.org/pkg/net/#ListenUDP The last parameter there is I'd be glad to accept that patch. |
Hello Jack, I have made some changes in the similar lines and running this awesome tool in production. See if you like the idea. |
I am running statsrelay as repeater daemon in my application boxes(ec2 m4.large) and forwarding the udp packets to group of boxes listening behind aws network load balancer(udp). This is opening around 50K connection flows in the NLB. The count of metrics published by the application boxes is around 10K/second. What is the reason behind opening such a high number of flows?
The text was updated successfully, but these errors were encountered: