hadoop-common-issues mailing list archives

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

     [ https://issues.apache.org/jira/browse/HADOOP-11629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Nauroth updated HADOOP-11629:
-----------------------------------
     Target Version/s: 2.7.0
    Affects Version/s:     (was: 2.6.1)

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