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

Support changing ShardingTaskExecutorPoolMinSize via setParameter without restart

    XMLWordPrintable

Details

    • Fully Compatible
    • Service Arch 2022-1-10, Service Arch Test, Service Arch 2022-1-24
    • 4

    Description

      Currently, changing ShardingTaskExecutorPoolMinSize requires a restart.

      But safe settings require consideration of total router count. So, in clusters that use this setting to keep connection pools as warm as possible, adding or removing shards requires a restart of all routers.

      Allowing ShardingTaskExecutorPoolMinSize to be configured via setParameter without restart allows shards to be added and removed without the added operational complexity and service interruption.

      Note that the related setting, ShardingTaskExecutorPoolMaxSize, is not as coupled to router count as the min size is. But as these settings are commonly paired it probably makes sense to allow both to be changed without restart. That said, *MinSize is more important to be able to change on the fly.

      (cc jason.carey)

      Attachments

        Issue Links

          Activity

            People

              tyler.seip@mongodb.com Tyler Seip (Inactive)
              eric.sedor@mongodb.com Eric Sedor
              Votes:
              1 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: