We are currently refactoring our documentation. Please excuse any problems you may find and report them here.

This section describes how to configure scheduling rate limit, specifically, at the store level.

In TiKV, PD generates different scheduling operators based on the information gathered from TiKV and scheduling strategies. The operators are then sent to TiKV to perform scheduling on Regions. You can use *-schedule-limit to set speed limits on different operators, but this may cause performance bottlenecks in certain scenarios because these parameters function globally on the entire cluster. Rate limit at the store level allows you to control scheduling more flexibly with more refined granularities.

How to configure scheduling rate limits on stores

PD provides the following two methods to configure scheduling rate limits on stores:

  • Configure the rate limit using store-balance-rate.

    The modification only takes effect on stores added after this configuration change, and will be applied to all stores in the cluster after you restart TiKV. If you want this change to work immediately on all stores or some individual stores before the change without restarting, combine this configuration with the pd-ctl tool method below. See Sample usages for more details.

    store-balance-rate specifies the maximum number of scheduling tasks allowed for each store per minute. The scheduling steps include adding peers or learners. Set this parameter in the PD configuration file. The default value is 15. This configuration is persistent.

    Use the pd-ctl tool to modify store-balance-rate and make it persistent.

    Example:

    1. » config set store-balance-rate 20

  • Use the pd-ctl tool to view or modify the upper limit of the scheduling rate. The commands are:

    This method is not persistent, and the configuration will revert after restarting TiKV.

    • stores show limit

      Example:

      1. # If store-balance-rate is set to 15, the corresponding rate for all stores should be 15.
      2. » stores show limit
      3. {
      4.     "4": {
      5.         "rate": 15
      6.     },
      7.     "5": {
      8.         "rate": 15
      9.     },
      10.     # ...
      11. }

    • stores set limit <rate>

      Example:

      1. # Set the upper limit of scheduling rate for all stores to be 20 scheduling tasks per minute.
      2. » stores set limit 20

    • store limit <store_id> <rate>

      Example:

      1. # Set the upper limit of scheduling speed for store 2 to be 10 scheduling tasks per minute.
      2. » store limit 2 10

See PD Control for more detailed description of these commands.

Sample usages

  • The following example modifies the rate limit to 20 and applies immediately to all stores. The configuration is still valid after restart.

    1. » config set store-balance-rate 20
    2. » stores set limit 20

  • The following example modifies the rate limit for all stores to 20 and applies immediately. After restart, the configuration becomes invalid, and the rate limit for all stores specified by store-balance-rate takes over.

    1.  » stores set limit 20

  • The following example modifies the rate limit for store 2 to 20 and applies immediately. After restart, the configuration becomes invalid, and the rate limit for store 2 becomes the value specified by store-balance-rate.

    1. » store limit 2 20