Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@crunch.apache.org
Date: Fri, 1 Nov 2013 16:57:27 +0000 (UTC)
From: "Josh Wills (JIRA)" <jira@apache.org>
To: crunch-dev@incubator.apache.org
Message-ID: <JIRA.12677106.1383325039356.7569.1383325047359@arcas>
In-Reply-To: <JIRA.12677106.1383325039356@arcas>
References: <JIRA.12677106.1383325039356@arcas>
Subject: [jira] [Created] (CRUNCH-292) Hack around Hadoop2's job counter
 limits
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Josh Wills created CRUNCH-292:
---------------------------------

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