Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-17469 IOStatistics Phase II
  3. HADOOP-18617

Make IOStatisticsStore and binding APIs public for use beyond our code



    • Sub-task
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 3.3.5
    • None
    • fs
    • None


      it's really useful to be able to collect iostats in things other than the FS classes -we do it in the S3A and manifest committers.

      But external code -such as the spark committers can't use the methods in {{org.apache.hadoop.fs.statistics.impl))


      Make some classes/interfaces public

      • IOStatisticsBinding
      • IOStatisticsStore
      • IOStatisticsStoreBuilder

      Ideally we should actually move the IOStatisticsStore interface into org.apache.hadoop.fs.statistics and the builder to match -but we can't do that without causing trauma elsewhere (google gcs).

      Strategy there: Add a new interface IOStatisticsCollector in .impl which is then implemented by IOStatisticsStore, and a new builder API which forwards to IOStatisticsStoreBuilder.

      Side issue: we don't make any use of the "clever, elegant functional" bit of DynamicIOStatisticsBuilder/DynamicIOStatistics, where every counter is mapped to a function which is then invoked to get at the atomic longs. It's used in IOStatisticsStoreImpl, but only with AtomicLong and MeanStatistic instances. If we just move to simple maps we will save on lambda-expressions and on lookup overhead. The original intent was something like coda hale metrics where we could add dynamic lookup to other bits of instrumentation; in practise we measure durations and build counts/min/max.




            Unassigned Unassigned
            stevel@apache.org Steve Loughran
            0 Vote for this issue
            2 Start watching this issue