[
https://issues.apache.org/jira/browse/BIGTOP-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14245907#comment-14245907
]
Dasha Boudnik commented on BIGTOP-1560:
---------------------------------------
Hi [~jayunit100],
Thanks for the excellent suggestions (I especially admire the one for the IP
address grep -- after looking at it for a while I stopped noticing how
terrifying it looks :)).
I added to the comment that the test needs to be performed on a cluster with at
least three datanodes, for the block to be able to recover. Is there actually a
need to indicate that block replication needs to be > 1? Correct me if I'm
wrong, but I thought that's always the case...
That's all I can remember as far as requirements go; everything else has been
taken care of within the test, I think... ([~cos], thanks for the puppet recipe
-- let me know if I've missed anything in regard to your comment!)
And [~jayunit100] -- not familiar with vagrant :)
> Add a test case for performing block corruption recovery
> --------------------------------------------------------
>
> Key: BIGTOP-1560
> URL: https://issues.apache.org/jira/browse/BIGTOP-1560
> Project: Bigtop
> Issue Type: Test
> Components: tests
> Affects Versions: 0.8.0
> Reporter: Dasha Boudnik
> Assignee: Dasha Boudnik
> Fix For: 0.9.0
>
> Attachments: BIGTOP-1560.patch, BIGTOP-1560.patch
>
>
> Found this issue in internal testing. Roughly:
> create file in HDFS
> find block for the file
> corrupt a block
> trigger recovery by trying to read the file
> check recovery was successful
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
