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

["Billie Rinaldi (JIRA)" <ji...@apache.org>]

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

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

I'm tempted not to fix this since it seems impossible to satisfy both our requirements: not leaving large files around and not killing the job when the process exits.  Is it too onerous to adjust the mapred.user.jobconf.limit property to allow for jobs with large numbers of ranges?
                
> 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.5.0
>
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira