Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
From: joshelser <git@git.apache.org>
To: dev@accumulo.apache.org
Reply-To: dev@accumulo.apache.org
References: <git-pr-25-accumulo@git.apache.org>
In-Reply-To: <git-pr-25-accumulo@git.apache.org>
Subject: [GitHub] accumulo pull request: ACCUMULO-3602 BatchScanner
 optimization for...
Content-Type: text/plain
Message-Id: <20150408205852.341D8E1118@git1-us-west.apache.org>
Date: Wed,  8 Apr 2015 20:58:52 +0000 (UTC)

Github user joshelser commented on the pull request:

    https://github.com/apache/accumulo/pull/25#issuecomment-91035731
  
    >  It seems like this change could encourage users to pass many ranges as configuration for the map reduce job. This could cause memory exhaustion for the job tracker. 
    
    Agreed, but is this a new issue? If anything, it this these changes would reduce the total number of objects in memory (as a split could contain multiple ranges whereas previously it was 1:1). I remember hearing about solutions that use HDFS as a mechanism for supporting large numbers of ranges instead of the Configuration. Either way, I think the current changes are a good addition but just not in scope to address the bigger issue you brought up.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---