[SERVER-58992] Force a refresh of the filtering metadata on the recipient shard during the commit phase of a moveChunk Created: 01/Aug/21  Updated: 29/Oct/23  Resolved: 13/Oct/21

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

Type: Task Priority: Major - P3
Reporter: Sergi Mateo Bellido Assignee: Jordi Serra Torrens
Resolution: Fixed Votes: 0
Labels: PM-2423-milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-58991 Acquire the critical section on the r... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding EMEA 2021-08-09, Sharding EMEA 2021-08-23, Sharding EMEA 2021-09-06, Sharding EMEA 2021-09-20, Sharding EMEA 2021-10-04, Sharding EMEA 2021-10-18
Participants:

 Description   

This refresh must happen during the commit phase of the moveChunk. Note that after we refresh we would have to release the critical section.

We might want to add a new command since the same code will be executed both on the donor and recipient.

Note that it would be interesting to overlap both refreshes (AsyncRequestsSender?)



 Comments   
Comment by Jordi Serra Torrens [ 13/Oct/21 ]

Done as part of SERVER-58991

Comment by Sergi Mateo Bellido [ 01/Aug/21 ]

After this ticket we might want to try to enable the feature flag in the all-feature-flags variant.

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