hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3409) Secondary namenode should expose checkpoint info via JMX
Date Fri, 11 May 2012 21:33:52 GMT

    [ https://issues.apache.org/jira/browse/HDFS-3409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273638#comment-13273638

Aaron T. Myers commented on HDFS-3409:

Hi Hitesh,

bq. I would defer to anyone who is more well versed with HDFS to make a call on where it makes
sense to expose this information for 1.x ( whether it is in the namenode if it tracks the
last checkpoint time or do it separately in each SNN given that multiple SNNs are supported

What gives you the impression that running multiple Secondary NameNodes is supported? I don't
know of any deployments that consciously choose to run multiple 2NNs, and it's not a configuration
that HDFS is designed to support, in my experience.

Given that, putting this info on the NN makes more sense to me.
> Secondary namenode should expose checkpoint info via JMX
> --------------------------------------------------------
>                 Key: HDFS-3409
>                 URL: https://issues.apache.org/jira/browse/HDFS-3409
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>    Affects Versions: 1.0.2
>            Reporter: Hitesh Shah
> Information such as when the last checkpoint was done should be exposed via JMX so that
it can be easily queried via scripts. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message