[
https://issues.apache.org/jira/browse/FLINK-32667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751048#comment-17751048
]
Matthias Pohl commented on FLINK-32667:
---------------------------------------
It would be great to have these performance tests set up before merging the
changes. That would give us some more assurance that working on those issues is
reasonable.
I'm also wondering whether there was a broader discussion on adding this
short-living jobs to the scope of Apache Flink in the ML. Do you have a link to
that discussion?
> Use standalone store and embedding writer for jobs with no-restart-strategy
> in session cluster
> ----------------------------------------------------------------------------------------------
>
> Key: FLINK-32667
> URL: https://issues.apache.org/jira/browse/FLINK-32667
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Coordination
> Affects Versions: 1.18.0
> Reporter: Fang Yong
> Assignee: Fang Yong
> Priority: Major
> Labels: pull-request-available
>
> When a flink session cluster use zk or k8s high availability service, it will
> store jobs in zk or ConfigMap. When we submit flink olap jobs to the session
> cluster, they always turn off restart strategy. These jobs with
> no-restart-strategy should not be stored in zk or ConfigMap in k8s
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
