You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@oozie.apache.org by "Peter Bacsko (JIRA)" <ji...@apache.org> on 2016/06/01 04:40:12 UTC
[jira] [Updated] (OOZIE-2548) Flaky test
TestZKLocksService.testLockReaper
[ https://issues.apache.org/jira/browse/OOZIE-2548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Bacsko updated OOZIE-2548:
--------------------------------
Description:
The testcase testLockReaper in TestZKLocksService is unstable.
The reason is that the test case sleeps for 2 seconds and checks the number of nodes under /locks. The child reaper threads remove ZK nodes after the ZK locks are released. However, 2 seconds is not always enough.
was:
The testcase testLockReaper in TestZKLocksService is unstable.
The reason is that the test cases sleeps for 2 seconds and checks the number of nodes under /locks. The child reaper threads remove ZK nodes after the ZK locks are released. However, 2 seconds is not always enough.
> Flaky test TestZKLocksService.testLockReaper
> --------------------------------------------
>
> Key: OOZIE-2548
> URL: https://issues.apache.org/jira/browse/OOZIE-2548
> Project: Oozie
> Issue Type: Bug
> Components: tests
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Minor
>
> The testcase testLockReaper in TestZKLocksService is unstable.
> The reason is that the test case sleeps for 2 seconds and checks the number of nodes under /locks. The child reaper threads remove ZK nodes after the ZK locks are released. However, 2 seconds is not always enough.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)