Skip to content

Commit 7e7f289

Browse files
committed
Incorporated Brian’s feedback 3.
1 parent 8fd4609 commit 7e7f289

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

src/current/v25.2/detect-hotspots.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,6 @@ This page provides practical guidance for identifying common [hotspots]({% link
1010

1111
- Review the [Understand hotspots page]({% link {{ page.version.version }}/understand-hotspots.md %}) for definitions and concepts.
1212
- 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.
1413

1514
## Troubleshooting overview
1615

@@ -48,7 +47,7 @@ For example:
4847
- Is there a node with a maximum value that is a clear outlier in the cluster for the CPU percent metric?
4948

5049
- 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.
5251

5352
## Step 2. Check for existence of `no split key found` log
5453

0 commit comments

Comments
 (0)