You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Aitozi (Jira)" <ji...@apache.org> on 2022/03/18 06:52:00 UTC

[jira] [Commented] (FLINK-26719) Rethink the default reschedule reconcile loop

    [ https://issues.apache.org/jira/browse/FLINK-26719?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17508597#comment-17508597 ] 

Aitozi commented on FLINK-26719:
--------------------------------

cc [~wangyang0918] [~gyfora] 

> 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)