[
https://issues.apache.org/jira/browse/HDDS-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16683369#comment-16683369
]
Elek, Marton commented on HDDS-816:
-----------------------------------
Thanks [~bharatviswa] for this. It was a missing point for me as well. As of
now when I start test cluster I can't follow the key numbers especially if the
servers are restarted.
I have two comments about the design doc:
1. Usually I am not interested about the exact numbers. Doesn't matter if it's
15 000 001 or 15 000 002. I would like to know that I have about 15 000 000
keys and show on graphana.
Therefore the "Always wrong" value in the "Estimated keys" row is too strong
for me. It's not "wrong" just "eventual" ;-)
2. Independent from the selected approach I hope that it can be implemented as
part of the DBTable abstraction. Would help to adjust/switch over later without
too much pain.
> Create OM metrics for bucket, volume, keys
> ------------------------------------------
>
> Key: HDDS-816
> URL: https://issues.apache.org/jira/browse/HDDS-816
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Manager
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
> Attachments: HDDS-816.00.patch, Metrics for number of volumes,
> buckets, keys.pdf
>
>
> This Jira is used to create the following metrics in Ozone manager.
> # number of volumesÂ
> # number of buckets
> # number of keys
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
