[FLINK-26719] Rethink the default reschedule reconcile loop

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Not A Problem
• Assignee: Unassigned
• Reporter: WenJun Min
• Created: 18/Mar/22 06:50
• Updated: 24/Nov/22 01:03
• Resolved: 19/Mar/22 09:37

Description

When I test locally, I found that it will reschedule and reconcile with the operator.reconciler.reschedule.interval.sec I doubt why we need this? I think we just need to reconcile

1. waiting for the status change
2. receive the new event
3. waiting for the savepoint result

So when JobManagerDeploymentStatus is Ready, we do not have to trigger the reconcile except waiting for the savepoint result.