hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tom White (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-3936) Clients should not enforce counter limits
Date Thu, 30 Aug 2012 13:58:07 GMT

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

Tom White updated MAPREDUCE-3936:

    Target Version/s: 1.1.0, 2.1.0-alpha  (was: 1.1.0)
            Assignee: Tom White
             Summary: Clients should not enforce counter limits   (was: Improve counter limits
behaviour in 1.x)

This problem affects trunk/branch-2 as well, so changing the summary.

I think this can be fixed by changing the code so that limits are only enforced at source
- i.e. when user task code is incrementing counters. In other cases - when counters are deserialized,
or when manipulating counters in the client - there is no need to check limits (and indeed
a mixed configuration will cause problems as mentioned in the description).
> Clients should not enforce counter limits 
> ------------------------------------------
>                 Key: MAPREDUCE-3936
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3936
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: mrv1
>            Reporter: Tom White
>            Assignee: Tom White
> The code for enforcing counter limits (from MAPREDUCE-1943) creates a static JobConf
instance to load the limits, which may throw an exception if the client limit is set to be
lower than the limit on the cluster (perhaps because the cluster limit was raised from the

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

View raw message