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.