Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-103932

Make ReshardingCoordinatorCommitMonitor account for replication lag on recipients

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • Fully Compatible
    • v8.1, v8.0
    • ClusterScalability Apr14-Apr28
    • None
    • 0
    • None
    • None
    • None
    • None
    • None
    • None

      The remaining time estimate should account for the replication lag since transitioning to the "strict-consistency" state (or any state) requires waiting for the write to the recipient state doc to be majority committed.

            Assignee:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Reporter:
            cheahuychou.mao@mongodb.com Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: