tree b05a3408c6ec89961ea0b723e024247c7b0e6be0
parent a22850a963faebee8458e162ca0466369483fa4f
author Saša Živkov <sasa.zivkov@sap.com> 1778840477 +0200
committer Saša Živkov <sasa.zivkov@sap.com> 1778850349 +0200

Add an option to drop pooled connection after a 503 response

We observe that sometimes Gerrit primary pods get a 503 response when
sending REST calls to each other. This happens when istio is used to
manage connections and one of the pods is either down or restarted. In
such cases, istio often continues to return 503 response even if the
target pod, and its IP address, is unavailable. The problem continues
until such a connection eventually expires and gets removed from the
connection pool. This often leads to missed or delayed messages between
the primary pods which leads to diverging indexes and inconsistent
caches.

This change adds a new option, http.reuseConnectionAfter503. When set to
false, a connection over which we receive a 503 response will be
immediately declared as non-reusable and will be removed from the
apache's http client connection pool.

Change-Id: I441c3ade9561e44a8841f346928d1273e38e39df