[
https://issues.apache.org/jira/browse/HADOOP-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raghu Angadi updated HADOOP-4552:
---------------------------------
Component/s: ipc
Description:
RPC server could get into a deadlock especially when clients or server are
network starved. This is a deadlock between RPC responder thread trying to
check if there are any connection to be purged and RPC handler trying to queue
a response to be written by the responder.
This was first observed [this
thread|http://www.nabble.com/TaskTrackers-disengaging-from-JobTracker-to20234317.html].
was:
RPC server could get into a deadlock especially when clients or server are
network starved. This is a deadlock between RPC responder thread trying to
check if there are any connection to be purged and RPC handler trying to queue
a response to be written by the responder.
This was first observed [this
thread|http://www.nabble.com/TaskTrackers-disengaging-from-JobTracker-to20234317.html].
> Deadlock in RPC Server
> ----------------------
>
> Key: HADOOP-4552
> URL: https://issues.apache.org/jira/browse/HADOOP-4552
> Project: Hadoop Core
> Issue Type: Bug
> Components: ipc
> Affects Versions: 0.16.3
> Reporter: Raghu Angadi
> Assignee: Raghu Angadi
>
> RPC server could get into a deadlock especially when clients or server are
> network starved. This is a deadlock between RPC responder thread trying to
> check if there are any connection to be purged and RPC handler trying to
> queue a response to be written by the responder.
> This was first observed [this
> thread|http://www.nabble.com/TaskTrackers-disengaging-from-JobTracker-to20234317.html].
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
