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

Failed election leaves recipient in unusable state

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • None
    • ALL
    • Server Serverless 2022-06-13, Server Serverless 2022-06-27

    Description

      See build failure logs here

      Look for these specific lines:

      [j5:rs10:n2] | 2022-05-22T01:21:24.036+00:00 I  COMMAND  21581   [conn44] "Received replSetStepUp request"
      [j5:rs10:n2] | 2022-05-22T01:21:24.036+00:00 D4 ELECTION 4615650 [conn44] "Rescheduled election timeout callback","attr":{"when":{"$date":"2022-05-23T03:20:58.441Z"},"requestedWhen":{"$date":"2022-05-23T01:21:24.036Z"},"error":{"code":0,"codeName":"OK"}}
      [j5:rs10:n2] | 2022-05-22T01:21:24.036+00:00 I  ELECTION 4615657 [conn44] "Not starting an election for a replSetStepUp request, since we are not electable","attr":{"reason":"Not standing for election because I cannot see a majority (mask 0x1)"}
      [j5:rs10:n2] | 2022-05-22T01:21:24.036+00:00 I  COMMAND  21582   [conn44] "replSetStepUp request failed","attr":{"error":" :: caused by :: CommandFailed: Election failed."}
      

      When the logs reach that line, all recipient nodes are marked as SECONDARY, and subsequent attempts to clear the sync source, and find a new one seem to fail. Eventually the test times out waiting for a recipient primary

      Attachments

        Activity

          People

            didier.nadeau@mongodb.com Didier Nadeau
            matt.broadstone@mongodb.com Matt Broadstone
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: