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

Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/03/25 10:24:00 UTC

[jira] [Updated] (FLINK-26825) Document State Machine Graph for JM Deployment

     [ https://issues.apache.org/jira/browse/FLINK-26825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated FLINK-26825:
-----------------------------------
    Labels: pull-request-available  (was: )

> Document State Machine Graph for JM Deployment
> ----------------------------------------------
>
>                 Key: FLINK-26825
>                 URL: https://issues.apache.org/jira/browse/FLINK-26825
>             Project: Flink
>          Issue Type: Sub-task
>            Reporter: Biao Geng
>            Assignee: Biao Geng
>            Priority: Major
>              Labels: pull-request-available
>
>  We may need a state machine graph for JM deployment or the whole cluster like [lyft’s|https://github.com/lyft/flinkk8soperator/blob/master/docs/state_machine.md] in our document to help our developers refine our code later and our users learn about how the oeprator reconciles.
> The state machine is highly probably to be changed when we introduce more features(e.g. rollback strategy) and we should update the doc when such change happens.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)