[SERVER-45741] Migration coordination stepup task should not block on the network while waiting for replication Created: 24/Jan/20  Updated: 29/Oct/23  Resolved: 18/Feb/20

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

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Jack Mulrow
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-46075 Use asynchronous version of forceShar... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-02-24
Participants:

 Description   

Edited to only be about not blocking on the network while waiting for replication. The task should run on a separate executor (not the fixed executor) as part of SERVER-46075.

Original description:

It currently blocks on the network for:

  1. waiting for the last opTime to be majority committed
  2. sending _configsvrEnsureChunkVersionGreaterThan
  3. forcing a filtering metadata refresh

These sub-tasks should be made asynchronous.



 Comments   
Comment by Githook User [ 14/Feb/20 ]

Author:

{'username': 'jsmulrow', 'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com'}

Message: SERVER-45741 Use WaitForMajorityService in migration coordinator stepup task
Branch: master
https://github.com/mongodb/mongo/commit/0d083cfc66abb8804ca5b80c8b2cea534434099b

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