hanhanzhang opened a new issue, #16717: URL: https://github.com/apache/dolphinscheduler/issues/16717
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement. ### Description We use -d option parameter when deploying Flink tasks using the Dolphin framework. After Flink is submitted to the Yarn cluster, the lifecycle management of tasks is no longer managed by Dolphin. We hope that this Detached Task will also be managed by Dolphin, which is currently implemented internally: 1. Determine whether the Task is Detached. After the Detached Task is submitted to external system, Worker thread is released, which can improve execution throughput of the worker node and report the task status (RUNNING) to the Master. 2. Worker starts thread to periodically detect detached task state, and reports detached task state to the Master if task state is not expected. 3. If worker failover, supervisory right transfer of detached task has not been done yet. Share this transformation and listen to the community's suggestions for our renovation. ### Are you willing to submit a PR? - [X] 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]
