tree d515b8d58ea82f6aafb677d624758a373088311c
parent 21259e7e8430794cc369ede98ca94b1f0c09493d
author Thomas Dräbing <thomas.draebing@sap.com> 1713265390 +0200
committer Thomas Dräbing <thomas.draebing@sap.com> 1713792743 +0000

Retry on lock failure during change update

Gerrit did not retry if posting a review failed with a lock failure
thrown by the global refdb implementation. Thus, in case the lock in
the global refdb could not be acquired, the ref-update was aborted
after the first try. This could lead to a lot of failed updates like
reviews, affecting especially users on very active repositories.

An ExceptionHook has been added that will cause Gerrit to retry,
if a GlobalRefDbLockException is being thrown. This ExceptionHook
has to be bound by every plugin that wants to make use of the
Global RefDB.

Bug: Issue 334278785
Change-Id: I3518ba9187761f8475233867ed8a3212713c9079