DOC-13785 Product Change- PR #147169 - release-25.2: add log and metric for identifying clear access direction #19748
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…and clear direction metrics and logs.
✅ Deploy Preview for cockroachdb-interactivetutorials-docs canceled.
|
✅ Deploy Preview for cockroachdb-api-docs canceled.
|
✅ Netlify Preview
To edit notification comments on pull requests, go to your Netlify project configuration. |
kevin-v-ngo
requested changes
Jun 16, 2025
|
|
||
| This log message can usually be ignored. However, if it appears repeatedly, it may indicate a load imbalance in the cluster. A load imbalance might occur if a [hot range]({% link {{ page.version.version }}/understand-hotspots.md %}#hot-range) cannot be split because it is effectively a [hot key]({% link {{ page.version.version }}/understand-hotspots.md %}#row-hotspot). For more information about how to reduce hotspots (including hot ranges) on your cluster, refer to [Understand hotspots]({% link {{ page.version.version }}/understand-hotspots.md %}). | ||
|
|
||
| The log message ends with one of the following string combinations, indicating the observed load pattern: |
There was a problem hiding this comment.
Perhaps more of a question for @angles-n-daemons,
- If there is "no split key found:" doesn't that imply that there was a popular key and thus is the 'hot key' scenario? What does it mean to have "popular key" and "clear direction detected"? Clear direction implies hot index correct?
clear direction detected indicates that accesses within the range progress steadily in one direction, either increasing or decreasing key order.
Should we call out 'hot index'? (Relatedly to my question above, i'm assuming this error points to a hot index issue.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes DOC-13785 DOC-13379
In load-based-splitting.md, updated monitor section with popular key and clear direction metrics and logs.
Rendered preview
Monitor load-based splitting