Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
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.