tree 126224fc10f2d4dcfa4f5c42917d644b2a40ea88
parent d7c2673d3ffb5c8c7c994a3ee385997237ed0d99
author Maxim Dounin <mdounin@mdounin.ru> 1316110378 +0000
committer Maxim Dounin <mdounin@mdounin.ru> 1316110378 +0000

Workaround for cpu hog on errors with cached connections.

Just doing another connect isn't safe as peer.get() may expect peer.tries
to be strictly positive (this is the case e.g. with round robin with multiple
upstream servers).  Increment peer.tries to at least avoid cpu hog in
round robin balancer (with the patch alert will be seen instead).

This is not enough to fully address the problem though, hence TODO.  We
should be able to inform balancer that the error wasn't considered fatal
and it may make sense to retry the same peer.