[DOCS-15643] Add "Change shard key is not supported for replica sets with arbiters" Created: 22/Sep/22  Updated: 22/Jan/24

Status: Backlog
Project: Documentation
Component/s: Server
Affects Version/s: 5.0.4
Fix Version/s: None

Type: Task Priority: Minor - P4
Reporter: Yuan Fang Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: backlog, feature, replication, sharding
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-64462 更新shard key并abortTransaction得到报错并导致mo... Closed
Participants:
Days since reply: 1 year, 19 weeks, 6 days ago
Epic Link: DOCSP-11702

 Description   

We should document considerations in https://www.mongodb.com/docs/manual/core/replica-set-arbiter/  for sharded clusters with arbiters so that it's very clear what the limitations of arbiters are.

In SERVER-64462  the issue (Changing shard keys errored for replica sets with an arbiter) was caused by unawareness of the fact that:

transactions whose write operations span multiple shards will error and abort if any transaction operation reads from or writes to a shard that contains an arbiter.

The context has been documented in transactions-sharded-clusters we believe it would be helpful to add a similar context in replica-set-arbiter (The first link that shows up by googling "MongoDB arbiters") to bring awareness of the limitation of using arbiters to users.


Generated at Thu Feb 08 08:13:27 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.