tree 168af52e94186c4cad8664d575b95a92a8a3ce8c
parent bf5ace98c235b9fd57277aa5bd21c8c376455599
author David Pursehouse <dpursehouse@collab.net> 1505430267 +0900
committer Gerrit Code Review <noreply-gerritcodereview@google.com> 1505432167 +0000

Update git submodules

* Update plugins/replication from branch 'master'
  - Merge branch 'stable-2.14'
    
    * stable-2.14:
      Fix minor nits in documentation of replication.maxRetries
      Fix replication retries when maxRetries is set to 0
      Set max retries to avoid queue congestion
    
    Change-Id: I303d3b471bc98eaead33cfa49d614b176cf34f58
    
  - Merge branch 'stable-2.13' into stable-2.14
    
    * stable-2.13:
      Fix minor nits in documentation of replication.maxRetries
      Fix replication retries when maxRetries is set to 0
      Set max retries to avoid queue congestion
    
    Change-Id: Icf972f3df7d3d59925db670bc1f033028306d0c1
    
  - Fix minor nits in documentation of replication.maxRetries
    
    Change-Id: I80e46269e12b9e7a429634dd90ce52e90cc6ad79
    
  - Fix replication retries when maxRetries is set to 0
    
    maxRetries defaults to 0 which means retry indefinitely but it was not
    retrying.
    
    Change-Id: I6c8d8d6b1511d67b647f25193dcfe860687eea76
    
  - Set max retries to avoid queue congestion
    
    When servers have *a lot* of remote slaves, some of them
    unstable and potentially offline, a maximum retry policy is
    needed to prevent push events to stay in the replication queue
    and getting rescheduled forever.
    
    Keep backward-compatible configuration by setting maxRetry
    by default to zero, which means disabled.
    
    Change-Id: I060cc7bc3a4d1089b0815db02d2e1430f83a2015