[
https://issues.apache.org/jira/browse/PHOENIX-5348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16893009#comment-16893009
]
Gokcen Iskender commented on PHOENIX-5348:
------------------------------------------
[~m2je], I don't think the root cause is the DELETEs. If that was the case, the
waitForTaskState would throw an exception "Ran out of time waiting for task
state to become .." since the task table was empty. It must have find a
complete task there to get to this statement.
I am adding a check that the task it checks for Complete status is a relevant
task. If there is a COMPLETE task but for another table, we return from
waitForTaskState even though the task that we are interested in is not complete
yet.
> IndexRebuildTaskIT.testIndexRebuildTask flaps (Jenkins only)
> ------------------------------------------------------------
>
> Key: PHOENIX-5348
> URL: https://issues.apache.org/jira/browse/PHOENIX-5348
> Project: Phoenix
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Gokcen Iskender
> Priority: Critical
> Fix For: 4.15.0, 5.1.0
>
> Attachments: 5348-disable.txt, 5348-v2.txt, 5348.txt
>
>
> This failed in the past four builds:
> {code}
> [ERROR] testIndexRebuildTask(org.apache.phoenix.end2end.IndexRebuildTaskIT)
> Time elapsed: 20.672 s <<< FAILURE!
> java.lang.AssertionError: expected:<1> but was:<0>
> at
> org.apache.phoenix.end2end.IndexRebuildTaskIT.testIndexRebuildTask(IndexRebuildTaskIT.java:164)
> {code}
> But... It does not fail locally for me.
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
