You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@kyuubi.apache.org by "sohurdc (via GitHub)" <gi...@apache.org> on 2025/08/01 03:41:26 UTC

[I] [Bug] Kyuubi job status always shows as "Succeeded" even when the actual job has failed [kyuubi]

sohurdc opened a new issue, #7161:
URL: https://github.com/apache/kyuubi/issues/7161

   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
   
   
   ### Search before asking
   
   - [x] I have searched in the [issues](https://github.com/apache/kyuubi/issues?q=is%3Aissue) and found no similar issues.
   
   
   ### Describe the bug
   
   Kyuubi job status always shows as "Succeeded" even when the actual job has failed.
   My execution script is as follows:
   beeline -u "jdbc:hive2://kyuubiserver.my.com:10009/myuser;principal=hive/kyuubi.my.com@MY.COM;hive.server2.proxy.user=myuser" --hiveconf spark.yarn.queue=center --hiveconf spark.executor.memory=4g  -e "insert overwrite directory 'hdfs:///user/myuser/tmp/2025-07-23' select * from ..."
   
   then job faied with error such as:
   Caused by: org.apache.kyuubi.plugin.spark.authz.AccessControlException: Permission denied: user [myuser] does not have [write] privilege on ...
   
   But the final job status shown on the Spark log page is "Succeeded", which makes it impossible to determine the actual job outcome based on the job status. This hinders accurate job monitoring and retry mechanisms.
   
   <img width="647" height="413" alt="Image" src="https://github.com/user-attachments/assets/9ed3e200-d1e4-4499-b9a9-93e7ff220f71" />
   
   ### Affects Version(s)
   
   1.10.2
   
   ### Kyuubi Server Log Output
   
   ```logtalk
   
   ```
   
   ### Kyuubi Engine Log Output
   
   ```logtalk
   
   ```
   
   ### Kyuubi Server Configurations
   
   ```yaml
   
   ```
   
   ### Kyuubi Engine Configurations
   
   ```yaml
   
   ```
   
   ### Additional context
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to fix.
   - [ ] No. I cannot submit a PR at this time.


-- 
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: notifications-unsubscribe@kyuubi.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@kyuubi.apache.org
For additional commands, e-mail: notifications-help@kyuubi.apache.org


Re: [I] [Bug] Kyuubi job status always shows as "Succeeded" even when the actual job has failed [kyuubi]

Posted by "Echan0808 (via GitHub)" <gi...@apache.org>.
Echan0808 commented on issue #7161:
URL: https://github.com/apache/kyuubi/issues/7161#issuecomment-3153813043

   翻译成英文,我在connection 的sharelevel下也碰到了同样的问题,jdbc客户端能接收报错,但是yarn app状态显示成功,这对于审计来说有些困扰,看起来有可能是因为kyuubi engine层手动调用了sparkcontext stop造成的


-- 
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: notifications-unsubscribe@kyuubi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@kyuubi.apache.org
For additional commands, e-mail: notifications-help@kyuubi.apache.org


Re: [I] [Bug] Kyuubi job status always shows as "Succeeded" even when the actual job has failed [kyuubi]

Posted by "Echan0808 (via GitHub)" <gi...@apache.org>.
Echan0808 commented on issue #7161:
URL: https://github.com/apache/kyuubi/issues/7161#issuecomment-3153814506

   I encountered the same issue under the sharelevel of connection. The JDBC client can receive the error, but the YARN app status shows as successful, which is somewhat troublesome for auditing. It seems likely that this is caused by the Kyuubi engine layer manually calling SparkContext.stop().


-- 
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: notifications-unsubscribe@kyuubi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@kyuubi.apache.org
For additional commands, e-mail: notifications-help@kyuubi.apache.org


Re: [I] [Bug] Kyuubi job status always shows as "Succeeded" even when the actual job has failed [kyuubi]

Posted by "pan3793 (via GitHub)" <gi...@apache.org>.
pan3793 commented on issue #7161:
URL: https://github.com/apache/kyuubi/issues/7161#issuecomment-3142150351

   It's by design, in this case, you will get an error report from your BeeLine client. 


-- 
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: notifications-unsubscribe@kyuubi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@kyuubi.apache.org
For additional commands, e-mail: notifications-help@kyuubi.apache.org


Re: [I] [Bug] Kyuubi job status always shows as "Succeeded" even when the actual job has failed [kyuubi]

Posted by "sohurdc (via GitHub)" <gi...@apache.org>.
sohurdc commented on issue #7161:
URL: https://github.com/apache/kyuubi/issues/7161#issuecomment-3144185320

   BeeLine client can get an error, But the existing job monitoring is all based on the YARN API. Is there any plan to support correcting job status in the future? Or is there a parameter can correcting job status ? You're very much appreciated.


-- 
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: notifications-unsubscribe@kyuubi.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@kyuubi.apache.org
For additional commands, e-mail: notifications-help@kyuubi.apache.org