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

Investigate changes in SERVER-17934: Do not report upstream progress while in state STARTUP2

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.4
    • Component/s: manual
    • # Replies:
      1
    • Last comment by Customer:
      true
    • Sprint:
      ServerDocs2020: Jun22-Jun26, ServerDocs2020: Jun29 - Jul2, ServerDocs2020: Jul7 - Jul10

      Description

      Description

      Downstream Change Summary

      Nodes in initial sync will not report replication progress upstream, which means that they will not participate in write majorities anymore. Even though their lastApplied and lastDurable will still advance, they won't project the real values for those in heartbeats, so other nodes won't know of their progress. They will also not send replSetUpdatePosition commands to their sync sources.

      Description of Linked Ticket

      Another way to look at this is that we should only report if we are secondary, and report when we become secondary in addition.

      Scope of changes

      Impact to Other Docs

      MVP (Work and Date)

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

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jeffrey.allen Jeffrey Allen
              Reporter:
              backlog-server-pm Backlog - DB Eng Program Management Team
              Participants:
              Last commenter:
              Jeffrey Allen
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                10 weeks, 5 days ago
                Date of 1st Reply: