hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tsz Wo (Nicholas), SZE (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3767) Brief, baseline namenode health check
Date Sat, 02 Aug 2008 00:47:31 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619175#action_12619175

Tsz Wo (Nicholas), SZE commented on HADOOP-3767:

I think you need to set "bad = true" inside the then-clause.  Otherwise, if the condition
in the first if-statement is true, all other then-clauses will be executed since (bad |= xxx)
will return true.

> Brief, baseline namenode health check
> -------------------------------------
>                 Key: HADOOP-3767
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3767
>             Project: Hadoop Core
>          Issue Type: New Feature
>          Components: dfs
>            Reporter: Chris Douglas
>            Priority: Minor
>         Attachments: 3767-0.patch
> It would be helpful if there were a way to query the namenode to verify that it is basically
healthy. In particular, that all the expected threads are running, data structures appear
sane, etc. Administrators could use this interface to verify that the namenode is both up
and essentially functional, attaching cron jobs, notification, etc. as required.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message