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

Consider consolidation of "timing" classes

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Not A Problem
    • None
    • None
    • client, master, tserver

    Description

      We have a number of "timing" classes in or used by the codebase

      • org.apache.accumulo.core.util.StopWatch
      • org.apache.accumulo.core.util.OpTimer
      • Traces
      • Guava's Stopwatch

      I'm assuming that consolidation of all of the timings into Traces would be the best (assuming that if we care about the timing of a given operation implies that twe would also care about the timing of the "bigger picture").

      If we can remove some of our timer classes, that would be great. Not suggesting that we forcibly prevent the use of Stopwatches/TImers in the codebase entirely – just where it makes sense.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. ACCUMULO-1242 Consistent logging

          • Major - Major loss of function.
          • Resolved

          Activity

            People

              Unassigned Unassigned
              elserj Josh Elser
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: