Protect shards from aggressive commitTransaction (et. al.) operations

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Sharding
    • Cluster Scalability
    • ALL
    • Cluster Scalability Priorities
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      The Sharding Fixed executor is configured to allow unlimited thread pool growth and can be used to route commitTransaction operations. But since commitTransaction operations can be user-driven, we should ensure mongods can be protected against aggressive client activity via the ShardingTaskExecutorPoolMinSize/ShardingTaskExecutorPoolMaxSize configs, such as by routing these operations to mongos Arbitrary Executors (NetworkInterface/TaskExecutor-0).

      This should also apply to any other operations that may be user-initiated within transactions.

      cc max.hirschhorn@mongodb.com

            Assignee:
            Unassigned
            Reporter:
            Eric Sedor
            Votes:
            0 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated: