Description

Customer reported problems performing multi-shard transactions in a cluster that contains arbiters in the shards. This limitation is clearly mentioned in some sections of our documentation, eg here which directly states:

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.

However, other sections of the documentation are much less clear on the matter. For example, customer linked this page which states:

A transaction that writes to multiple shards errors if any of the transaction’s read or write operations involves a shard that has disabled read concern "majority".

The above implies that such an operation (transaction writing to multiple shards) would be successful if read concern majority had not been disabled.

I suggest that we specifically state out that the "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." in the disable-read-concern-majority part of the doc, to clarify the limitations.

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)