[
https://issues.apache.org/jira/browse/KYLIN-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874211#comment-15874211
]
Dayue Gao commented on KYLIN-2451:
----------------------------------
Hi [[email protected]],
I see what's the difference. Our goal is the same, make rpc timeout longer than
coprocessor-timeout-seconds. The differences are
that previously we override coprocessor-timeout-seconds according to
HBASE_RPC_TIMEOUT (please see comment about coprocessor-timeout-seconds in
kylin.properties), and now you want to do it oppositely, set HBASE_RPC_TIMEOUT
according to coprocessor-timeout-seconds, right?
But I would prefer the previously approach because coprocessor-timeout-seconds
is a cube level configs but HBASE_RPC_TIMEOUT is a global one. With your
approach, use can't choose a larger value at cube level.
> Set HBASE_RPC_TIMEOUT according to
> kylin.storage.hbase.coprocessor-timeout-seconds
> ----------------------------------------------------------------------------------
>
> Key: KYLIN-2451
> URL: https://issues.apache.org/jira/browse/KYLIN-2451
> Project: Kylin
> Issue Type: Improvement
> Reporter: liyang
> Assignee: liyang
> Fix For: v2.0.0
>
>
> Currently if HBASE_RPC_TIMEOUT is shorter than
> "kylin.storage.hbase.coprocessor-timeout-seconds", the HBase RPC call will
> timeout before coprocessor gives up. Shall let RPC wait longer.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
