[
https://issues.apache.org/jira/browse/FLINK-32667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17751107#comment-17751107
]
Matthias Pohl commented on FLINK-32667:
---------------------------------------
Thanks, [~zjureel]. I think it's a good idea to initiate the discussion in the
mailing list. That way we might gather additional feedback on the scenarios and
avoid redoing things because we haven't considered certain edge cases. That
said, I'm confident that this use case makes sense to consider as part of the
Flink roadmap. I'm looking forward to your ML post.
> 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)
