Make ReshardingCoordinatorCommitMonitor account for replication lag on recipients

XMLWordPrintableJSON

    • Cluster Scalability
    • Fully Compatible
    • v8.1, v8.0
    • ClusterScalability Apr14-Apr28
    • None
    • 3
    • 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
            Reporter:
            Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: