[SERVER-47982] Change the shard version update procedure of the migration source manager Created: 06/May/20  Updated: 29/Oct/23  Resolved: 17/Jun/20

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

Type: Task Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Marcos José Grillo Ramirez
Resolution: Fixed Votes: 0
Labels: PM-1645-Milestone-1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-47974 Introduce ScopedShardVersionCriticalS... Closed
depends on SERVER-47975 Optimize ScopedShardVersionCriticalSe... Closed
depends on SERVER-47985 Implement recovery of a shard's `shar... Closed
is depended on by SERVER-32198 Missing collection metadata on the sh... Closed
is depended on by SERVER-47987 Remove forceShardFilteringMetadataRef... Closed
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-05-18, Sharding 2020-06-01, Sharding 2020-06-15, Sharding 2020-06-29
Participants:

 Description   

As part of SERVER-47987 the way the cache is refreshed will be changed on a more optimized and safe way using a new scoped object. All this work will end on the removal of forceShardFilteringMetadataRefresh, which will make the local cache of a shard consistent with the config server. As part of this process the migration source manager needs to set the filtering metadata within the critical section, and should ensure:

1. If the operation fails, it must set the collection metadata to unknown, so the real shard version can be recovered lazily when needed.
2. There must not be any unnecessary refresh of the metadata after committing the new shard version, it should simply set the new shard version.
3. There must not be any recovery.



 Comments   
Comment by Githook User [ 17/Jun/20 ]

Author:

{'name': 'Marcos José Grillo Ramírez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-47982 Change the shard version update procedure of the migration source manager
Branch: master
https://github.com/mongodb/mongo/commit/1edd4798f8e72f226ad69269a8b0154b247a8049

Comment by Githook User [ 16/Jun/20 ]

Author:

{'name': 'Marcos José Grillo Ramírez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-47982 Remove refreshFilteringMetadataUntilSuccess from migration recovery
Branch: master
https://github.com/mongodb/mongo/commit/78c8c0b7bea617a336b5b4701f17e0107db3f78a

Comment by Githook User [ 28/May/20 ]

Author:

{'name': 'Marcos José Grillo Ramírez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: Revert "SERVER-47982 Fixed Windows compilation for Visual Studio 2019 version 16.6.0"

This reverts commit 02e3ec83c7e92adff03beda4def39bb33f1cd02d to prevent confusions with ticket id's.
Branch: master
https://github.com/mongodb/mongo/commit/f9f0b0b64d9b3166a5d45a52069101937a6a9795

Comment by Githook User [ 28/May/20 ]

Author:

{'name': 'Marcos José Grillo Ramírez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}

Message: SERVER-47982 Fixed Windows compilation for Visual Studio 2019 version 16.6.0
Branch: master
https://github.com/mongodb/mongo/commit/02e3ec83c7e92adff03beda4def39bb33f1cd02d

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