[ https://issues.apache.org/jira/browse/FLINK-26719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508658#comment-17508658 ]
Aitozi commented on FLINK-26719: -------------------------------- [~matyas] Thanks for your inputs, It seems we have done the same thing manually in \{{org.apache.flink.kubernetes.operator.observer.JobManagerDeploymentStatus#rescheduleAfter}} . [~wangyang0918], IMO we have to define a final/target status for example: {{the JobManager is ready for serve}} and stop the reconcile, It's not a common way to run each loop to sync status without an end. > Rethink the default reschedule reconcile loop > --------------------------------------------- > > Key: FLINK-26719 > URL: https://issues.apache.org/jira/browse/FLINK-26719 > Project: Flink > Issue Type: Sub-task > Reporter: Aitozi > Priority: Major > > 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 > # waiting for the status change > # receive the new event > # waiting for the savepoint result > So when JobManagerDeploymentStatus is Ready, we do not have to trigger the > reconcile except waiting for the savepoint result. -- This message was sent by Atlassian Jira (v8.20.1#820001)