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

["Hung Pham (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ACCUMULO-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hung Pham updated ACCUMULO-2005:
--------------------------------

    Attachment: ACCUMULO-2005.v7.patch.txt

ACCUMULO-2005.v7.patch.txt includes following:

1)  Annotation Parameter strTimeoutFactor was changed from String to Integer, intTimeoutFactor with a default value of 1.
2)  static private Integer timeoutFactor was eliminated and opts.intTimeoutFactor was used to assigned directly to static final String TIMEOUT_FACTOR.
3)  NumberFormatException was no longer needed.

> 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
>            Assignee: Hung Pham
>            Priority: Minor
>             Fix For: 1.4.5
>
>         Attachments: ACCUMULO-2005.v4.patch.txt, ACCUMULO-2005.v7.patch.txt
>
>
> 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.5#6160)