[
https://issues.apache.org/jira/browse/KYLIN-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
liyang resolved KYLIN-1645.
---------------------------
Resolution: Fixed
Assignee: liyang (was: hongbin ma)
Fix Version/s: v1.5.3
> Exception inside coprocessor should report back to the query thread
> -------------------------------------------------------------------
>
> Key: KYLIN-1645
> URL: https://issues.apache.org/jira/browse/KYLIN-1645
> Project: Kylin
> Issue Type: Bug
> Reporter: liyang
> Assignee: liyang
> Fix For: v1.5.3
>
>
> Currently, exception inside coprocessor is logged at query side, but in a
> separate thread. E.g.
> {code}
> 2016-05-02 23:19:07,130 ERROR [pool-3-thread-23] v2.CubeHBaseEndpointRPC:110
> : Caught exception in thread pool-3-thread-23:
> java.lang.RuntimeException: <sub-thread for GTScanRequest 7d354973> Error
> when visiting cubes by endpoint
> {code}
> The problem is the exception does not notify the main query thread, which
> will wait to timeout and throw out "Timeout visiting cube!" to client. Very
> misleading.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
