tree 989c77855bd666f84d380cce17da1ec999f6df2c
parent 7b2ac29a92df037b1e15a0c02014892f46c83046
author Willy Tarreau <w@1wt.eu> 1628098513 +0200
committer Willy Tarreau <w@1wt.eu> 1628098861 +0200
encoding latin1

BUG/MINOR: server: update last_change on maint->ready transitions too

Nenad noticed that when leaving maintenance, the servers' last_change
field was not updated. This is visible in the Status column of the stats
page in front of the state, as the cumuled time spent in the current state
is wrong, it starts from the last transition (typically ready->maint). In
addition, the backend's state was not updated either, because the down
transition is performed by set_backend_down() which also emits a log, and
it is this function which was extended to update the backend's last_change,
but it's not called for down->up transitions so that was not done.

The most visible (and unpleasant) effect of this bug is that it affects
slowstart so such a server could immediately restart with a significant
load ratio.

This should likely be backported to all stable releases.