[SERVER-56206] Make the estimation of remaining time in resharding more robust Created: 20/Apr/21  Updated: 29/Oct/23  Resolved: 10/May/21

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 5.0.0-rc0

Type: Bug Priority: Major - P3
Reporter: Amirsaman Memaripour Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: PM-234-M3, PM-234-T-autocommits
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-56660 Remove need for reshardingCoordinator... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Sharding 2021-05-17
Participants:
Story Points: 1

 Description   

The resharding coordinator consumes the estimation of remaining operation time, reported by the recipients, to engage the critical section when recipients are about to finishing cloning and applying oplog entries.

However, the estimation does not consider the possibility of having no oplog entries to fetch/apply. When there are no oplog entries to fetch, the estimation algorithm assumes fetching/applying oplog entires will take as long as the duration of cloning from donors, and the estimated remaining time will never reach zero. This would prevent the coordinator from automatically engaging the critical section.

This ticket should improve the estimation algorithm (here) to account for the aforementioned situations.



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

Author:

{'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}

Message: SERVER-56206 Make the estimation of remaining time in resharding more robust
Branch: master
https://github.com/mongodb/mongo/commit/d2fbca2bbf1e878745abf58f68f066883d191e44

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