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

Coordinating a transaction should run fully in the ThreadPoolTaskExecutor for sharding tasks

    • Type: Icon: Task Task
    • Resolution: Gone away
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Sharding

      Currently, coordinating a transaction "hops" between the TransactionCoordinatorService's ThreadPool and the fixed ThreadPoolTaskExecutor on the Grid.

      It does so in order to run the parts of the commit coordination that block on the local storage engine in a separate thread pool from the Grid's fixed ThreadPoolTaskExecutor.

      This ticket is to make coordinating the transaction run wholly on the fixed ThreadPoolTaskExecutor on the Grid, and set the size of the thread pool in that ThreadPoolTaskExecutor to unbounded.

            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            0 Vote for this issue
            5 Start watching this issue