hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantin Shvachko (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-4552) Deadlock in RPC Server
Date Tue, 11 Nov 2008 02:09:44 GMT

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

Konstantin Shvachko commented on HADOOP-4552:

+1 This looks right to me.
I would include in this jira more information about the issue, otherwise it is hard to understand
the problem.
The stack trace mentioned in the mail-thread should be attached and a link to the Selector
documentation would be helpful.

> 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
>             Fix For: 0.19.1, 0.20.0
>         Attachments: deadlock-example.txt, 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.

View raw message