You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Jasen Minton (Jira)" <ji...@apache.org> on 2021/04/14 22:49:02 UTC
[jira] [Commented] (HDDS-4839) RocksDB statistics not exposed on
Ozone DN
[ https://issues.apache.org/jira/browse/HDDS-4839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17321490#comment-17321490 ]
Jasen Minton commented on HDDS-4839:
------------------------------------
When containers exist in the DN, the corresponding jmx entries are created at startup (and at the time of the container creation). For example:
{{"name" : "Hadoop:service=HddsDatanode,name=Rocksdb_1-dn-container.db",}}
When I start fresh, I do not see container jmx entries but if I exercise the DN and store some data, containers are created and their corresponding jmx entries show up at DN start. I don't see the error unless I'm not fully understanding the bug report to begin with.
> RocksDB statistics not exposed on Ozone DN
> ------------------------------------------
>
> Key: HDDS-4839
> URL: https://issues.apache.org/jira/browse/HDDS-4839
> Project: Apache Ozone
> Issue Type: Bug
> Components: Ozone Datanode
> Affects Versions: 1.0.0
> Reporter: Wei-Chiu Chuang
> Assignee: Jasen Minton
> Priority: Major
>
> Setting ozone.metastore.rocksdb.statistics = ALL, I can find the rocksdb stats exposed in OM JMX
> {noformat}
> "name" : "Hadoop:service=Ozone,name=RocksDbStore,dbName=om.db",
> {noformat}
> but the entry is not found on DN if I try to enable this property on a DN. Initial hunch is that the tocksdb stats is created per DN, and DN has many DBs. When one DB is closed, the corresponding JMX entry is removed.
>
> This bug is similar to HDDS-4722.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org