summaryrefslogtreecommitdiff
path: root/src/mongo/db/s/README.md
diff options
context:
space:
mode:
authorHaley Connelly <haley.connelly@mongodb.com>2020-04-17 13:55:47 -0400
committerEvergreen Agent <no-reply@evergreen.mongodb.com>2020-04-27 20:50:49 +0000
commit24461c383f25dbba57aa0ea20270f37a172b86b4 (patch)
tree772bb4561d5292cb5c16f1f39f0cfd98f4c4ff11 /src/mongo/db/s/README.md
parent738290e8227e99e08665cbdd8e110312a587d165 (diff)
downloadmongo-24461c383f25dbba57aa0ea20270f37a172b86b4.tar.gz
SERVER-47239 Add the 'Replica set monitoring and host targeting' section to the sharding arch guide
Diffstat (limited to 'src/mongo/db/s/README.md')
-rw-r--r--src/mongo/db/s/README.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/src/mongo/db/s/README.md b/src/mongo/db/s/README.md
index d3b82aca164..0c7a17a1784 100644
--- a/src/mongo/db/s/README.md
+++ b/src/mongo/db/s/README.md
@@ -39,8 +39,10 @@ on each of these collections for efficient querying
## The shards list cache
-## Replica set monitoring and host targeting
+## Targeting a specific host within a shard
+When routing a query to a replica set, a cluster node must determine which member to target for a given read preference. A cluster node either has or creates a ReplicaSetMonitor for each remote shard to which it needs to route requests. Information from the ReplicaSetMonitor interface is used to route requests to a specific node within a shard.
+Further details on replica set monitoring and host targeting can be found [here](../../../mongo/client/README.md).
---
# Migrations