[
https://issues.apache.org/jira/browse/HDFS-3585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13405291#comment-13405291
]
Uma Maheswara Rao G commented on HDFS-3585:
-------------------------------------------
Todd, If this situation happened for all blocks( for replication), then we will
not invalidate that corrupt blocks right? If we have enough replication then
only we will go for invalidation.
> Blocks are getting marked as corrupt when commitblocksyncronization(Since
> recovery called by another client) is success before BR send
> --------------------------------------------------------------------------------------------------------------------------------------
>
> Key: HDFS-3585
> URL: https://issues.apache.org/jira/browse/HDFS-3585
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 2.0.1-alpha, 3.0.0
> Reporter: Brahma Reddy Battula
>
> Scenario:
> ===========
> Writing files without close
> renaming file
> deleting files with four DN's and replication factor=3
--
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
