[
https://issues.apache.org/jira/browse/FLINK-14615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-14615:
-----------------------------------
Labels: auto-deprioritized-major stale-minor usability (was:
auto-deprioritized-major usability)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Add Flink Web UI capabilities for savepoint
> -------------------------------------------
>
> Key: FLINK-14615
> URL: https://issues.apache.org/jira/browse/FLINK-14615
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Web Frontend
> Reporter: Mario Georgiev
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor, usability
>
> Having the ability to do the following would greatly simplify Kubernetes/any
> cluster deployment that utilizes a single cluster for multiple jobs, rather
> than job per cluster.
> My proposal is the following:
> Have a way to trigger savepoint from the UI for a job and have a way to get
> the savepoint's progress somewhere in the UI.
> Have a way to deploy a new job/existing job from the UI using an existing
> savepoint and choosing between --allowNonRestoredState or not allowing such
> state at all.
> Have a way to trigger savepoints at scheduled interval for job or group of
> jobs ( this could very well be a second iteration since this would require
> persistence for the job schedules )
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
