tree 16dc025342cdc2fef1531226fc367747d1c91125
parent ca8185c2f6301fa5b79b656b4279da4dcb7386a1
author Luca Milanesio <luca.milanesio@gmail.com> 1563493655 +0000
committer Gerrit Code Review <noreply-gerritcodereview@google.com> 1563493655 +0000

Update git submodules

* Update plugins/replication from branch 'stable-2.15'
  to 3b1b656d09eb2dd73f94f50772bbeb39d167b540
  - Revert "Remove replication event from pending when runway is allowed"
    
    This reverts commit e780ae61cbbba3f88558a3620065d1fcdc0768c8.
    
    Reason for revert: Creates potentially infinite Heap consumption and
    JVM crash when a PushOp is denied to use the runway.
    
    The problem is caused by the late removal of the PushOp from the
    list of pending operations, which causes the subsequent reschedule
    to find the same operation and double the number of replication states
    associated with it. If the loop happens multiple times, the generated
    consumption grows exponentially causing the JVM to enter a series
    of continuous stop-the-world GC that eventually lead to complete
    block of the JVM activity.
    
    The method `requestRunway` is thus not telling the truth because
    it is actually relying on the fact that the PushOne operation is
    removed also from the pending list, independently from its runway
    concession status.
    
    Change-Id: I6097bc7ad16c8bcc86a7d30af7d2ad331728712d