Mailing-List: contact dev-help@crunch.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@crunch.apache.org
Date: Tue, 12 Aug 2014 04:49:12 +0000 (UTC)
From: "Josh Wills (JIRA)" <jira@apache.org>
To: crunch-dev@incubator.apache.org
Message-ID: <JIRA.12732443.1407373903427.61266.1407818952561@arcas>
In-Reply-To: <JIRA.12732443.1407373903427@arcas>
References: <JIRA.12732443.1407373903427@arcas>
Subject: [jira] [Updated] (CRUNCH-458) Eliminate potentially random MR
 split-point decisions
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Josh Wills updated CRUNCH-458:
------------------------------

    Attachment: CRUNCH-458b.patch

@Gabriel I couldn't think of a better approach, either. ;-)

> Eliminate potentially random MR split-point decisions
> -----------------------------------------------------
>
>                 Key: CRUNCH-458
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-458
>             Project: Crunch
>          Issue Type: Bug
>            Reporter: Josh Wills
>         Attachments: CRUNCH-458.patch, CRUNCH-458b.patch
>
>
> I'm running into a pipeline in which the decision of where to split two dependent jobs seems to be random from run-to-run (I only noticed it b/c one of the runs causes the pipeline to throw an NPE, and the other does not.) I'd like to investigate this and try to eliminate any potential sources of randomness in the way that two dependent GBK operations are split.


--
This message was sent by Atlassian JIRA
(v6.2#6252)