Describe the bug
After IdealState Removal for TaskFramework, we observe onDemand rebalance flooding. We traced back to a root cause: if a jobConfigs exists for a workflow that does not contain it in the DAG, the jobConfig will trigger runtimeJobDag refreshes every time a pipeline runs. Every time runtimeJobDag gets refreshed, it will re-process all the jobs that have been completed, and initiate a clean up process; such a process triggers an onDemand rebalance.
To Reproduce
Create a jobConfig for a workflow without adding it to the DAG.
Expected behavior
onDemand rebalances only happen when necessary.
Additional context
Add any other context about the problem here.
Describe the bug
After IdealState Removal for TaskFramework, we observe onDemand rebalance flooding. We traced back to a root cause: if a jobConfigs exists for a workflow that does not contain it in the DAG, the jobConfig will trigger runtimeJobDag refreshes every time a pipeline runs. Every time runtimeJobDag gets refreshed, it will re-process all the jobs that have been completed, and initiate a clean up process; such a process triggers an onDemand rebalance.
To Reproduce
Create a jobConfig for a workflow without adding it to the DAG.
Expected behavior
onDemand rebalances only happen when necessary.
Additional context
Add any other context about the problem here.