[SERVER-50209] ShardRegistry internal reload is not interruptible Created: 10/Aug/20  Updated: 29/Oct/23  Resolved: 28/May/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 4.4.0
Fix Version/s: 4.4.7

Type: Bug Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: sharding-wfbf-day
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-46202 Implement ShardRegistry on top of Rea... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:
Linked BF Score: 20

 Description   

The ShardRegistry periodically schedules an internal reload on its own dedicated executor. However, this reload is not interruptible in any way, even though shut down of the ShardRegistry will join on it.

Given that this internal reload has no operation deadline, it can get stuck for various reasons, which in turn will block the shutdown sequence.

As part of this ticket, we should make ShardRegistry keep track of its internal reloads (possibly through an OperationContextGroup) so that it can be interrupted on shutdown.



 Comments   
Comment by Githook User [ 28/May/21 ]

Author:

{'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-50209 Allow interruption of shard registry refresh thread when shutting down
Branch: v4.4
https://github.com/mongodb/mongo/commit/98af1d93241d11ba5e8f748968a298b5b900a8b6

Comment by Kevin Pulo [ 10/Aug/20 ]

Note that this is being incidentally fixed in master branch by SERVER-46202, so only needs to be directly fixed in the v4.4 branch.

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