[
https://issues.apache.org/jira/browse/ACCUMULO-4778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Miller resolved ACCUMULO-4778.
--------------------------------------
Resolution: Fixed
> Resolving table name to table id is expensive
> ---------------------------------------------
>
> Key: ACCUMULO-4778
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4778
> Project: Accumulo
> Issue Type: Bug
> Affects Versions: 1.7.3, 1.8.1
> Reporter: Keith Turner
> Assignee: Michael Miller
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.7.4, 1.9.0, 2.0.0
>
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> I was running a Fluo test application and profiling the tablet server and
> Fluo worker. The Fluo worker does lots small scans against Accumulo.
> Resolving table names to ids (which is done for each scan) was expensive
> enough to make a significant showing in the profiling data.
> I looked that the 1.8 code and it does the following to resolve a table name :
> * reads over all cached table ids in zookeeper putting them in a treemap
> * does a lookup in the treemap
> Ideally the client code would keep a cache of name to id mappings and
> invalidate them when something changes in zookeeper. The data in zookeeper
> is stored by id, so it does need to be inverted to lookup by name.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
