Skip to main content
On a secure cluster, this area of the DB Console can only be accessed by users belonging to the or a SQL user with the (or the legacy VIEWACTIVITY or VIEWACTIVITYREDACTED ) defined. The or do not grant access to this page.
The Hot Ranges page of the DB Console provides details about ranges receiving a high number of reads or writes. These are known as . When optimizing or troubleshooting statement performance, this page can help you identify nodes, ranges, or tables that are experiencing . To view this page, and click Hot Ranges in the left-hand navigation.

​
Filter hot ranges

Use the Filter menu to filter the hot ranges list on any combination of: node ID, store ID, database, table, index, or locality.

​
Hot ranges list

The Hot ranges list displays the ranges with the highest queries per second (QPS) from each node .
Hot ranges are not necessarily problematic. Some ranges naturally experience higher QPS than others. For example, a range for a frequently accessed table will have a higher QPS.However, a significant increase in traffic can also indicate a hotspot on the range that should be reduced. For more information, refer to . To view the Range Report for a hot range, click its range ID.

​
Range Report

The Range Report is typically used for purposes. If your aim is to , refer to the following fields:
  • Key Range shows the interval of the that is “hottest” (i.e., read by the processor). This is expressed as a span of key values.
  • Lease Holder QPS shows the queries executed per second on the node that holds the . If a hot range is not properly using , this will be greater than the value configured by the kv.range_split.load_qps_threshold (2500 by default).

​
See also