[SERVER-44975] Make donor shard retry refreshing its filtering metadata until it succeeds before leaving the critical section Created: 06/Dec/19  Updated: 29/Oct/23  Resolved: 12/Dec/19

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

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

Backwards Compatibility: Fully Compatible
Sprint: Sharding 2019-12-16
Participants:

 Description   

In the 4.2 migration commit protocol, this simply makes the donor keep trying to refresh (while it is not shutting down), instead of giving up on refreshing and marking its filtering metadata as UNSHARDED.

In the 4.4 migration commit protocol, the results of this refresh will be guaranteed to reflect whether the migration commit succeeded or failed, making it possible for the donor to inform either itself or the recipient to go ahead and delete the orphaned range.



 Comments   
Comment by Githook User [ 12/Dec/19 ]

Author:

{'name': 'Esha Maharishi', 'email': 'esha.maharishi@mongodb.com', 'username': 'EshaMaharishi'}

Message: SERVER-44975 Make donor shard retry refreshing its filtering metadata until it succeeds before leaving the critical section
Branch: master
https://github.com/mongodb/mongo/commit/af51dce90f14ae0671e2151c85bff1590df40148

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