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

["Sean Busbey (JIRA)" <ji...@apache.org>]

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

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

The patch applies well to 1.4.5-SNAPSHOT. Unfortunately, argument handling changed substantially in 1.5.x, so the changes won't impact there.

Could you checkout 1.5.1-SNAPSHOT and take a look at making your changes work with that version of the code? You'd just add another patch for that branch (e.g. ACCUMULO-2005.v4-1.5.1-SNAPSHOT.patch).

If you don't think you'll have time, just drop a note here and we'll get someone to handle it when they have time.

> 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
>
>
> 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)