[HBASE-15645] hbase.rpc.timeout is not used in operations of HTable

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.3.0, 1.2.1, 1.0.3, 1.1.4, 2.0.0
• Fix Version/s: 1.3.0, 1.0.4, 1.1.5, 1.2.2, 2.0.0
• Hadoop Flags: Reviewed

Release Note

Fixes regression where hbase.rpc.timeout configuration was ignored in branch-1.0+

Adds new methods setOperationTimeout, getOperationTimeout, setRpcTimeout, and getRpcTimeout to Table. In branch-1.3+ they are public interfaces and in 1.0-1.2 they are labeled as @InterfaceAudience.Private.

Adds hbase.client.operation.timeout to hbase-default.xml with default of 1200000

• Assignee: Phil Yang
• Reporter: Phil Yang
• Created: 13/Apr/16 15:04
• Updated: 22/Feb/18 20:58
• Resolved: 27/Apr/16 17:08

Description

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():

TEST_UTIL.getConfiguration().setLong(HConstants.HBASE_RPC_TIMEOUT_KEY, 3000);

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.

Issue Links

• breaks: HBASE-16420 Fix source incompatibility of Table interface
• Is contained by: HBASE-18223 Track the effort to improve/bug fix read replica feature
• is related to: HBASE-17449 Add explicit document on different timeout settings
• links to: review board