Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-10907

Docs for SERVER-30482: Mongos should not close sessions to below the configured ShardingTaskExecutorPoolMinSize

    XMLWordPrintable

    Details

      Description

      We document them in the https://docs.mongodb.com/manual/reference/parameters/index.html#param.ShardingTaskExecutorPoolHostTimeoutMS

      Documentation Request Summary:

      The server is now enforcing and correcting bad values of these parameters in the following way. If they are documented, the documentation should probably reflect this:

      ShardingTaskExecutorPoolHostTimeoutMS > ShardingTaskExecutorPoolRefreshRequirementMS > ShardingTaskExecutorPoolRefreshTimeoutMS

      ShardingTaskExecutorPoolHostTimeoutMS > ShardingTaskExecutorPoolRefreshRequirementMS + ShardingTaskExecutorPoolRefreshTimeoutMS

      Engineering Ticket Description:

      While doing some testing with mongos connection we noticed that if you set the ShardingTaskExecutorPoolHostTimeoutMS below the heartbeat timer mongos will close the idle sessions to secondaries (in our case they aren't in use).

      This is a poor behavior because ShardingTaskExecutorPoolMinSize is set to 1, and this ShardingTaskExecutorPoolHostTimeoutMS enforcement is causing the only single connection open to close-- which means that mongos must then immediately create a new one.

      Mongos should not close sessions to below the configured ShardingTaskExecutorPoolMinSize regardless of the configured ShardingTaskExecutorPoolHostTimeoutMS

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              kevin.albertson Kevin Albertson
              Reporter:
              kay.kim Kay Kim
              Participants:
              Last commenter:
              Githook User
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Days since reply:
                1 year, 29 weeks ago
                Date of 1st Reply: