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

Investigate Grid's fixed executor using different ConnectionPool options

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing

      The Grid's fixed executor NetworkInterface is not setup with the same ConnectionPool::Options as the non-fixed executors. This includes the ShardingTaskExecutorPoolController, which is where parameters such as 
      ShardingTaskExecutorPoolHostTimeoutMS are applied.
       
      This seems like a bug. This ticket is to investigate if this is the case, and fix if appropriate.

            Assignee:
            Unassigned Unassigned
            Reporter:
            yujin.kang@mongodb.com Yujin Kang Park
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: