[ https://issues.apache.org/jira/browse/HBASE-15645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Yang updated HBASE-15645: ------------------------------ Attachment: HBASE-15645-v1.patch Upload patch. In HTable for each rpcCallerFactory.<Result> newCaller, add a rpcTimeout in it. Timeout for scan and Table interface is not changed, I think we can open another two issues and have more discussion. > hbase.rpc.timeout is not used in operations of HTable > ----------------------------------------------------- > > 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 > Attachments: HBASE-15645-v1.patch > > > 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)