[
https://issues.apache.org/jira/browse/HDFS-10810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15489048#comment-15489048
]
Brahma Reddy Battula commented on HDFS-10810:
---------------------------------------------
bq. but I don't see why the block is counted as corrupt.
It will mark as corrupt,after using {{hasEnoughEffectiveReplicas(block, repl,
pendingNum,curExpectedReplicas}} instead of {{isNeededReconstruction(block,
repl.liveReplicas()}} see the [comment here |
https://issues.apache.org/jira/browse/HDFS-10810?focusedCommentId=15445957&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15445957]
for same.
Since mainly this jira is for not considering for underconstruction,I put
underconstruction assert first so that testcase will fail without the fix.
> Setreplication removing block from underconstrcution temporarily when batch
> IBR is enabled.
> --------------------------------------------------------------------------------------------
>
> Key: HDFS-10810
> URL: https://issues.apache.org/jira/browse/HDFS-10810
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Brahma Reddy Battula
> Assignee: Brahma Reddy Battula
> Attachments: HDFS-10810-002.patch, HDFS-10810-003.patch,
> HDFS-10810.patch
>
>
> 1)Batch IBR is enabled with number of committed blocks allowed=1
> 2) Written one block and closed the file without waiting for IBR
> 3)Setreplication called immediately on the file.
> So till the finalized IBR Received, this block will be marked as corrupt.
--
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
