Uploaded image for project: 'Kylin'
  1. Kylin
  2. KYLIN-1645

Exception inside coprocessor should report back to the query thread

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: v1.5.3
    • Component/s: None
    • Labels:
      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.

        Attachments

          Activity

            People

            • Assignee:
              liyang.gmt8@gmail.com liyang
              Reporter:
              liyang.gmt8@gmail.com liyang
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: