[SERVER-47243] Add the "Replicating the orphan filtering table" section to the sharding arch guide Created: 01/Apr/20  Updated: 06/Dec/22  Resolved: 18/Feb/22

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: [DO NOT USE] Backlog - Sharding EMEA
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Sharding EMEA
Participants:

 Description   

Guidelines:

Should include

  • Why is it necessary for the filtering table to be propagated via the oplog, as opposed to e.g. secondaries refreshing directly from the config server?

Code references

  • ShardServerCatalogCacheLoader class


 Comments   
Comment by Esha Maharishi (Inactive) [ 11/Jun/20 ]

Moving into PM-1645, since that project is changing the way the filtering table is replicated.

Today, the CatalogCache replicates the filtering table, but this causes problems because it means the CatalogCache cannot be refreshed under a strong lock.

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