[ https://issues.apache.org/jira/browse/HADOOP-6470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
dhruba borthakur reassigned HADOOP-6470: ---------------------------------------- Assignee: Dmytro Molkov > JMX Context for Metrics > ----------------------- > > Key: HADOOP-6470 > URL: https://issues.apache.org/jira/browse/HADOOP-6470 > Project: Hadoop Common > Issue Type: New Feature > Reporter: Dmytro Molkov > Assignee: Dmytro Molkov > Attachments: JMX.patch > > > The way metrics are currently exposed to the JMX in the NameNode is not > helpful, since only the current counters in the record can be fetched and > without any context those number mean little. > For example the number of files created equal to 150 only means that in the > last period there were 150 files created but when the new period will end is > unknown so fetching 150 again will either mean another 150 files or we are > fetching the same time period. > One of the solutions for this problem will be to have a JMX context that will > accumulate the data (being child class of AbstractMetricsContext) and expose > different records to the JMX through custom MBeans. This way the information > fetched from the JMX will represent the state of things in a more meaningful > way. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.