In the linked AF ticket, the node was applying oplog entries as part of replication recovery as a standalone. There was a concurrent shutdown triggered by a SIGTERM and then the node crashed since shutdown kills all operations including the main startup thread that is doing recovery.

We should handle this case more gracefully, for example early exit the recovery procedure if shutdown is detected, but there might be some thinking needed to do that correctly w.r.t to the startup sequence.