tree 09dc469db92ca9ac70aaeb2cbaaa44b9623c833e
parent 180590409ffd34d4032f89839482ab098aae6f04
author Willy Tarreau <w@1wt.eu> 1548501541 +0100
committer Willy Tarreau <w@1wt.eu> 1548959905 +0100
encoding latin1

BUG/MINOR: server: fix logic flaw in idle connection list management

With variable connection limits, it's not possible to accurately determine
whether the mux is still in use by comparing usage and max to be equal due
to the fact that one determines the capacity and the other one takes care
of the context. This can cause some connections to be dropped before they
reach their stream ID limit.

It seems it could also cause some connections to be terminated with
streams still alive if the limit was reduced to match the newly computed
avail_streams() value, though this cannot yet happen with existing muxes.

Instead let's switch to usage reports and simply check whether connections
are both unused and available before adding them to the idle list.

This should be backported to 1.9.