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

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

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Gone away
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Sharding
    • Labels:
      None

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              backlog-server-sharding Backlog - Sharding Team
              Reporter:
              esha.maharishi Esha Maharishi
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: