Accumulo
  1. Accumulo
  2. ACCUMULO-2837

Scanning empty table can be optimized

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Trivial Trivial
    • Resolution: Unresolved
    • Affects Version/s: 1.6.0
    • Fix Version/s: 1.7.0, 1.6.3
    • Component/s: None
    • Labels:
      None

      Description

      I wrote an application that repeatedly scanned random rows in an empty table at one point. It did not know the table was empty. I was jstacking the tserver and repeatedly saw stack traces in a few places in the code.

      • the audit canScan method
      • DefaultConfiguration.get
      • Kept seeing Password token ungziping the password??????

      After fixing all of these issues (except for system token) I ran a simple test I saw times go from ~1.7s to ~1.3s for a simple test I wrote to recreate this issue.

      I am not sure how much of an impact the gziping the password has. I was just sampling the stack traces manually. I seems like I saw the password token gzip stack traces less frequently, but I did catch it multiple jstack calls.

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Keith Turner
            Reporter:
            Keith Turner
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development