Skip to content

Commit a4c60c8

Browse files
authored
DOCSP-33087 Arbiters in Sharded Clusters (#5388) (#5481)
* DOCSP-33087 Arbiters in Sharded Clusters * Fixes per Joe * fixes per Joe
1 parent eb596dc commit a4c60c8

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

source/core/sharded-cluster-shards.txt

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,8 +14,14 @@ A :term:`shard` contains a subset of sharded data for a :term:`sharded
1414
cluster`. Together, the cluster's shards hold the entire data set for the
1515
cluster.
1616

17-
As of MongoDB 3.6, shards must be deployed as a :term:`replica set` to
18-
provide redundancy and high availability.
17+
Shards must be deployed as a :term:`replica set` to provide redundancy and high
18+
availability.
19+
20+
.. important::
21+
22+
Sharded clusters use the write concern ``"majority"`` for a lot of internal
23+
operations. Using an arbiter in a sharded cluster is discouraged due to
24+
:ref:`replica-set-arbiter-performance-psa`.
1925

2026
Users, clients, or applications should only directly connect to a shard to
2127
perform local administrative and maintenance operations.

0 commit comments

Comments
 (0)