[SERVER-42838] A slow thread in forceShardFilteringMetadataRefresh can reset the shard's filtering metadata to UNSHARDED Created: 15/Aug/19  Updated: 30/Mar/23  Resolved: 30/Mar/23

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

Type: Task Priority: Major - P3
Reporter: Esha Maharishi (Inactive) Assignee: Sergi Mateo Bellido
Resolution: Duplicate Votes: 0
Labels: pm-1051-legacy-tickets, sharding-DDL-bugs, sharding-common-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-72322 The 'forceShardFilteringMetadataRefre... Open
is related to SERVER-64730 The 'forceShardFilteringMetadataRefre... Closed
Assigned Teams:
Sharding EMEA
Sprint: Sharding EMEA 2023-01-23, Sharding EMEA 2023-02-06, Sharding EMEA 2023-02-20, Sharding EMEA 2023-03-06, Sharding EMEA 2023-03-20, Sharding EMEA 2023-04-03
Participants:

 Description   

A shard refreshes its filtering metadata by first refreshing its CatalogCache, then using the fresh routing info from its CatalogCache to populate its filtering metadata.

There areĀ checks to ensure a shard does not overwrite newer routing info for a sharded collection with older routing info, but there is no such check (and there can't be by design) to prevent the shard from overwriting routing info for a sharded collection with unsharded routing info.


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