accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Billie Rinaldi (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-507) Large amount of ranges can prevent job from kicking off
Date Thu, 31 Oct 2013 17:17:20 GMT


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

View raw message