incubator-ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-1702) Ambari/GSInstallers need to set the value of mapred.jobtracker.completeuserjobs.maximum
Date Thu, 18 Apr 2013 22:24:13 GMT

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

Siddharth Wagle updated AMBARI-1702:
------------------------------------

    Summary: Ambari/GSInstallers need to set the value of mapred.jobtracker.completeuserjobs.maximum
 (was: Ambari/GSInstallers need to set the value of mapred.jobtracker.completeuserjobs.maximum=100)
    
> Ambari/GSInstallers need to set the value of mapred.jobtracker.completeuserjobs.maximum
> ---------------------------------------------------------------------------------------
>
>                 Key: AMBARI-1702
>                 URL: https://issues.apache.org/jira/browse/AMBARI-1702
>             Project: Ambari
>          Issue Type: Bug
>          Components: controller
>    Affects Versions: 1.2.2
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>             Fix For: 1.3.0
>
>         Attachments: AMBARI-1702-1.patch, AMBARI-1702.patch
>
>
> mapred.jobtracker.completeuserjobs.maximum is currently set to 0. This causes issues
with failed(/successful) jobs from pig and other job submitters because the references to
the failed job is cleared up asap in jobtracker preventing one from accessing the failure
reason. This value should be bumped up to about 100 according to the MapReduce team.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message