Hi,
I recently have been seeing issues in a large environment where the
listen backlog of ovsdb-server, both NB and SB, is getting over-flowed,
for example:
17842 times the listen queue of a socket overflowed
17842 SYNs to LISTEN sockets dropped
There is more on NB than SB, but I was surprised to see any. I can only
guess at the moment it is happening when the leader changes and hundreds
of nodes try and reconnect.
Looking at their sockets I can see the backlog is only set to 10:
$ ss -ltm | grep 664
LISTEN 0 10 0.0.0.0:6641 0.0.0.0:*
LISTEN 0 10 0.0.0.0:6642 0.0.0.0:*
Digging into the code, there is only two places where listen() is
called, one being inet_open_passive():
/* Listen. */
if (style == SOCK_STREAM && listen(fd, 10) < 0) {
error = sock_errno();
VLOG_ERR("%s: listen: %s", target, sock_strerror(error));
goto error;
}
There is no way to config around this to even test if increasing would
help in a running environment.
So my question is two-fold:
1) Should this be increased? 128, 256, 1024? I can send a patch.
2) Should this be configurable?
Has anyone else seen this?
Thanks for any thoughts.
-Brian
_______________________________________________
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
