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

Hadoop QA commented on HDFS-10932:
----------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  4s{color} 
| {color:red} HDFS-10932 does not apply to trunk. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HDFS-10932 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12831020/HDFS-10932.001.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-HDFS-Build/16936/console |
| Powered by | Apache Yetus 0.4.0-SNAPSHOT   http://yetus.apache.org |


This message was automatically generated.



> 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.001.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
(v6.3.4#6332)

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

Reply via email to