You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Hung Pham (JIRA)" <ji...@apache.org> on 2014/03/05 15:11:43 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=13920875#comment-13920875 ]
Hung Pham commented on ACCUMULO-2005:
-------------------------------------
Hi Sean,
Sorry, I've been late on emails. I've on-site with no internet access
until now. Just caught up and saw this. Yes I'd like to go through
rebasing exercise myself (to learn), but I probably won't be able to touch
this til this weekend. Is that ok? If yes, please show me the steps.
Thanks,
Hung
> 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.2#6252)