tree 57cc256eb2cbde45c9fadf3aa8de16a92a4c241b
parent 8c62c47cb287ab25623505ed491a01d3b940f801
author Emeric Brun <ebrun@haproxy.com> 1442927106 +0200
committer Willy Tarreau <w@1wt.eu> 1442930847 +0200
encoding latin1

BUG/MEDIUM: peers: some table updates are randomly not pushed.

If an entry is still not present in the update tree, we could miss to schedule
for a push depending of an un-initialized value (upd.key remains un-initialized
for new sessions or isn't re-initalized for reused ones).

In the same way, if an entry is present in the tree, but its update's tick
is far in the past (> 2^31). We could consider it's still scheduled even if
it is not the case.

The fix consist to force the re-scheduling of an update if it was not present in
the updates tree or if the update is not in the scheduling window of every peers.