[
https://issues.apache.org/jira/browse/HADOOP-11629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14338430#comment-14338430
]
Hudson commented on HADOOP-11629:
---------------------------------
FAILURE: Integrated in Hadoop-Hdfs-trunk #2048 (See
[https://builds.apache.org/job/Hadoop-Hdfs-trunk/2048/])
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)
