[
https://issues.apache.org/jira/browse/HADOOP-11295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14306746#comment-14306746
]
Ming Ma commented on HADOOP-11295:
----------------------------------
Thanks, [~daryn]. Yes, we can change the shutdown order from the current "
handlers -> listener -> readers -> responder" to "listener -> readers ->
handlers -> responder". But I don't know if it makes much of difference given
the server is being shutdown anyway. If you meant draining the RPC queue before
the server is shutdown, then we will have to wait for all requests to be
processed by handlers and responder; it might not be worthy it. Thoughts?
> RPC Server Reader thread can't shutdown if RPCCallQueue is full
> ---------------------------------------------------------------
>
> Key: HADOOP-11295
> URL: https://issues.apache.org/jira/browse/HADOOP-11295
> Project: Hadoop Common
> Issue Type: Bug
> Reporter: Ming Ma
> Assignee: Ming Ma
> Attachments: HADOOP-11295-2.patch, HADOOP-11295-3.patch,
> HADOOP-11295-4.patch, HADOOP-11295-5.patch, HADOOP-11295.patch
>
>
> If RPC server is asked to stop when RPCCallQueue is full, {{reader.join()}}
> will just wait there. That is because
> 1. The reader thread is blocked on {{callQueue.put(call);}}.
> 2. When RPC server is asked to stop, it will interrupt all handler threads
> and thus no threads will drain the callQueue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
