You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/current/v25.2/detect-hotspots.md
+1-2Lines changed: 1 addition & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,6 @@ This page provides practical guidance for identifying common [hotspots]({% link
10
10
11
11
- Review the [Understand hotspots page]({% link {{ page.version.version }}/understand-hotspots.md %}) for definitions and concepts.
12
12
- Ensure you have access to the DB Console Metrics and the relevant logs.
13
-
- Confirm that you have the necessary permissions to modify the application or schema.
14
13
15
14
## Troubleshooting overview
16
15
@@ -48,7 +47,7 @@ For example:
48
47
- Is there a node with a maximum value that is a clear outlier in the cluster for the CPU percent metric?
49
48
50
49
- If **Yes**, note the ID of the [hot node]({% link {{ page.version.version }}/understand-hotspots.md %}#hot-node) and the time range when it was hot. Proceed to check for a [`popular key detected `log](#a-popular-key-detected).
51
-
- If **No**, investigate other possible causes for the metrics outlier.
50
+
- If **No**, and the metrics outlier appears in a metric other than CPU percent or latch conflict wait duration, consider causes other than a hotspot.
52
51
53
52
## Step 2. Check for existence of `no split key found` log
0 commit comments