[jira] [Commented] (ACCUMULO-507) Large amount of ranges can prevent job from kicking off

["John Vines (JIRA)" <ji...@apache.org>]

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

John Vines commented on ACCUMULO-507:
-------------------------------------

[~billie.rinaldi@gmail.com] Is this patch good to commit (after updating) or do we need more discussion here?

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