[DOCS-5367] Indicate that primary members cache sharding metadata Created: 06/May/15  Updated: 30/Oct/23  Resolved: 01/Nov/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Improvement Priority: Minor - P4
Reporter: Roger McCoy (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

sharding with replica sets


Participants:
Days since reply: 1 year, 14 weeks, 1 day ago
Epic Link: DOCSP-1769

 Description   

Regarding sharding metadata in this document section:
http://docs.mongodb.org/manual/core/sharded-cluster-config-servers/#read-and-write-operations-on-config-servers

It may be helpful to state that in a sharded cluster, the primary members of replica sets cache sharding metadata too, along with mongos.

This may help operations staff, for example, when they are migrating or replacing config servers.



 Comments   
Comment by Education Bot [ 01/Nov/22 ]

Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you!

Generated at Thu Feb 08 07:50:11 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.