lbrowny commented on issue #16906: URL: https://github.com/apache/dolphinscheduler/issues/16906#issuecomment-2556574451
> > > The only one different is the `.kill` file will be executed by tenant, please check if the tenant has permission to execute the file > > > > > > Yes. Through the permission of the file is not 755, execute .kill file by user tenantName1, the output indicates tenantName1 has permission to execute the file.  > > @lbrowny I submit #16909 to fix this problem. I mean through `.kill` file without x permission, the file can be successfully executed using `sh` command. I also tried make `.kill` file myself, chmod it to 777 , and then stop the task instance. In this way, org.apache.dolphinscheduler.plugin.task.api.am.YarnApplicationManager#execYarnKillCommand could used the exists `.kill` file with `rwx` permission, but still failed to stop spak job with the exactly same output. It seems nothing to do with the permission of the `.kill` file. I notice that similar issues with ExitCodeException usually have additional infomation about fail reason, but showed nothing in my case. Is it because of exit code? 137 means shell execution was interrupted‌. -- 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]
