hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-1138) Datanodes that are dead for a long long time should not show up in the UI
Date Tue, 04 Sep 2007 18:50:45 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-1138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Raghu Angadi updated HADOOP-1138:

    Attachment: HADOOP-1138.patch

New patch attached.

bq. 1. FSnamesystem.getDatanodeListForReport excludes nodes that are listed in dfs.hosts.exclude.
Maybe a better option wold be to show them with a status of "Excluded". Currently, it shows
"Decommisioned" or "In Service".

Currently there is no state shown for deadnodes. Note that this method looks at dfs.hosts.exclude
only for datanodes that are considered dead.

bq. 2. The comment in FSnamesystem.getDatanodeListForReport talks about "dfs.report.datanode.timeout.day"
but it should be "dfs.report.datanode.timeout.hours".

Done. Good catch. You actually read the comments!

bq. 3. Maybe a unit test case that tests this functionality would be really nice.
This is a very non-consequential functionality. It only affects Namenode front page and 'dfsadmin
-report'. Let me know if we really need to add a unit test. I did test it. 

> Datanodes that are dead for a long long time should not show up in the UI
> -------------------------------------------------------------------------
>                 Key: HADOOP-1138
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1138
>             Project: Hadoop
>          Issue Type: Bug
>          Components: dfs
>            Reporter: dhruba borthakur
>            Assignee: Raghu Angadi
>             Fix For: 0.15.0
>         Attachments: HADOOP-1138.patch, HADOOP-1138.patch
> Proposal 1:
> If a include files is used, then show all nodes (dead/alive) that are listed in the includes
file. If there isn't an include file, then display only nodes that have pinged this instance
of the namenode.
> Proposal2:
> A config variable specifies the time duration. The namenode, on a restart, purges all
datanodes that have not pinged for that time duration. The default value of this config variable
can be 1 week. 

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

View raw message