[SERVER-37355] Make ShardRemote::_runExhaustiveCursorCommand interruptible when joining with the Fetcher Created: 27/Sep/18  Updated: 02/Nov/18  Resolved: 02/Nov/18

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

Type: Improvement Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: Kaloian Manassiev
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-35870 Temporarily release locks on replica ... Closed
related to SERVER-37329 Allow ShardRemote to be interrupted w... Closed
Sprint: Sharding 2018-10-22, Sharding 2018-11-05
Participants:

 Comments   
Comment by Kaloian Manassiev [ 02/Nov/18 ]

With the recent proposal for improved replication state transition concurrency control, this might be no longer needed. While making the usages of the Fetcher uninterruptible is a good idea generally, given that we want to go in the direction of using asynchronous networking we won't spend the effort of doing that, so I am closing this ticket as Won't Fix.

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