[SERVER-32198] Missing collection metadata on the shard implies both UNSHARDED and "metadata not loaded yet" Created: 06/Dec/17 Updated: 30/Oct/23 Resolved: 30/Jun/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.4.10, 3.6.0, 4.0.4 |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Fixed | Votes: | 4 |
| Labels: | PM-1645-Milestone-1, ShardingRoughEdges | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Assigned Teams: |
Sharding
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | Sharding 2018-01-01, Sharding 2017-12-18, Sharding 2018-02-12, Sharding 2018-02-26, Sharding 2018-06-18, Sharding 2018-07-02, Sharding 2018-07-16, Sharding 2018-07-30, Sharding 2018-08-13, Sharding 2018-08-27, Sharding 2018-09-10 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
This ticket was created as an overflow of If after a migration commit on the config server, a donor shard fails to refresh its metadata, we clear the MetadataManager's metadata. We do this so that the next time the metadata is needed, a refresh will be triggered. However, if a request comes in with an UNSHARDED shardVersion, it will see empty metadata and the request will be allowed to go through without triggering a refresh. The linked |
| Comments |
| Comment by Githook User [ 08/Feb/22 ] |
|
Author: {'name': 'Allison Easton', 'email': 'allison.easton@mongodb.com', 'username': 'allisoneaston'}Message: |
| Comment by Kaloian Manassiev [ 30/Jun/20 ] |
|
This work has completed as a result of the commits made to this ticket and all the completed dependencies, which constitute Milestone 1 of PM-1645. |
| Comment by Githook User [ 26/Feb/20 ] |
|
Author: {'name': 'Kaloian Manassiev', 'username': 'kaloianm', 'email': 'kaloian.manassiev@mongodb.com'}Message: o getCurrentMetadataIfKnown - which returns the current filtering metadata if any is available This is in preparation for making getMetadataForOperation/getCurrentMetadata throw StaleShardVersion exception if the metadata has not been loaded yet. This is a partial cherry-pick from dcf7e0dd89d34f58b592f1adb3d41e5edd6e2012, adapted for the 4.0 branch. |
| Comment by Githook User [ 26/Feb/20 ] |
|
Author: {'name': 'Kaloian Manassiev', 'username': 'kaloianm', 'email': 'kaloian.manassiev@mongodb.com'}Message: This is partial cherry-pick of the changes done under 20117b8ee9678794be675eb4d728bfcc8f9d75f4 to make the 4.0 logic match that of 4.2. |
| Comment by Githook User [ 29/Jan/20 ] |
|
Author: {'name': 'Kaloian Manassiev', 'username': 'kaloianm', 'email': 'kaloian.manassiev@mongodb.com'}Message: Revert " This reverts commit e4e052a10484cf2cc44c62c377db4ece8162820a. |
| Comment by Githook User [ 29/Jan/20 ] |
|
Author: {'name': 'Kaloian Manassiev', 'username': 'kaloianm', 'email': 'kaloian.manassiev@mongodb.com'}Message: Revert " This reverts commit a414e4ceafb45dc6ebf4daeb9198f0a7f3fb189c. |
| Comment by Githook User [ 25/Jan/20 ] |
|
Author: {'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm', 'name': 'Kaloian Manassiev'}Message: o getCurrentMetadataIfKnown - which returns the current filtering This is in preparation for making This is a partial cherry-pick from dcf7e0dd89d34f58b592f1adb3d41e5edd6e2012, adapted for the 4.0 branch. |
| Comment by Githook User [ 24/Jan/20 ] |
|
Author: {'username': 'kaloianm', 'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com'}Message: This is partial cherry-pick of the changes done under 20117b8ee9678794be675eb4d728bfcc8f9d75f4 to make the 4.0 logic match that of 4.2. |
| Comment by Githook User [ 14/Nov/18 ] |
|
Warning: Do not backport the commit seen below without also including a bugfix from Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: o getCurrentMetadataIfKnown - which returns the current filtering This is in preparation for making |
| Comment by Githook User [ 19/Sep/18 ] |
|
Author: {'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}Message: (cherry picked from commit 80de0da37b00dbeed576b28a842cb172b6714358)
(cherry picked from commit 2aa65a86193e5d38934a4f2d6b0a8298e2432485)
(cherry picked from commit 60559a00b81293184922b3418a8e56610edf8dd9)
(cherry picked from commit c9c340ad6e9e1f33cb001a8375c62d6b16138c74)
(cherry picked from commit ca04f5bcf9bfa73c9162b3a77225c997c6deec8a)
(cherry picked from commit db1cc80d13d203b6351f5510f7756cc1c7bfc0ea)
(cherry picked from commit 884d232473dca72e0872f0e540d4c3108c1e0b3d)
(cherry picked from commit d91262c4a2ed7d94923c3b1c5ff5d208aa981c73)
(cherry picked from commit e491e284e8066929c8272c96a3128241ab481be8)
Expose the ShardingState properties and move the appendInfo logic to be (cherry picked from commit 24e411d5cd7f64c5b4da25a351529cd1873284b8)
(cherry picked from commit 7a97557ce5bf74dc2b663762b7a5ffb9c958d580)
... and move it into a ShardingInitializationMongoD class, which is Also gets rid of the 'sharding' library, so there is no more library (cherry picked from commit 200c3dc58410d8b3287a2075cc9b2ad085100e83)
... and also remove dependency of MongoS on the replication coordinator (cherry picked from commit fab6864f4edcae7bb304f79e601f1f62cc376a77) |
| Comment by Githook User [ 12/Sep/18 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: |
| Comment by Githook User [ 11/Sep/18 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: |
| Comment by Githook User [ 27/Jun/18 ] |
|
Author: {'username': 'kaloianm', 'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Githook User [ 12/Jun/18 ] |
|
Author: {'username': 'kaloianm', 'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Githook User [ 07/Jun/18 ] |
|
Author: {'username': 'kaloianm', 'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Githook User [ 24/May/18 ] |
|
Author: {'username': 'kaloianm', 'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com'}Message: |
| Comment by Githook User [ 26/Apr/18 ] |
|
Author: {'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm', 'name': 'Kaloian Manassiev'}Message: This avoids having to cast them to NamespaceString for passing to |
| Comment by Githook User [ 09/Mar/18 ] |
|
Author: {'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}Message: This allows the logic for making the shard version decision to be |
| Comment by Nicholas Zolnierz [ 13/Dec/17 ] |
|
Note that this comment refers to the previous ticket number, but should be updated by this ticket. |