[
https://issues.apache.org/jira/browse/HBASE-20802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527006#comment-16527006
]
stack edited comment on HBASE-20802 at 6/29/18 1:24 AM:
--------------------------------------------------------
Advantage would be we'd promptly shutdown hung rpc.
I want to interrupt it in remotecallfailed that the scp is running...that's why
I want to add an interrupt your to the dispatch api.
was (Author: stack):
Advantage would be we'd promptly shutdown hung rpc.
I want to interrupt it in remotecallfailed ...that's why I want to add this api.
> Add an interruptCall to RemoteProcedureDispatch
> -----------------------------------------------
>
> Key: HBASE-20802
> URL: https://issues.apache.org/jira/browse/HBASE-20802
> Project: HBase
> Issue Type: Sub-task
> Components: amv2
> Reporter: stack
> Priority: Major
>
> Follow-on from the parent. In summary, RPC's to zombie servers can get
> stuck/hang. We'll notice the server has gone non-responsive after a while and
> will effect repair but the RPCs will remain up until they go to their timeout
> (default 3minutes).
> This issue is about adding a means of interrupting an ongoing RPC.
> ServerCrashProcedure does cleanup of any ongoing, unsatisfied
> assigns/unassigns. As part of this cleanup, it could interrupt any
> outstanding RPCs.
> We'd add an interruptCall to the below interface in RemoteProcedureDispatch
> {code}
> public interface RemoteProcedure<TEnv, TRemote> {
> RemoteOperation remoteCallBuild(TEnv env, TRemote remote);
> void remoteCallCompleted(TEnv env, TRemote remote, RemoteOperation
> response);
> void remoteCallFailed(TEnv env, TRemote remote, IOException exception);
> }
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
