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

CSRS member fails to be killed on 4.4.0-rc3

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Gone away
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Replication
    • Labels:
      None
    • Operating System:
      ALL
    • Sprint:
      Sharding 2020-05-18

      Description

      Running a sharded cluster on 4.4.0-rc3. I killed all 3 CSRS members by running a kill <pid> command. The first and third members were successfully shut down, but the second member was not able to shut down. My random guess at the most relevant error is here:

      {"t":{"$date":"2020-04-28T14:26:47.203+00:00"},"s":"W", "c":"STORAGE", "id":20561,  "ctx":"SignalHandler","msg":"Error stepping down in non-command initiated shutdown path","attr":{"error":{"code":189,"codeName":"PrimarySteppedDown","errmsg":"While waiting for secondaries to catch up before stepping down, this node decided to step down for other reasons"}}}
      

      Attaching the full logs. "member2_9008" is the process that failed to be killed.

      Note – this doesn't happen every time, but I can reliably trigger again.

      Spoke to Judah Schvimer and he recommended filing a bug directly.

        Attachments

        1. member1_9007.log
          26.63 MB
        2. member2_9008.log
          14.21 MB
        3. member3_9009.log
          1.15 MB

          Activity

            People

            Assignee:
            janna.golden Janna Golden
            Reporter:
            louisa.berger Louisa Berger
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: