[SERVER-24878] do not exit with a non-zero code when shutting down a secondary Created: 01/Jul/16  Updated: 09/Aug/16  Resolved: 08/Jul/16

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.3.10

Type: Improvement Priority: Major - P3
Reporter: Eric Milkie Assignee: Eric Milkie
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: Repl 17 (07/15/16)
Participants:
Linked BF Score: 0

 Description   

Currently, even if a write returns InterruptedAtShutdown, we fassert on a secondary. This causes the backup_restore.js test to fail, under certain workloads.



 Comments   
Comment by Githook User [ 08/Jul/16 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-24878 capture InterruptedAtShutdown when replicating for all code paths
Branch: master
https://github.com/mongodb/mongo/commit/aac4bf95130a06a4711e4b0eb7ce23195c96b932

Comment by Githook User [ 01/Jul/16 ]

Author:

{u'username': u'milkie', u'name': u'Eric Milkie', u'email': u'milkie@10gen.com'}

Message: SERVER-24878 capture InterruptedAtShutdown when replicating, to avoid non-zero exit status
Branch: master
https://github.com/mongodb/mongo/commit/aca39983fa7a51cf5ec17d0ac386335210a8c0bf

Generated at Thu Feb 08 04:07:39 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.