[
https://issues.apache.org/jira/browse/HBASE-14600?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14963577#comment-14963577
]
stack commented on HBASE-14600:
-------------------------------
bq. Otherwise it will break down this testcase when i<50, we'd better just
catch "Sync aborted exception".
I wanted to loosen the conditions under which the test was considered passing.
If we broke out here with sync aborted and we'd done i > 50, then that would be
enough exercise for the test to pass. If i < 50, I want it to fail. Its worth
digging in if it fails at i < 50...
> Make #testWalRollOnLowReplication looser still
> ----------------------------------------------
>
> Key: HBASE-14600
> URL: https://issues.apache.org/jira/browse/HBASE-14600
> Project: HBase
> Issue Type: Sub-task
> Components: test
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: 14600.addendum.txt, 14600.txt
>
>
> The parent upped timeouts on testWalRollOnLowReplication. It still fails on
> occasion. Chatting w/ [~mbertozzi], he suggested that if we've make progress
> in the test, return the test as compeleted successfully if we get a
> RuntimeException out of the sync call....(because DN is slow to recover).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
