alirezazamani opened a new issue #1099: URL: https://github.com/apache/helix/issues/1099
(In purge logic) There exists a scenario where a job gets deleted from the config but the job has not been deleted from the DAG yet. If in this cache gets refreshed, the new RuntimeJobDag will be created which contains the jobs without the config. In this case, the queue will be stuck because once controller wants to process this job without the config, it will return empty assignment. Hence, the queue will be halted until a new change happens to the queue. Regarding purging a job, it is better to work the opposite of adding the job. 1- First delete the job from DAG 2- Second delete the job from config Note: TestJobQueueCleanUp is unstable due to the same issue. Also it is not possible to handle this scenario in cache level because once we the job config gets purged, we cannot have enough information regarding the type of workflow/queue and its DAG. ---------------------------------------------------------------- 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]
