accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Updated] (ACCUMULO-4778) Resolving table name to table id is expensive
Date Wed, 24 Jan 2018 15:33:00 GMT


ASF GitHub Bot updated ACCUMULO-4778:
    Labels: pull-request-available  (was: )

> Resolving table name to table id is expensive
> ---------------------------------------------
>                 Key: ACCUMULO-4778
>                 URL:
>             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: 2.0.0
> 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
> 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

View raw message