Kwafoor commented on issue #5304:
URL: https://github.com/apache/kyuubi/issues/5304#issuecomment-1755392102

   Eliminate helpless tailing stacktrace is difficult. The exception stack from 
ProcBuilder's stderr isn't being captured. The matching rule for the exception 
stack is `\tat`, but when stderr outputs the exception, the prefix of the stack 
is `        at `. The problem I'm facing could be solved by capturing this part 
of the exception stack.
   
   The part of the log that matches the exception is missing the exception 
stack.
   ```
   Caused by: java.lang.RuntimeException: 
org.apache.kyuubi.KyuubiSQLException:Exception in thread "main" 
java.lang.reflect.UndeclaredThrowableException
    See more: /xxxxxxxxx/kyuubi-spark-sql-engine.log.xxx
        at 
org.apache.kyuubi.KyuubiSQLException$.apply(KyuubiSQLException.scala:69)
        at 
org.apache.kyuubi.engine.ProcBuilder.$anonfun$start$1(ProcBuilder.scala:142)
        ... 1 more
   ```
   Log containing the exception stack.
   ```
   For more detailed output, check the application tracking page: 
http://xxxxxxx Then click on links to logs of each attempt.
   . Failing the application.
   Exception in thread "main" java.lang.reflect.UndeclaredThrowableException
           at 
org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1780)
   ...
   Caused by: org.apache.spark.SparkException: Application xxxxxxxx finished 
with failed status
           at org.apache.spark.deploy.yarn.Client.run(Client.scala:1249)
   ...
   ```
   
![image](https://github.com/apache/kyuubi/assets/25627922/139258b1-fc46-45f5-ae7d-dad5d8c6495b)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to