[
https://issues.apache.org/jira/browse/HADOOP-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hairong Kuang updated HADOOP-2188:
----------------------------------
Attachment: ipc-timeout7.patch
This patch additionally has the following changes:
1. In Server, a call's time stamp is updated when it is received and when its
reponse is sent to the Responder.
2. Client.Connection.in is accessed by only the Connection thread, so its lock
is no longer to be acquired. This eliminates a possible deadlock in the code.
> RPC should send a ping rather than use client timeouts
> ------------------------------------------------------
>
> Key: HADOOP-2188
> URL: https://issues.apache.org/jira/browse/HADOOP-2188
> Project: Hadoop Core
> Issue Type: Improvement
> Components: dfs, ipc
> Affects Versions: 0.16.1
> Reporter: Owen O'Malley
> Assignee: Hairong Kuang
> Fix For: 0.18.0
>
> Attachments: ipc-timeout.patch, ipc-timeout1.patch,
> ipc-timeout2.patch, ipc-timeout3.patch, ipc-timeout4.patch,
> ipc-timeout5.patch, ipc-timeout6.patch, ipc-timeout7.patch, rpc-to.patch
>
>
> Current RPC (really IPC) relies on client side timeouts to find "dead"
> sockets. I propose that we have a thread that once a minute (if the
> connection has been idle) writes a "ping" message to the socket. The client
> can detect a dead socket by the resulting error on the write, so no client
> side timeout is required. Also note that the ipc server does not need to
> respond to the ping, just discard it.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
