ExportXMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • ClusterScalability 28Sep-12Oct, ClusterScalability 12Oct-26Oct, ClusterScalability 26Oct-9Nov, ClusterScalability 9Nov-23Nov
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Today, resharding's configuration is based on a number of server parameters. This causes friction in a few ways:

      • Users must set these parameters on each mongod where resharding will be running (including secondaries, in the case of failovers) for them to take affect.
      • Atlas users are not permissioned to change server parameters, so modifying these requires interacting with support.
      • Each of these settings are global to the node where they are running, whereas users may want to be able to vary these parameters per operation in the future when we allow multiple concurrent resharding operations.

      To address this, we should do the following:

      • Allow specifying values each resharding parameter when invoking reshardCollection (and its derivative commands e.g. moveCollection) using an optional config object or similar.
      • Provide a new modifyReshardCollectionOptions command (and corresponding commands for derivative commands e.g. modifyMoveCollectionOptions) which targets an ongoing operation by its UUID and can be used to modify runtime settable parameters for that specific operation.

      Any parameters not modified in this way will get the node default based on the already existing server parameters. To make this more coherent, we may want to consider using the dbPrimary shard's values at the time resharding is initialized for the defaults for the operation as a whole.

            Assignee:
            Brett Nawrocki
            Reporter:
            Brett Nawrocki
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: