Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Mon, 31 Aug 2015 21:15:47 +0000 (UTC)
From: "Eric Newton (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12860698.1441031669000.214691.1441055747557@Atlassian.JIRA>
In-Reply-To: <JIRA.12860698.1441031669000@Atlassian.JIRA>
References: <JIRA.12860698.1441031669000@Atlassian.JIRA>
 <JIRA.12860698.1441031669995@arcas>
Subject: [jira] [Commented] (ACCUMULO-3982) Add LRU mechanism to address
 memory concerns and possibly pre-fetch Tablet Locations.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eric Newton commented on ACCUMULO-3982:
---------------------------------------

The implementation issues that [~kturner] mentioned over on ACCUMULO-3982:
 * pre-fetch
 * prioritize
 * concurrency

The user of the locator doesn't really need sorted iteration.


> Add LRU mechanism to address memory concerns and possibly pre-fetch Tablet Locations.
> -------------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-3982
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3982
>             Project: Accumulo
>          Issue Type: New Feature
>          Components: client, tserver
>    Affects Versions: 1.6.3, 1.7.0, 1.8.0
>            Reporter: marco polo
>            Assignee: Eric Newton
>             Fix For: 1.8.0
>
>
> On larger systems, especially those of which may split frequently, I've seen churn in the TabletLocator caches. Could we possibly pre-fetch entries for a table so that we don't constantly access the metadata table for tablet locations. 
> Additionally, instead of clearing the cache in the case of a miss or failure, could we simply update those entries in the cache? If we do this we may minimize cache misses overall and the need to scan the meta data table. If need be, we could have a threshold before clearing the cache entirely if people see the need for that.
> It would also be helpful to add an LRU cache ( or maybe even priority based LRU cache ). In ACCUMULO-3549, we added a cache clear to TabletServer to avoid overwhelming memory. An LRU cache might address this concern and make the clear cache call unnecessary.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)