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

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Sharding NYC
    • 5
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            [DO NOT USE] Backlog - Sharding NYC
            Reporter:
            Andrew Shuvalov (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: