hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2835) Make per-job counter limits configurable
Date Fri, 12 Aug 2011 23:07:27 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-2835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13084447#comment-13084447
] 

Arun C Murthy commented on MAPREDUCE-2835:
------------------------------------------

Tom, we purposely kept these not configurable per job (by the user) since they would start
to workaround these limits.

We saw lots of cases where users took down jobs due to this and hence it's only configurable
by admins. OTOH other limits like #groups, counter-name-len etc. are generous enough that
we never had issues, but was done to be super-safe. 

> Make per-job counter limits configurable
> ----------------------------------------
>
>                 Key: MAPREDUCE-2835
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2835
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>    Affects Versions: 0.20.204.0
>            Reporter: Tom White
>            Assignee: Tom White
>             Fix For: 0.20.205.0
>
>         Attachments: MAPREDUCE-2835.patch, MAPREDUCE-2835.patch
>
>
> The per-job counter limits introduced in MAPREDUCE-1943 are fixed, except for the total
number allowed per job (mapreduce.job.counters.limit). It would be useful to make them all
configurable.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message