[SERVER-29619] Make ShardServerCatalogCacheLoader interruptible via OperationContext Created: 14/Jun/17  Updated: 30/Oct/23  Resolved: 30/Aug/17

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Nathan Myers
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-30014 Need OpCtxGroup, a OperationContext c... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2017-07-10, Sharding 2017-07-31
Participants:

 Description   

OperationContext objects must be stored in the ShardServerCatalogCacheLoader class so that they can be referenced.



 Comments   
Comment by Githook User [ 13/Jul/17 ]

Author:

{u'username': u'nathan-myers-mongo', u'name': u'Nathan Myers', u'email': u'nathan.myers@10gen.com'}

Message: SERVER-29619 Interrupt shard server catalog cache loader tasks on stepdown
Branch: master
https://github.com/mongodb/mongo/commit/98bb1900c5aa0c8f7ede0b9df201f9cd9b7c9da5

Comment by Nathan Myers [ 05/Jul/17 ]

New plan is for ShardServerCatalogCacheLoader to keep its own registry of contexts, and register a callback to kill them.

Comment by Kaloian Manassiev [ 30/Jun/17 ]

This approach sounds reasonable to me. You will have to thread that flag through the ServiceContext::makeOperationContext() call.

Comment by Nathan Myers [ 30/Jun/17 ]

Plan is to add a flag argument to the opctx constructor to indicate it should be interrupted when clients are interrupted, and make the catalog cache uses set the flag.

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