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] [Resolved] (ACCUMULO-507) Large amount of ranges can prevent job from kicking off
Date Fri, 01 Nov 2013 21:59:17 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Billie Rinaldi resolved ACCUMULO-507.
-------------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 1.6.0)

I'm going to close this.  In Hadoop 2, the property limiting the conf size no longer exists
(which doesn't necessarily mean that there is no limit, just that I haven't found it).  If
someone finds the Hadoop 1 workaround to be insufficient, we can revisit this then.

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

Mime
View raw message