hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Kanter (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5856) Counter limits always use defaults even if JobClient is given a different Configuration
Date Sat, 10 May 2014 22:11:42 GMT

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

Robert Kanter updated MAPREDUCE-5856:
-------------------------------------

    Resolution: Duplicate
        Status: Resolved  (was: Patch Available)

MAPREDUCE-5875 fixes this use case, as well as some others.

> Counter limits always use defaults even if JobClient is given a different Configuration
> ---------------------------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5856
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5856
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 2.3.0, 2.4.0
>            Reporter: Robert Kanter
>            Assignee: Robert Kanter
>         Attachments: MAPREDUCE-5856.patch
>
>
> If you have a job with more than the default number of counters (i.e. > 120), and
you create a JobClient with a Configuration where the default is increased (e.g. 500), then
JobClient will throw this Exception:
> {noformat}
> org.apache.hadoop.mapreduce.counters.LimitExceededException: Too many counters: 121 max=120
> {noformat}



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

Mime
View raw message