[jira] [Commented] (CRUNCH-292) Hack around Hadoop2's job counter limits

["Vinod Kumar Vavilapalli (JIRA)" <ji...@apache.org>]

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

Vinod Kumar Vavilapalli commented on CRUNCH-292:
------------------------------------------------

These limits are per job, and MR is a user land library now anyways, so you don't need to restart YARN?

> Hack around Hadoop2's job counter limits
> ----------------------------------------
>
>                 Key: CRUNCH-292
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-292
>             Project: Crunch
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.7.0
>            Reporter: Josh Wills
>            Assignee: Josh Wills
>
> Hadoop2 introduces limits in the Counters library that set a maximum of 120 counters per job. These limits are really hard to hack around (for some good reasons); the only real way to override them is to update mapred-site.xml and restart the cluster.
> This presents a challenge for Crunch's in-memory implementation, which uses the Counters library in local mode and can potentially generate well more than 120 counters when testing long pipelines. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)