accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Havanki (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-1789) Increase test timeouts for Accumulo 1.5.x
Date Tue, 22 Oct 2013 17:36:41 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13802050#comment-13802050
] 

Bill Havanki commented on ACCUMULO-1789:
----------------------------------------

I had generally increased some timeouts by a factor of two to three. The
maxRuntime value of 120 in JavaTest was one I had to increase to 360 for
many tests. There were also onesy-twosy changes I had to make in
SimpleBalancerFairness, DeleteRowsSplitTest, MergeTest, and
MetadataMaxFiles.

However, based on a comment by Steve Loughran, I decided to add the ability
to scale the timeouts at run time instead of just poke in what worked for
me. This way, the original timeouts stay there, but anyone can scale them
up for their particular environment.






-- 
// - - -
// Bill Havanki
// Solutions Architect, Cloudera
// - - -


> Increase test timeouts for Accumulo 1.5.x
> -----------------------------------------
>
>                 Key: ACCUMULO-1789
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1789
>             Project: Accumulo
>          Issue Type: Test
>          Components: test
>    Affects Versions: 1.5.0
>            Reporter: Bill Havanki
>            Assignee: Bill Havanki
>            Priority: Minor
>              Labels: test
>
> In our test environment we've found that increasing some timeouts for Accumulo 1.5.x
tests lets them complete more reliably. They include: CreateAndUseTest, BloomFilterTest, SimpleBalancerFairness,
DeleteRowsSplitTest, MergeTest.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message