You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Sean Busbey (JIRA)" <ji...@apache.org> on 2013/12/12 17:37:07 UTC

[jira] [Commented] (ACCUMULO-2005) Provide a scaling factor for mapred.task.timeout inside functional test's RunTests.java

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

Sean Busbey commented on ACCUMULO-2005:
---------------------------------------

we should also make sure that such a timeout scaling argument also results in the same factor being passed to the individual tests.

> Provide a scaling factor for mapred.task.timeout inside functional test's RunTests.java
> ---------------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-2005
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2005
>             Project: Accumulo
>          Issue Type: Test
>          Components: test
>    Affects Versions: 1.4.4, 1.5.0
>            Reporter: Hung Pham
>            Priority: Minor
>
> The MR option for running functional tests ($ACCUMULO_HOME/test/system/auto) fails with a mapred timeout currently set at 480 secs (8*60*1000).    A flag or argument for scaling mapred.task.timeout inside RunTests.java (ie, a number that influence the 8 in  8*60*1000) needs to be in place to allow scaling up or down mapred.task.timeout as needed.     This is similar to ACCUMULO-1829.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)