Hi Gerrit team,
We are currently running Gerrit 3.12.2-27-gcf7d13a276 in production and are testing an upgrade to Gerrit 3.13.8 in our DEV environment.
During testing, we are seeing repeated errors from one of the Gerrit pods:
org.apache.http.client.HttpResponseException: status code: 503, reason phrase: Query failed
From our investigation, this looks related to the high-availability plugin reusing pooled HTTP connections after a pod restart/IP change. We found what appears to be the relevant upstream fix here:
Add an option to drop pooled connection after a 503 response
However, this fix is currently on master. We cannot directly use the HA plugin JAR built from master, because it appears to be built against a newer Gerrit/JDK/API baseline and may not be compatible with Gerrit 3.13.8. We also checked newer stable branches, and this fix does not appear to be available in stable-3.13 or stable-3.14.
We tried using the latest GerritForge build for the `stable-3.13` HA plugin, but that did not resolve the issue. From what we could see, the GerritForge `stable-3.13` build does not include the above fix yet.
We also tried reproducing the same behaviour on our current production baseline, Gerrit 3.12.2-27-gcf7d13a276. In that version, the issue appears to recover automatically and does not keep repeating in the same way.
Could you please advise the recommended way to consume this fix for Gerrit 3.13.8?
Is there any plan to backport this fix to stable-3.13?
To reproduce/check the behaviour, we deleted the `gerrit-0` pod and monitored the logs from `gerrit-1`.
Command used :
kubectl logs gerrit-1 -n gerrit -c gerrit --timestamps | grep "status code: 503"
Output:
2026-08-07T11:30:03.409139460Z org.apache.http.client.HttpResponseException: status code: 503, reason phrase: Query failed
2026-08-07T11:31:10.681144356Z org.apache.http.client.HttpResponseException: status code: 503, reason phrase: Query failed
2026-08-07T11:32:07.560985372Z org.apache.http.client.HttpResponseException: status code: 503, reason phrase: Query failed
2026-08-07T11:33:03.401057859Z org.apache.http.client.HttpResponseException:
Hi Gerrit team,
We are currently running Gerrit 3.12.2-27-gcf7d13a276 in production and are testing an upgrade to Gerrit 3.13.8 in our DEV environment.
During testing, we are seeing repeated errors from one of the Gerrit pods:
org.apache.http.client.HttpResponseException: status code: 503, reason phrase: Query failed
From our investigation, this looks related to the high-availability plugin reusing pooled HTTP connections after a pod restart/IP change. We found what appears to be the relevant upstream fix here:
Add an option to drop pooled connection after a 503 response
However, this fix is currently on master. We cannot directly use the HA plugin JAR built from master, because it appears to be built against a newer Gerrit/JDK/API baseline and may not be compatible with Gerrit 3.13.8. We also checked newer stable branches, and this fix does not appear to be available in stable-3.13 or stable-3.14.
We tried using the latest GerritForge build for the `stable-3.13` HA plugin, but that did not resolve the issue. From what we could see, the GerritForge `stable-3.13` build does not include the above fix yet.
We also tried reproducing the same behaviour on our current production baseline, Gerrit 3.12.2-27-gcf7d13a276. In that version, the issue appears to recover automatically and does not keep repeating in the same way.
Could you please advise the recommended way to consume this fix for Gerrit 3.13.8?
Is there any plan to backport this fix to stable-3.13?
Hey Naveen,On Monday, 10 August 2026 at 10:59:52 UTC+1 NaveenKuma...@arm.com wrote:Hi Gerrit team,
We are currently running Gerrit 3.12.2-27-gcf7d13a276 in production and are testing an upgrade to Gerrit 3.13.8 in our DEV environment.
During testing, we are seeing repeated errors from one of the Gerrit pods:
org.apache.http.client.HttpResponseException: status code: 503, reason phrase: Query failed
From our investigation, this looks related to the high-availability plugin reusing pooled HTTP connections after a pod restart/IP change. We found what appears to be the relevant upstream fix here:
Add an option to drop pooled connection after a 503 response
However, this fix is currently on master. We cannot directly use the HA plugin JAR built from master, because it appears to be built against a newer Gerrit/JDK/API baseline and may not be compatible with Gerrit 3.13.8. We also checked newer stable branches, and this fix does not appear to be available in stable-3.13 or stable-3.14.
We tried using the latest GerritForge build for the `stable-3.13` HA plugin, but that did not resolve the issue. From what we could see, the GerritForge `stable-3.13` build does not include the above fix yet.
We also tried reproducing the same behaviour on our current production baseline, Gerrit 3.12.2-27-gcf7d13a276. In that version, the issue appears to recover automatically and does not keep repeating in the same way.
Could you please advise the recommended way to consume this fix for Gerrit 3.13.8?
Is there any plan to backport this fix to stable-3.13?
Feel free to create a cherry-pick to 3.13 and it can be reviewed when someone gets time.
To reproduce/check the behaviour, we deleted the `gerrit-0` pod and monitored the logs from `gerrit-1`.
Command used :
kubectl logs gerrit-1 -n gerrit -c gerrit --timestamps | grep "status code: 503"
Output:
2026-08-07T11:30:03.409139460Z org.apache.http.client.HttpResponseException: status code: 503, reason phrase: Query failed
2026-08-07T11:31:10.681144356Z org.apache.http.client.HttpResponseException: status code: 503, reason phrase: Query failed
2026-08-07T11:32:07.560985372Z org.apache.http.client.HttpResponseException: status code: 503, reason phrase: Query failed
2026-08-07T11:33:03.401057859Z org.apache.http.client.HttpResponseException:
--
--
To unsubscribe, email repo-discuss...@googlegroups.com
More info at http://groups.google.com/group/repo-discuss?hl=en
---
You received this message because you are subscribed to the Google Groups "Repo and Gerrit Discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to repo-discuss...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/repo-discuss/a8f014b7-3227-4456-821b-57e49a87cb9fn%40googlegroups.com.