[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: |
|
||||||||||||
| 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. |