You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Aaron Kimball (JIRA)" <ji...@apache.org> on 2008/11/02 04:35:44 UTC

[jira] Commented: (HADOOP-4552) Deadlock in RPC Server

    [ https://issues.apache.org/jira/browse/HADOOP-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12644555#action_12644555 ] 

Aaron Kimball commented on HADOOP-4552:
---------------------------------------

As the reporter of the thread mentioned: we've been running with this patch now for a few days and haven't had to restart mapreduce again yet. This seems to have fixed the issue. (Thanks!)

> 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
>         Attachments: HADOOP-4552.patch
>
>
> 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.