Theory, based on the bug link above: requests coming in too fast might trigger this.
I think we could add some code to the worker to basically verify haproxy has restarted fully (PID file present?) before returning the Gearman response. Perhaps add a timeout, too.
Theory, based on the bug link above: requests coming in too fast might trigger this.
I think we could add some code to the worker to basically verify haproxy has restarted fully (PID file present?) before returning the Gearman response. Perhaps add a timeout, too.