HDDS-15324. Dashboard for monitoring Data Node performance#10314
Open
yandrey321 wants to merge 1 commit into
Open
HDDS-15324. Dashboard for monitoring Data Node performance#10314yandrey321 wants to merge 1 commit into
yandrey321 wants to merge 1 commit into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What changes were proposed in this pull request?
Created a dashboard that shows DataNode performance metrics:
JVM (HddsDatanode)
CPU — JVM vs system load for the DN process hosts you pick.
Heap — used, committed, and max heap memory.
Garbage collection — how much CPU time GC uses and how often collections happen.
Netty — direct (off-heap) buffer use vs configured max.
Threads — count of JVM threads by state.
Ratis
Log append throughput, flushes, and RPC-style client read/write rates.
Backlog (pending queue) and rough timing snapshots for appends, follower appends, and log sync; failed writes rate.
All of this is rolled up across raft groups per DataNode (one scrape target series per selected node).
Container I/O
For common Xceiver operations (WriteChunk, ReadChunk, PutBlock, GetBlock, DeleteChunk/Block, CreateContainer, CloseContainer):
How many ops per second, bytes per second, and average latency (CloseContainer omits bytes; only ops + latency).
Storage volume I/O
Per selected DataNode, sums across disks: read/write throughput, read/write IOPS, read/write latency, and volume space used vs capacity (excluding total-capacity rollup metrics).
SCM commands and background work
Command handlers — for each SCM command type, panels for incoming command rate, handler invocation rate, run time, queue depth, and optional thread-pool size — so you can see SCM-driven work separated by command.
Block deleting service — background delete pipeline: transactions, blocks/bytes succeeded or failed, pending/chosen/marked counts, retries, outliers (e.g. lock timeouts, out-of-order transactions).
What is the link to the Apache JIRA
[Please create an issue in ASF JIRA before opening a pull request, and you need to set the title of the pull
request which starts with the corresponding JIRA issue number. (e.g. HDDS-XXXX. Fix a typo in YYY.)
If you do not have an ASF Jira account yet, please follow the first-time contributor
instructions in the Jira guideline.
(Please replace this section with the link to the Apache JIRA)
](https://issues.apache.org/jira/browse/HDDS-15324)
How was this patch tested?
Deployed Grafana locally, connected the dashboard to the data source with Ozone metrics.