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

syncSource diagnostics are incorrect

    • Type: Icon: Bug Bug
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 4.0.2
    • Component/s: None
    • Labels:
      None
    • Replication
    • ALL
    • Hide

      1. Start a 3 member replica set on 4.0.2 or later.
      2. Reconfigure replication to not allow chaining.
      3. Stepdown the Primary.
      4. Observe the syncSourceId for the node that doesn't step up.

      Show
      1. Start a 3 member replica set on 4.0.2 or later. 2. Reconfigure replication to not allow chaining. 3. Stepdown the Primary. 4. Observe the syncSourceId for the node that doesn't step up.

      In 4.0.1, the syncSourceId for a node identifies the member of the replica set the node is syncing from. Starting in 4.0.2, the syncSourceId for a node doesn't change unless the node is either stepping down or stepping up itself.

      Additionally, if chaining is disabled there is no logging explicitly stating the new sync source when there was in 4.0.1.

      4.0.1:

      2019-09-24T18:12:41.842-0400 I REPL     [replexec-2] Member localhost:27018 is now in state PRIMARY
      2019-09-24T18:12:42.335-0400 I REPL     [rsBackgroundSync] chaining not allowed, choosing primary as sync source candidate: localhost:27018
      

      4.0.2:

      2019-09-24T18:04:18.868-0400 I REPL     [replexec-0] Member localhost:27018 is now in state PRIMARY
      

            Assignee:
            backlog-server-repl [DO NOT USE] Backlog - Replication Team
            Reporter:
            daniel.hatcher@mongodb.com Danny Hatcher (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: