[
https://issues.apache.org/jira/browse/HDFS-7642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Mackrory updated HDFS-7642:
Attachment: HDFS-7642.001.patch
Attaching an initial implementation. I'm wondering if hostname is guaranteed to
be non-empty - if it isn't, it may be safer (but less human readable) to use
the node's uuid instead. Since this just runs every 30 seconds (configurable)
it isn't synchronized with the actual state changes of the nodes, so I added a
'~' to the log message to convey that it's just an approximation.
> NameNode should periodically log DataNode decommissioning progress
> --
>
> Key: HDFS-7642
> URL: https://issues.apache.org/jira/browse/HDFS-7642
> Project: Hadoop HDFS
> Issue Type: Improvement
>Reporter: Zhe Zhang
>Assignee: Sean Mackrory
>Priority: Minor
> Attachments: HDFS-7642.001.patch
>
>
> We've see a case where the decommissioning was stuck due to some files have
> more replicas then DNs. HDFS-5662 fixes this particular issue but there are
> other use cases where the decommissioning process might get stuck or slow
> down. Some monitoring / logging will help debugging those issues.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
