Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-14255

Clarification needed in doc regarding multi-shard transactions in a cluster contains arbiters.

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open
    • Priority: Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: manual, Server
    • Labels:
      None
    • Last comment by Customer:
      true
    • Story Points:
      2
    • Sprint:
      ServerDocs2020: Mar2 - Mar9, ServerDocs2020: Mar9 - Mar16, ServerDocs2020: Mar16 - Mar23, ServerDocs2020: Mar23 - Mar30, ServerDocs2020: Mar30 - Apr06, ServerDocs2020: Apr6 - Apr13, ServerDocs2020: Apr13 - Apr20

      Description

      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.)

        Attachments

          Activity

            People

            Assignee:
            andrew.feierabend Andrew Feierabend
            Reporter:
            tom.li Tom Li
            Participants:
            Last commenter:
            Andrew Feierabend Andrew Feierabend
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Due:
              Created:
              Updated:
              Days since reply:
              7 weeks, 3 days ago