hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Douglas (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-3936) Clients should not enforce counter limits
Date Fri, 08 May 2015 22:23:02 GMT

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

Chris Douglas updated MAPREDUCE-3936:
-------------------------------------
    Status: Open  (was: Patch Available)

Patch no longer applies.

In the context of YARN-2928, presumably the timeline server can handle unlimited counters.
The limit can already be set very high... is this still relevant for MR? If nobody plans to
work on this, please close as "later" or "won't fix"

> 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
>              Labels: BB2015-05-TBR
>         Attachments: MAPREDUCE-3936.patch, MAPREDUCE-3936.patch
>
>
> 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
default).



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

Mime
View raw message