[SERVER-34363] addShard shard registry reload can cause mongos to terminate Created: 06/Apr/18  Updated: 29/Oct/23  Resolved: 17/Apr/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.7.3
Fix Version/s: 3.6.6, 3.7.5

Type: Bug Priority: Major - P3
Reporter: Randolph Tan Assignee: Misha Tyulenev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v3.6
Sprint: Sharding 2018-04-23
Participants:
Linked BF Score: 37

 Description   

ShardRegistry::reload is called inside ON_BLOCK_EXIT in the addShard command. The reload method can throw and when it does, it will terminate the server because ON_BLOCK_EXIT has throw() and calls safeExecute.



 Comments   
Comment by Githook User [ 01/Jun/18 ]

Author:

{'username': 'mikety', 'name': 'Misha Tyulenev', 'email': 'misha@mongodb.com'}

Message: SERVER-34363: move reload shard registry in addShard command from ON_BLOCK_EXIT

(cherry picked from commit 730a60e529046946f737955feba98ee4412a0c4d)
Branch: v3.6
https://github.com/mongodb/mongo/commit/8e14403f4799b2538d82b072522e6e0c6c575b44

Comment by Githook User [ 17/Apr/18 ]

Author:

{'name': 'Misha Tyulenev', 'email': 'misha@mongodb.com', 'username': 'mikety'}

Message: SERVER-34363: move reload shard registry in addShard command from ON_BLOCK_EXIT
Branch: master
https://github.com/mongodb/mongo/commit/730a60e529046946f737955feba98ee4412a0c4d

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