[
https://issues.apache.org/jira/browse/CRUNCH-292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811475#comment-13811475
]
Vinod Kumar Vavilapalli commented on CRUNCH-292:
------------------------------------------------
Okie.
But just calling Limits.init(Configuration conf) with a different value for
that conf property should work? Unless you need thread safety too..
> 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
> Attachments: CRUNCH-292.patch
>
>
> 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)
