Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Thu, 31 Oct 2013 17:17:20 +0000 (UTC)
From: "Billie Rinaldi (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12549166.1333377788947.1715.1383239840142@arcas>
In-Reply-To: <JIRA.12549166.1333377788947@arcas>
References: <JIRA.12549166.1333377788947@arcas>
Subject: [jira] [Commented] (ACCUMULO-507) Large amount of ranges can
 prevent job from kicking off
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Billie Rinaldi commented on ACCUMULO-507:
-----------------------------------------

I'm a little uncomfortable with not knowing whether this has a chance of causing your job to fail, if it's the case that under some conditions a job is submitted more than once.  If I figure it out today I'll commit, and otherwise push it off.  It doesn't seem like people are clamoring for this change given that there's a workaround.

> Large amount of ranges can prevent job from kicking off
> -------------------------------------------------------
>
>                 Key: ACCUMULO-507
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-507
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 1.3.5
>            Reporter: John Vines
>            Assignee: Billie Rinaldi
>            Priority: Minor
>              Labels: mapreduce
>             Fix For: 1.6.0
>
>         Attachments: ACCUMULO-507.patch
>
>
> We use the various ranges a user provides to create splits. Those get read when the job is submitted by the client. On the client side, those ranges are used to get all of the splits, and then the job is started. If the configuration is too large, the job will fail to submit (this size is configurable, but that's besides the point). We should look into clearing the ranges out of the jobconf if it's large to prevent this error, since at this point the ranges are no longer needed in the configuration.


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