[
https://issues.apache.org/jira/browse/HDFS-15170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17246486#comment-17246486
]
Ayush Saxena edited comment on HDFS-15170 at 12/9/20, 12:33 PM:
----------------------------------------------------------------
Thanx [~hexiaoqiao]
Yeps, that is expected, since initially the count will be 0 only, when the IBR
gets processed it will get marked as 1,
I added a comment above, regarding how to repro.
https://issues.apache.org/jira/browse/HDFS-15170?focusedCommentId=17037104&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17037104
just remove the prod change and change 0 to 1 in test, It will show that the
count increases to 1.
May be we can add a Thread.sleep(10000) after cluster.restartDataNode(dn); and
that should also make the test fail,
Let me know if you have any suggestions for improving the test, or finding
difficulty reproducing it, or any issues with the code change.
was (Author: ayushtkn):
Thanx [~hexiaoqiao]
Yeps, that is expected, since initially the count will be 0 only, when the IBR
gets processed it will get marked as 1,
I added a comment above, regarding how to repro.
https://issues.apache.org/jira/browse/HDFS-15170?focusedCommentId=17037104&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17037104
just remove the prod change and change 0 to 1 in test, It will show that the
count increases to 1.
> EC: Block gets marked as CORRUPT in case of failover and pipeline recovery
> --------------------------------------------------------------------------
>
> Key: HDFS-15170
> URL: https://issues.apache.org/jira/browse/HDFS-15170
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Ayush Saxena
> Assignee: Ayush Saxena
> Priority: Critical
> Attachments: HDFS-15170-01.patch, HDFS-15170-02.patch,
> HDFS-15170-03.patch
>
>
> Steps to Repro :
> 1. Start writing a EC file.
> 2. After more than one stripe has been written, stop one datanode.
> 3. Post pipeline recovery, keep on writing the data.
> 4.Close the file.
> 5. transition the namenode to standby and back to active.
> 6. Turn on the shutdown datanode in step 2
> The BR from datanode 2 will make the block corrupt and during invalidate
> block won't remove it, since post failover the blocks would be on stale
> storage.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
