Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
0.21.0
-
None
-
None
-
Twitter Mesos Q4 Sprint 4
-
2
Description
We observed that in our production environment with network monitoring being turned on.
If there are many connections (> 10^4) in a container, getting socket information is expensive. It might take 1min to process all the socket information.
One of the reason is that the library we are using (libnl) is not so optimized. Cong Wang has already submitted a patch:
http://lists.infradead.org/pipermail/libnl/2014-November/001715.html