[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: |
|
||||||||||||||||
| 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 If |
| Comment by Kaloian Manassiev [ 22/Nov/17 ] |
|
This will not be necessary if we implemented |