[
https://issues.apache.org/jira/browse/ACCUMULO-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13925955#comment-13925955
]
Hung Pham commented on ACCUMULO-2005:
-------------------------------------
Just like everyone else, ie:
username name organization timezone
hpham Hung Pham Cloudera ET (-5 / -4)
> 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, 1.5.2
>
> Attachments: ACCUMULO-2005.v4-1.4.5-SNAPSHOT.patch.txt,
> ACCUMULO-2005.v4.patch.txt, ACCUMULO-2005.v7-1.5.1-SNAPSHOT.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.2#6252)
