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

Docs for SERVER-40462: Disallow transactions on shard servers with writeConcernMajorityJournalDefault = false

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.11
    • Component/s: manual, Server
    • Labels:

      Description

      Description

      Description:

      This commits disallow multi-statement transactions on shard servers that have writeConcernMajorityJournalDefault = false.

      Engineering Ticket Description:

      Nodes running with the in-memory storage engine do not support transaction prepare and because of this, currently they cannot participate in cross-shard transactions.

      On the chance that we start supporting that and in order to ensure that in-memory nodes and nodes running with writeConcernMajorityJournalDefault = false don't count towards the majority quorum for any w:majority writes done by the coordinator and participant, such writes should be done with j:true.

      Scope of changes

      • txn
      • txn prod concern
      • txn sharded clusters prod concern
      • rs conf page
      • For now, will not put in the limits/restriction page for sharded clusters operation.

      Impact to Other Docs

      MVP (Work and Date)

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

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kay.kim Kay Kim (Inactive)
              Reporter:
              kay.kim Kay Kim (Inactive)
              Participants:
              Last commenter:
              Kay Kim Kay Kim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                2 years, 35 weeks, 5 days ago
                Date of 1st Reply: