Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Tue, 24 Feb 2015 19:47:04 +0000 (UTC)
From: "shanyu zhao (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12777271.1424807195000.3744.1424807224795@Atlassian.JIRA>
In-Reply-To: <JIRA.12777271.1424807195000@Atlassian.JIRA>
References: <JIRA.12777271.1424807195000@Atlassian.JIRA>
 <JIRA.12777271.1424807195035@arcas>
Subject: [jira] [Created] (HADOOP-11629) WASB filesystem should not start
 BandwidthGaugeUpdater if fs.azure.skip.metrics set to true
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

shanyu zhao created HADOOP-11629:
------------------------------------

             Summary: WASB filesystem should not start BandwidthGaugeUpdater if fs.azure.skip.metrics set to true
                 Key: HADOOP-11629
                 URL: https://issues.apache.org/jira/browse/HADOOP-11629
             Project: Hadoop Common
          Issue Type: Bug
          Components: tools
    Affects Versions: 2.6.1
            Reporter: shanyu zhao
            Assignee: shanyu zhao


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.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)