You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Shaofeng SHI (JIRA)" <ji...@apache.org> on 2016/07/28 06:48:21 UTC
[jira] [Closed] (KYLIN-1645) Exception inside coprocessor should
report back to the query thread
[ https://issues.apache.org/jira/browse/KYLIN-1645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shaofeng SHI closed KYLIN-1645.
-------------------------------
Resolved in release 1.5.3 (2-16-07-28)
> 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)