hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erik Krogen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-12004) Namenode UI continues to list DNs that have been removed from include and exclude
Date Mon, 26 Jun 2017 16:17:00 GMT

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

Erik Krogen commented on HDFS-12004:

Ah, don't know how I missed that. Thank you, [~kihwal]. Sorry for the duplication.

> Namenode UI continues to list DNs that have been removed from include and exclude
> ---------------------------------------------------------------------------------
>                 Key: HDFS-12004
>                 URL: https://issues.apache.org/jira/browse/HDFS-12004
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.3.0
>            Reporter: Erik Krogen
>            Priority: Minor
> Initially in HDFS, after a DN was decommission and subsequently removed from the exclude
file (thus removing all references to it), it would still appear in the NN UI as a "dead"
node until the NN was restarted. In HDFS-1773, discussion about this was had, and it was decided
that the web UI should not show these nodes. However when HDFS-5334 went through and the NN
web UI was reimplemented client-side, the behavior reverted back to pre-HDFS-1773, and dead+decommissioned
nodes once again showed in the dead list. This can be operationally confusing for the same
reasons as discussed in HDFS-1773.
> I would like to open this discussion to determine if the regression was intentional or
if we should carry forward the logic implemented HDFS-1773 into the new UI.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message