Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 26 Feb 2015 15:26:09 +0000 (UTC)
From: "Hudson (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12777271.1424807195000.23211.1424964369376@Atlassian.JIRA>
In-Reply-To: <JIRA.12777271.1424807195000@Atlassian.JIRA>
References: <JIRA.12777271.1424807195000@Atlassian.JIRA>
 <JIRA.12777271.1424807195035@arcas>
Subject: [jira] [Commented] (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


    [ https://issues.apache.org/jira/browse/HADOOP-11629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338550#comment-14338550 ] 

Hudson commented on HADOOP-11629:
---------------------------------

FAILURE: Integrated in Hadoop-Mapreduce-trunk #2066 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/2066/])
HADOOP-11629. WASB filesystem should not start BandwidthGaugeUpdater if fs.azure.skip.metrics set to true. Contributed by Shanyu Zhao. (cnauroth: rev 5731c0e0d08c3048fafdf62a14ca7611be4df5d7)
* hadoop-tools/hadoop-azure/src/main/java/org/apache/hadoop/fs/azure/AzureNativeFileSystemStore.java
* hadoop-common-project/hadoop-common/CHANGES.txt


> 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
>            Reporter: shanyu zhao
>            Assignee: shanyu zhao
>             Fix For: 2.7.0
>
>         Attachments: HADOOP-11629.1.patch, HADOOP-11629.patch
>
>
> 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)