[
https://issues.apache.org/jira/browse/HBASE-15645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15422349#comment-15422349
]
Phil Yang commented on HBASE-15645:
-----------------------------------
This issue broke source compatibility of Table interface. We need revert the
changing on branch-1.1 and branch-1.2. There is also a bugfix for timeout, so
we should keep the bugfix code.
In git tree this issue is made up of several commits (and revert...), so let me
upload an addendum patch first which we can push to current branch-1.1/1.2
directly. If we have to revert all commits first, I can upload a whole patch.
> 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
> Affects Versions: 2.0.0, 1.3.0, 1.2.1, 1.0.3, 1.1.4
> Reporter: Phil Yang
> Assignee: Phil Yang
> Priority: Critical
> Fix For: 2.0.0, 1.3.0, 1.0.4, 1.4.0, 1.1.5, 1.2.2
>
> Attachments: HBASE-15645-branch-1-v1.patch,
> HBASE-15645-branch-1.0-v1.patch, HBASE-15645-branch-1.1-v1.patch,
> HBASE-15645-branch-1.2-v1.patch, HBASE-15645-v1.patch, HBASE-15645-v2.patch,
> HBASE-15645-v3.patch, HBASE-15645-v4.patch, lable.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)
