You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "liyang (JIRA)" <ji...@apache.org> on 2016/05/03 09:24:12 UTC
[jira] [Updated] (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 ]
liyang updated KYLIN-1645:
--------------------------
Description:
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.
was:
Currently, exception inside coprocessor is logged at query side, but in a separate thread. E.g.
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
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.
> 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: hongbin ma
>
> 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)