[SERVER-32075] Load sharding metadata from disk on mongod startup Created: 22/Nov/17  Updated: 06/Dec/22  Resolved: 23/Jan/20

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

Type: Bug Priority: Major - P3
Reporter: Spencer Brody (Inactive) Assignee: [DO NOT USE] Backlog - Sharding Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-32198 Missing collection metadata on the sh... Closed
Related
related to SERVER-32198 Missing collection metadata on the sh... Closed
Assigned Teams:
Sharding
Operating System: ALL
Participants:

 Description   

Starting in 3.6, when a shard mongod loads the chunk metadata for a sharded collection, it records that metadata durably. If the mongod restarts, however, the in-memory cache of that information is lost and isn't loaded until a metadata refresh is triggered via a request from a mongos. Shard mongods should load the routing information from its persistent local copy into memory at startup.



 Comments   
Comment by Spencer Brody (Inactive) [ 22/Nov/17 ]

I think that's right. But doing this ticket even without SERVER-31056 would still have value, if this ticket is easier to implement.

If SERVER-31056 is as easy or easier to implement, then feel free to close this one, that one is certainly the fuller fix.

Comment by Kaloian Manassiev [ 22/Nov/17 ]

This will not be necessary if we implemented SERVER-31056/SERVER-32198, right?

Generated at Thu Feb 08 04:29:06 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.