gaotong521 opened a new issue, #16843: URL: https://github.com/apache/dolphinscheduler/issues/16843
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar issues. ### What happened When kerberos authentication is enabled, the kerberos expiration time is 7 days, and tasks such as flink and spark will fail to be run after 7 days. The kerberos code logic for periodically updating has been added and is valid, allowing the resource center to use it properly. However, the hand running flink and spark tasks still fails and the Dolphinscheduler cluster needs to be restarted The newly added code is shown below：   After 7 days, the resource center can be used normally, as shown in the following figure  Running the flink live spark task will fail after 7 days, as shown below:    ### What you expected to happen The flink and spark tasks can run properly at any time without failing when kerberos expires, and the dolphinscheduler cluster does not need to be restarted ### How to reproduce The expiration time of kerberos is 7 days, after which running tasks will fail ### Anything else no ### Version 3.2.x ### Are you willing to submit PR? - [ ] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- 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]
