You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Ravi Prakash (JIRA)" <ji...@apache.org> on 2015/05/18 18:53:00 UTC

[jira] [Resolved] (MAPREDUCE-5074) Remove limits on number of counters and counter groups in MapReduce

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

Ravi Prakash resolved MAPREDUCE-5074.
-------------------------------------
    Resolution: Won't Fix

We can re-open this if we find users compelling us to increase the limits

> Remove limits on number of counters and counter groups in MapReduce
> -------------------------------------------------------------------
>
>                 Key: MAPREDUCE-5074
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-5074
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mr-am, mrv2
>    Affects Versions: 3.0.0, 2.0.3-alpha, 0.23.6
>            Reporter: Ravi Prakash
>
> Can we please consider removing limits on the number of counters and counter groups now that it is all user code? Thanks to the much better architecture of YARN in which there is no single Job Tracker we have to worry about overloading, I feel we should do away with this (now arbitrary) constraint on users' capabilities. Thoughts?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)