OPERATIONAL DEFECT DATABASE
...
...
The shutdown task for mongos doesn't consider exceptions that may occur before the initialization of global objects (and decorations). For example, LogicalSessionCache is accessed from here on v4.0.28, while it is initialized from here and any error that may occur before this point will cause a segmentation fault during shutdown. This ticket should identify any resource that is accessed by the shutdown task but may not be ready/initialized during shutdown. The shutdown task must ensure each resource is valid before accessing it. AC: Investigate if this behavior exists on 4.2/4.4/5.0/6.0, if it does re-triage, if not, close.
jason.chan commented on Mon, 13 Jun 2022 18:53:47 +0000: For this ticket, I think we should investigate whether this issue exists on any version later than 4.0 (considering v4.0 is EOL'd). amirsaman.memaripour@mongodb.com confirmed the problem is not reproducible on master.
Reproducing the issue is quite easy: start a mongos using an already in-use listening port. The issue is reliably reproducible using v4.0.28.
Click on a version to see all relevant bugs
MongoDB Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
