You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Harsh J (Created) (JIRA)" <ji...@apache.org> on 2011/11/20 05:09:51 UTC

[jira] [Created] (HDFS-2569) DN decommissioning quirks

DN decommissioning quirks
-------------------------

                 Key: HDFS-2569
                 URL: https://issues.apache.org/jira/browse/HDFS-2569
             Project: Hadoop HDFS
          Issue Type: Bug
          Components: data-node
    Affects Versions: 0.23.0
            Reporter: Harsh J
            Assignee: Harsh J


Decommissioning a node is working slightly odd in 0.23+:

The steps I did:

- Start HDFS via {{hdfs namenode}} and {{hdfs datanode}}. 1-node cluster.
- Zero files/blocks, so I go ahead and exclude-add my DN and do {{hdfs dfsadmin -refreshNodes}}
- I see the following log in NN tails, which is fine:
{code}
11/11/20 09:28:10 INFO util.HostsFileReader: Setting the includes file to 
11/11/20 09:28:10 INFO util.HostsFileReader: Setting the excludes file to build/test/excludes
11/11/20 09:28:10 INFO util.HostsFileReader: Refreshing hosts (include/exclude) list
11/11/20 09:28:10 INFO util.HostsFileReader: Adding 192.168.1.23 to the list of hosts from build/test/excludes
{code}
- However, DN log tail gets no new messages. DN still runs.
- The dfshealth.jsp page shows this table, which makes no sense -- why is there 1 live and 1 dead?:

|Live Nodes|1 (Decommissioned: 1)|
|Dead Nodes|1 (Decommissioned: 0)|
|Decommissioning Nodes|0|

- The live nodes page shows this, meaning DN is still up and heartbeating but is decommissioned:

|Node|Last Contact|Admin State|
|192.168.1.23|0|Decommissioned|

- The dead nodes page shows this, and the link to the DN is broken cause the port is linked as -1. Also, showing 'false' for decommissioned makes no sense when live node page shows that it is already decommissioned:

|Node|Decommissioned|
|192.168.1.23|false|

Investigating if this is a quirk only observed when the DN had 0 blocks on it in sum total.

--
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