[jira] [Resolved] (HBASE-11359) A simple request timeout interrupt mechanism in HBase server side

["Andrew Kyle Purtell (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/HBASE-11359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Kyle Purtell resolved HBASE-11359.
-----------------------------------------
    Resolution: Incomplete

> A simple request timeout interrupt mechanism in HBase server side
> -----------------------------------------------------------------
>
>                 Key: HBASE-11359
>                 URL: https://issues.apache.org/jira/browse/HBASE-11359
>             Project: HBase
>          Issue Type: Improvement
>          Components: regionserver
>    Affects Versions: 0.99.0, 0.94.20
>            Reporter: Liang Xie
>            Priority: Major
>
> we had introduced a fail fast mechanism in RPC layer, see HBASE-10506.
> But still, a slow latency problem comes from lower HDFS layer could make all HBase handler threads slow, sometimes those handler could hang several seconds. it's meanlingless to continue processing those read/write requests in the valuable rpc handler threads, especially the ones need to do a costly physical read operation or networking activity(write pipeline). A better solution should be similar with twitter MySQL branch: statement-timeout feature. I haven't taken time on figure out weather it's need to break compatibility or not in master, we are using a 0.94 branch, to me it will break if i adding a operation timeout field in every client rpc request.
> so i added a simpler patch using the existing "rpcCall.throwExceptionIfCallerDisconnected()", instrumenting it just before HLog sync and  DFSInputStream read/pread (@readAtOffset). 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)