hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-942) dfsadmin -report returns deadnode as "In Service"
Date Wed, 29 Oct 2008 22:24:44 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643676#action_12643676
] 

Konstantin Shvachko commented on HADOOP-942:
--------------------------------------------

I think HADOOP-1627 replaced one confusing message "State : In Service" with another "Decommission
State : Normal".
Doesn't it sound confusing for a dead node to have "Decommission State : Normal"?
This field should not be a decommission state but rather a state of the node, which includes
states like
- In service
- Out of Service (dead)
- Decommission in progress.
- Decommissioned.

Should we reopen this issue or create a new one?



> dfsadmin -report returns deadnode as "In Service"
> -------------------------------------------------
>
>                 Key: HADOOP-942
>                 URL: https://issues.apache.org/jira/browse/HADOOP-942
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>            Reporter: Koji Noguchi
>            Assignee: dhruba borthakur
>            Priority: Trivial
>
> dfsadmin -report returned a deadnode entry as follows.
> Name: hostA.zzz.com:12345
> State          : In Service
> Total raw bytes: 0 (0.0 k)
> Used raw bytes: 0 (0.0 k)
> % used: NaN%
> "in service" is confusing for a node that's not running a datanode.

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


Mime
View raw message