[
https://issues.apache.org/jira/browse/HADOOP-942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12643685#action_12643685
]
dhruba borthakur commented on HADOOP-942:
-----------------------------------------
I agree with Konstantin. I think there are two different states: one is the
configured state of the datanode. This can be In-Service/Out-of-Service. This
does not change even if the entire cluster is restarted.
Then there is a "Run State" for each datanode. This reflects the current state
of the datanode. It can be dead/alive.
> 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.
