hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11629) WASB filesystem should not start BandwidthGaugeUpdater if fs.azure.skip.metrics set to true
Date Tue, 24 Feb 2015 23:25:04 GMT

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

Hadoop QA commented on HADOOP-11629:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12700601/HADOOP-11629.1.patch
  against trunk revision 9a37247.

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
tests.
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:green}+1 javac{color}.  The applied patch does not increase the total number of
javac compiler warnings.

    {color:green}+1 javadoc{color}.  There were no new javadoc warning messages.

    {color:green}+1 eclipse:eclipse{color}.  The patch built with eclipse:eclipse.

    {color:green}+1 findbugs{color}.  The patch does not introduce any new Findbugs (version
2.0.3) warnings.

    {color:green}+1 release audit{color}.  The applied patch does not increase the total number
of release audit warnings.

    {color:green}+1 core tests{color}.  The patch passed unit tests in hadoop-tools/hadoop-azure.

Test results: https://builds.apache.org/job/PreCommit-HADOOP-Build/5771//testReport/
Console output: https://builds.apache.org/job/PreCommit-HADOOP-Build/5771//console

This message is automatically generated.

> 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
>         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)

Mime
View raw message