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

{replSetFreeze: 0} done in RollbackTest.restartNode() should be resilient of network errors

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.2.7, 4.4.0-rc6, 4.7.0
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.4, v4.2
    • Linked BF Score:
      19

      Description

      In RollbackTest.restartNode we try to freeze and unfreeze the current secondary to prevent elections from happening when we restart the primary. We use ReplSetTest.freeze to freeze which handles network errors (see SERVER-43237). But when we try to unfreeze, we use a vanilla adminCommand which does NOT handle network errors. However, if the current secondary is in rollback, the node would close all user connections so the this replSetFreeze command could fail with network errors for the same reasons as described in SERVER-43237. So I think we should also make the "unfreeze" part in RollbackTest.restartNode() resilient of network errors.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              lingzhi.deng Lingzhi Deng
              Reporter:
              lingzhi.deng Lingzhi Deng
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: