One-click Inspection generates a health report for your Lindorm cluster, covering node status, shard distribution, storage usage, and hot spot activity. Use it to identify hot shards and hot keys before they affect cluster performance.
Prerequisites
Before you begin, ensure that you have:
Logged in to Lindorm Insight for your cluster. For more information, see Log on to Lindorm Insight.
Access to the upgraded console. One-click Inspection is only available in the upgraded console and does not appear in the current console version. To request access, submit a ticket.
Run an inspection
In the left-side navigation pane of the Lindorm Insight page, click One-click Inspection.
Select an Internet Data Center (IDC) and a group, then click Query. The inspection report appears. The following table describes each section.
Section What it shows When to pay attention Instance/Cluster Basic Information The database type and the IDC where it is deployed. Verify that the IDC matches your expected deployment location. Table/Database Space The number of namespaces and tables in the group, and the total size of all tables. Check this section when table count or total size grows unexpectedly. Storage Overview Total storage capacity, storage used by table data, WAL logs, and other objects, and the overall usage ratio. Investigate if the usage ratio is high. Plan capacity upgrades before storage is exhausted. Node Overview The number of read/write requests per second sent to nodes in the group, along with generated traffic and average response time. Look for nodes with significantly higher request rates or response times than others, which may indicate uneven shard distribution. topregion The nodes and tables storing the hottest shards, the list of hot shards, and the number of requests per second accessing each shard. High request counts on a small number of shards indicate a hot shard problem. Consider splitting or rebalancing those shards. topkey The nodes, tables, and shards storing the hottest keys, the list of hot keys, the number of read requests per second and generated traffic for each key, and average response time. A key with disproportionately high read traffic or response time is a hot key. Redesign the access pattern or row key to spread the load. Optional: Click Export to export the inspection report for the current cluster.