tree 8f53345837398e175b201728578d7fcface2090d
parent 65a5517c7e6e70f0658765b3d3b73b36dd2f3ea1
author Matthias Sohn <matthias.sohn@sap.com> 1711702119 +0100
committer Gerrit Code Review <noreply-gerritcodereview@google.com> 1711702119 +0000

Update git submodules

* Update plugins/replication from branch 'master'
  to cc47d53d4870e2c285c3b72202ebe6f3fdd67b57
  - Destination#pushWasCanceled: minimize time spent in critical section
    
    When cancelling a push to a replication destination don't notify
    listeners about not attempted push during the critical section where the
    stateLock is held but do this immediately after the critical section.
    
    We observed in a high-availability setup with 2 primaries that
    cancelling a replication push blocked >90 other threads trying to
    update some refs which tried to create new replication tasks via
    synchronous events. Cancelling the push was stuck on visibility checks
    done in EventBroker#fireEvent triggered by Destination#pushWasCanceled.
    This visibility check was slow since the affected repository is huge
    (30GiB) and we use NFS for sharing repositories between primaries.
    
    Moving the call to PushOne#notifyNotAttempted outside the critical
    section should reduce the impact of this critical section on other
    requests updating refs concurrently.
    
    Change-Id: I085700c3f4cad95ef62521527ac4b920a59c76c2
    Signed-off-by: Matthias Sohn <matthias.sohn@sap.com>