crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Wills (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CRUNCH-292) Hack around Hadoop2's job counter limits
Date Fri, 01 Nov 2013 17:35:26 GMT

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

Josh Wills commented on CRUNCH-292:
-----------------------------------

Looks like it was fixed here, for 2.3.0: https://issues.apache.org/jira/browse/MAPREDUCE-5487

We'd also need to figure out a way to make the call compatible w/the Hadoop 1.0 APIs.

> 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)

Mime
View raw message