Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-63538

Detail how transactions could execute on the merged shard + config server

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • None
    • Sharding NYC
    • 5

    Description

      The transactions code has logic conditioned on being executed on a shard or on a config server. In particular, transaction coordinator may behave differently if executed on Config server.
      Investigate if it's necessary to force the transaction coordinator to always pick its role as Config or shard. Investigate if it matters for the mongos sending the transaction. Investigate if a shard coordinator picks a special client to run the local leg of transaction.

      Attachments

        Activity

          People

            backlog-server-sharding-nyc [DO NOT USE] Backlog - Sharding NYC
            andrew.shuvalov@mongodb.com Andrew Shuvalov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: