[
https://issues.apache.org/jira/browse/HDFS-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15264558#comment-15264558
]
Andras Bokor commented on HDFS-334:
-----------------------------------
[[email protected]] Why? You wrote the test failures are not related.
I think at this point (if you are sure the test failures are not related) you
need to find a reviewer who can accept/reject/commit your patch.
Note that there are a lot of intermittent test failures in Hadoop, so this does
not always mean wrong patch.
> dfsadmin -metasave should also log corrupt replicas info
> --------------------------------------------------------
>
> Key: HDFS-334
> URL: https://issues.apache.org/jira/browse/HDFS-334
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Reporter: Lohit Vijayarenu
> Assignee: Denis Bolshakov
> Priority: Minor
> Labels: newbie
> Attachments: HDFS-334.001.patch, HDFS-334.002.patch,
> HDFS-334.003.patch
>
>
> _hadoop dfsadmin -metasave <filename>_ should also dump information about
> corrupt replicas map. This could help in telling if pending replication was
> due to corrupt replicas.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
