[
https://issues.apache.org/jira/browse/HBASE-8581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-8581:
-------------------------
Attachment: 8581.txt
Here is a patch to restore what we had in 0.94 passing down an operation
timeout.
{code}
1 In HTable, allow setting an operation timeout on meta. Needed testing.
2
3 In ServerCallable, do a little refactor so cleaner around checking for
timeout.
4
5 In RpcClient, add back the getRpcTimeout that takes a default timeout and
6 returns minimum of default rpc timeout and whatever is set in the thread
local.
7 Call this new method on setup of a 'Service' the first time (In 0.94 it was
8 called when we set up a new proxy, which equates to about the same thing).
9
10 In TestClientNoCluster, add a test that verifies we get
SocketTimeoutException
11 when the operation timeout is reached rather than a retries exhausted
12 exception which is what we were getting when before this patch.
13
14 Add a log4j.properties to hbase-client so we get a bit of logging.
{code}
> rpc refactor dropped passing the operation timeout through to the rpcclient
> ---------------------------------------------------------------------------
>
> Key: HBASE-8581
> URL: https://issues.apache.org/jira/browse/HBASE-8581
> Project: HBase
> Issue Type: Bug
> Reporter: stack
> Assignee: stack
> Attachments: 8581.txt
>
>
> jd was poking and noticed that we were not passing the operation timeout down
> as rpc timeout as we used to in 0.94. Let me fix.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
