[Improvement] When EngineRef.exitValue returns a non-0 status. Hopefully, can print an error message

[Toms5578]

Code of Conduct

• I agree to follow this project's Code of Conduct

Search before asking

• I have searched in the issues and found no similar issues.

What would you like to be improved?

When EngineRef.exitValue returns a non-0 status. Hopefully, can print an error message

How should we improve?

No response

Are you willing to submit PR?

• Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
• No. I cannot submit a PR at this time.

[Toms5578]

eg： BufferedReader reader = new BufferedReader(new InputStreamReader(process.getErrorStream()));
String line;
while ((line = reader.readLine()) != null) {
System.out.println(line);
}

[pan3793]

what's the current behavior you observed? I think you should see error messages when something goes wrong on engine launching.

[Toms5578]

您观察到的当前行为是什么？我认为当引擎启动时出现问题时您应该会看到错误消息。

The client reports an error as ：Failed to detect the root cause, please check /data/kyuubi/logs/work/****/kyuubi-spark-sql-engine.log.62 at server side if necessary. The last 10 line(s) of log are:
But the size of this file is 0

[Toms5578]

the retry succeeds, fault locating is affected

[Toms5578]

I suppose ：this error occurred when executing the spark script. bin/spark-class

[pan3793]

what's your version? does it include #6422 (fixed in 1.9.1/1.8.3)?

[github-actions]

Hello @Toms5578,
Thanks for finding the time to report the issue!
We really appreciate the community's efforts to improve Apache Kyuubi.

[Toms5578]

你的版本是什么？它包含#6422吗（已在 1.9.1/1.8.3 中修复）？

1.6.0 Thank you.