alirezazamani opened a new issue #1421: URL: https://github.com/apache/helix/issues/1421
### Describe the bug Once the last task of a job finished, the controller marks the job as completed/failed and sends the DROPPED message for the last task. However, if pending messages existed, the job will be marked as finished, but the tasks do not receive the DROPPED message. In this case, the job will be removed from the DAG and the currentState will not be removed. ### To Reproduce Have a queue with several jobs. Each job should have multiple short-lived tasks. After you start the queue, you would notice that the task current states remain in the ZK. ### Expected behavior The controller should not mark the job as COMPLETED or FAILED if the pending message still existed for the tasks ### Additional context This issue appears as we are not relying on IdealState anymore, Previously, the legacy pipeline would DROP the tasks in the next pipelines ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
