[
https://issues.apache.org/jira/browse/HBASE-7417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538861#comment-13538861
]
Lars Hofhansl commented on HBASE-7417:
--------------------------------------
So that fixed the weird SplitLogManager messages, but the truncate still timed
out.
That part is actually scary too, because it means the deleted rows were not
replicated in a reasonable time. That could be a test problem, or indicating
that something is wrong with replication.
I know you prefer #2 and #3 [[email protected]]. But I am beginning to feel
that we should roll back these two changes from 0.94 to keep 0.94 stable. Maybe
even more changes need to be reverted.
Before Dec 12th or 13th or so, we had close to 80% pass rates of the 0.94
tests. Something happened then, maybe it's the ipv4 change? Or the upgrade to
ZK 3.4.5? It's very hard to pinpoint this locally.
> TestReplication is flaky
> ------------------------
>
> Key: HBASE-7417
> URL: https://issues.apache.org/jira/browse/HBASE-7417
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Priority: Critical
> Fix For: 0.96.0, 0.94.4
>
> Attachments: 7417-0.94.txt, 7417-0.96.txt, 7417-test.txt,
> 7417-test-v2.txt
>
>
> See discussion at the end of HBASE-5778.
> TestReplication failed in all recent 0.94 jenkins builds.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
