[
https://issues.apache.org/jira/browse/HBASE-15645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15242891#comment-15242891
]
Phil Yang commented on HBASE-15645:
-----------------------------------
The timeout settings controlled by Configuration is determined when HTable
instance created, in HTable we have setOperationTimeout method to change the
timeout for this HTable instance, but in master Table is the new API for users,
and setOperationTimeout is not in it. The only way is
connection.getConfiguration().setInt(xxx) and then getTable, which is not
convenience if users want to change the timeout after Table created. So I think
setOperationTimeout(and setRpcTimeout) should be added in Table interface.
> hbase.rpc.timeout is not used in get operation
> ----------------------------------------------
>
> Key: HBASE-15645
> URL: https://issues.apache.org/jira/browse/HBASE-15645
> Project: HBase
> Issue Type: Bug
> Reporter: Phil Yang
> Assignee: Phil Yang
> Priority: Critical
>
> While fixing HBASE-15593, I find that we use operationTimeout as the timeout
> of Get operation rpc call (hbase.client.scanner.timeout.period is used in
> scan rpc), not the hbase.rpc.timeout.
> This can be verified by add one line in TestHCM.setUpBeforeClass():
> {code}
> TEST_UTIL.getConfiguration().setLong(HConstants.HBASE_RPC_TIMEOUT_KEY, 3000);
> {code}
> and then run testOperationTimeout(), the test passes but it should have
> failed because we should get rpc timeout first after 3 seconds then client
> should retry and timeout again and again until operationTimeout or max
> retries reached.
> If I port this test to 0.98, it will fail as expected.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
