hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gera Shegalov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5875) Make Counter limits consistent conf across JobClient, MRAppMaster, and YarnChild
Date Sun, 15 Jun 2014 01:06:02 GMT

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

Gera Shegalov updated MAPREDUCE-5875:
-------------------------------------

    Attachment: MAPREDUCE-5875.v07.patch

Jobs run MiniMRCluster get an incorrect history tracking URL and there can be a delay when
history tracking URL is set via unregister. The latter can be solved by waiting but I think
it's sufficient to simply log the error. It may be better to do it only in the test case and
throw an exception in production code. Suggestions?

> Make Counter limits consistent conf across JobClient, MRAppMaster, and YarnChild
> --------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5875
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5875
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: applicationmaster, client, task
>    Affects Versions: 2.4.0
>            Reporter: Gera Shegalov
>            Assignee: Gera Shegalov
>         Attachments: MAPREDUCE-5875.v01.patch, MAPREDUCE-5875.v02.patch, MAPREDUCE-5875.v03.patch,
MAPREDUCE-5875.v04.patch, MAPREDUCE-5875.v05.patch, MAPREDUCE-5875.v06.patch, MAPREDUCE-5875.v07.patch
>
>
> Currently, counter limits "mapreduce.job.counters.*" handled by {{org.apache.hadoop.mapreduce.counters.Limits}}
are initialized asymmetrically: on the client side, and on the AM, job.xml is ignored whereas
it's taken into account in YarnChild.
> It would be good to make the Limits job-configurable, such that max counters/groups is
only increased when needed. With the current Limits implementation relying on static constants,
it's going to be challenging for tools that submit jobs concurrently  without resorting to
class loading isolation.
> The patch that I am uploading is not perfect but demonstrates the issue. 



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message