[SERVER-20399] MongoS may return exit code 48 (EXIT_NET_ERROR) during clean shutdown Created: 14/Sep/15  Updated: 07/Oct/15  Resolved: 15/Sep/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 3.1.9

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 0

 Description   

Whether there's a clean shutdown or not, the network listener thread will return and this is treated as a network error by the mongos main method.

So there is a race condition between the signal processing thread and the return from the main method as to which thread will call dbexit first. If the signal processing thread calls it first (which happens most of the time), it will result in zero return code. However, if the main method calls it first, this will return into exit code 48.



 Comments   
Comment by Githook User [ 15/Sep/15 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-20399 Do not return EXIT_NET_ERROR if inShutdown is set
Branch: master
https://github.com/mongodb/mongo/commit/06f9b374227f38c63d5073f7e0aee6071bdfb213

Generated at Thu Feb 08 03:54:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.