[
https://issues.apache.org/jira/browse/FLINK-20264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tzu-Li (Gordon) Tai updated FLINK-20264:
----------------------------------------
Description:
Currently, due to how functions can be executed as stateless deployments
separate to the StateFun runtime, they can be easily upgraded with
zero-downtime.
However, up to now there are still some restrictions to what can be done
without restarting StateFun processes:
* Users can not upgrade existing functions to declare new persisted state
* Users can not add new functions to an existing StateFun application, and have
messages routed to it
The end goal of this epic is to enable the above operations for function
deployments, without the need to restart the StateFun runtime. Further details
can be found in subtasks of this JIRA.
was:
Currently, due to how functions can be executed as stateless deployments
separate to the StateFun runtime, they can be easily upgraded with
zero-downtime.
However, up to now there are still some restrictions to what can be done
without restarting StateFun processes:
* Can't upgrade existing functions to declare new persisted state
* Can't add new functions to an existing StateFun application, and have
messages routed to it
The end goal of this epic is to enable the above operations for function
deployments, without the need to restart the StateFun runtime. Further details
can be found in subtasks of this JIRA.
> Zero-downtime / dynamic function upgrades in Stateful Functions
> ---------------------------------------------------------------
>
> Key: FLINK-20264
> URL: https://issues.apache.org/jira/browse/FLINK-20264
> Project: Flink
> Issue Type: New Feature
> Components: Stateful Functions
> Reporter: Tzu-Li (Gordon) Tai
> Priority: Major
> Fix For: statefun-2.3.0
>
>
> Currently, due to how functions can be executed as stateless deployments
> separate to the StateFun runtime, they can be easily upgraded with
> zero-downtime.
> However, up to now there are still some restrictions to what can be done
> without restarting StateFun processes:
> * Users can not upgrade existing functions to declare new persisted state
> * Users can not add new functions to an existing StateFun application, and
> have messages routed to it
> The end goal of this epic is to enable the above operations for function
> deployments, without the need to restart the StateFun runtime. Further
> details can be found in subtasks of this JIRA.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
