Uploaded image for project: 'Accumulo'
  1. Accumulo
  2. ACCUMULO-4778

Resolving table name to table id is expensive

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 1.7.3, 1.8.1
    • 1.9.0
    • None

    Description

      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.

      Attachments

        Issue Links

          Activity

            People

              milleruntime Michael Miller
              kturner Keith Turner
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 4h 50m
                  4h 50m