hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anu Engineer (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-10932) Ozone : fix XceiverClient slow shutdown
Date Sat, 01 Oct 2016 00:14:20 GMT

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

Anu Engineer updated HDFS-10932:
      Resolution: Fixed
    Hadoop Flags: Reviewed
          Status: Resolved  (was: Patch Available)

[~vagarychen] Thank you for finding and fixing the issue. I have committed this to the feature

> Ozone : fix XceiverClient slow shutdown
> ---------------------------------------
>                 Key: HDFS-10932
>                 URL: https://issues.apache.org/jira/browse/HDFS-10932
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Chen Liang
>            Assignee: Chen Liang
>         Attachments: HDFS-10932-HDFS-7240.002.patch, HDFS-10932-HDFS-7240.002.patch,
> Currently {{XceiverClient}} is the underlying entity of {{DistributedStorageHandler.newKeyWriter()}}
and {{DistributedStorageHandler.newKeyReader()}}  for making call to container for read/write.
When {{XceiverClient}} gets closed, {{group.shutdownGracefully()}} gets called, which is an
asynchronous call. 
> A problem is that this asynchronous call has default quiet period of 2 seconds before
it actually shutdown, so if we have a burst of read/write calls, we would end up having threads
created faster than they got terminated, reaching system limit at some point.
> Ideally, this needs to be fixed with cached clients instead of creating new thread each
time. This JIRA only tries to give a temporary fix for the time being.
> Thanks [~anu] for the offline discussion.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message