[
https://issues.apache.org/jira/browse/PHOENIX-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14681924#comment-14681924
]
Lukas Lalinsky commented on PHOENIX-269:
----------------------------------------
Sorry for commenting on an old ticket, but I was wondering about this.
I see it has been fixed back in 2013 here
https://github.com/forcedotcom/phoenix/pull/166, but I don't see the change in
the apache/phoenix repo. Has it been intentionally removed or just missed with
the switch from salesforce's repo to apache?
> set hbase.rpc.timeout when necessary
> ------------------------------------
>
> Key: PHOENIX-269
> URL: https://issues.apache.org/jira/browse/PHOENIX-269
> Project: Phoenix
> Issue Type: Task
> Reporter: Raymond Liu
>
> when phoenix.query.timeoutMs is set to a value large than hbase.rpc.timeout.
> we should also modify hbase.rpc.timeout for this query too. otherwise, as an
> hbase client, phoenix query will still timeout, and this setting won't
> achieve it's goal. Though user can modify hbase.rpc.timeout by themselves,
> while since phoenix do a lot of aggregation works in RS, it will have more
> chance to time out the client. the usage scenario is quite different from
> normal HBase client.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
