You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gyula Fora (Jira)" <ji...@apache.org> on 2022/06/08 15:26:00 UTC
[jira] [Commented] (FLINK-26493) Use state machine based mechanism to simply the reconciler
[ https://issues.apache.org/jira/browse/FLINK-26493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551671#comment-17551671 ]
Gyula Fora commented on FLINK-26493:
------------------------------------
I am bit hesitant about this ticket at this stage. It would be good to capture the shared parts of the main reconciler logic between Session/Application && Application/SessionJob but not sure what design will be the most suitable overall.
> Use state machine based mechanism to simply the reconciler
> ----------------------------------------------------------
>
> Key: FLINK-26493
> URL: https://issues.apache.org/jira/browse/FLINK-26493
> Project: Flink
> Issue Type: Improvement
> Components: Kubernetes Operator
> Reporter: Aitozi
> Priority: Major
>
> As discussed in [link|https://lists.apache.org/list?dev@flink.apache.org:lte=1M:controller%20flow] , we reach a consensus to use the state machine mechanism to simplify the annoying if-else in the reconciler. Since the modular {{Observer}} {{Reconciler}} and {{validator}} have completed. I think we can start this work now.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)