Menu

#56 Race condition triggered by broadcast on multiple IPs

Annoyance
open
8
2004-03-12
2004-03-12
No

This is hilarious...

Suppose, I'm on box A that is resolving as 127.0.0.1,
192.168.1.1, and 192.168.2.1. If I specify more than
one bind address in the provider , the consumer ends up
receiving broadcasts for the same set of devices from
different sources (as currently implemented), which
triggers a swap of a listener to a new one in a rapid
succession. This causes listeners to drop connections,
which, in turn, causes DAC to accumulate dead
connection handlers because they don't actively check
the connection status and allow it to linger for quite
a while (bug #603786).

Fix: implement a unique provider signature and
recognize multiple IP aliases of the same provider.

Discussion


Log in to post a comment.

MongoDB Logo MongoDB