accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Billie Rinaldi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-507) Large amount of ranges can prevent job from kicking off
Date Wed, 23 Jan 2013 00:10:12 GMT

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

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

I looked into it.  What I saw in the code led me to believe that the size restriction is on
the entire job submit directory, which contains a file where the ranges are written after
they are obtained from getSplits.  However, the code was not very transparent, so it's possible
that I made incorrect conclusions.  Anyone else feel like verifying it one way or the other?
                
> 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

Mime
View raw message