Uploaded image for project: 'Hadoop Common'
  1. Hadoop Common
  2. HADOOP-11629

WASB filesystem should not start BandwidthGaugeUpdater if fs.azure.skip.metrics set to true

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.7.0
    • tools
    • None
    • Reviewed

    Description

      In Hadoop-11248 we added configuration "fs.azure.skip.metrics". If set to true, we do not register Azure FileSystem metrics with the metrics system. However, BandwidthGaugeUpdater object is still created in AzureNativeFileSystemStore, resulting in unnecessary threads being spawned.

      Under heavy load the system could be busy dealing with these threads and GC has to work on removing the thread objects. E.g. When multiple WebHCat clients submitting jobs to WebHCat server, we observed that the WebHCat server spawns ~400 daemon threads, which slows down the server and sometimes cause timeout.

      Attachments

        1. HADOOP-11629.patch
          2 kB
          shanyu zhao
        2. HADOOP-11629.1.patch
          3 kB
          shanyu zhao

        Activity

          People

            shanyu shanyu zhao
            shanyu shanyu zhao
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: