Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-13600

Investigate changes in SERVER-45085: Check Config Replication condition on reconfig

      Description

      Downstream Change Summary

      Safe reconfig command will wait for the new config to propagate to a majority of nodes after installing the new config. This waiting behavior is subject to maxTimeMS.

      Description of Linked Ticket

      Config Replication condition checks the config C_i is replicated to a majority of data-bearing voting nodes in C_i in the primary’s term.

      Config Replication condition check in reconfig step 1 checks the config terms and version received via heartbeats in memberData. Waiting for _Config Replication in step 4 can either run Config Replication condition check with a ScatterGatherRunner in a loop or let replication coordinator signal it on receiving heartbeat responses.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

            Assignee:
            Unassigned Unassigned
            Reporter:
            backlog-server-pm Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:
              3 years, 49 weeks, 6 days ago