[
https://issues.apache.org/jira/browse/FLINK-18165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-18165:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
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.
> When savingpoint is restored, select the checkpoint directory and stateBackend
> ------------------------------------------------------------------------------
>
> Key: FLINK-18165
> URL: https://issues.apache.org/jira/browse/FLINK-18165
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
> Affects Versions: 1.9.0
> Environment: flink 1.9
> Reporter: Xinyuan Liu
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
>
> If the checkpoint file is used as the initial state of the savepoint startup,
> it must be ensured that the state backend used before and after is the same
> type, but in actual production, there will be more and more state, the
> taskmanager memory is insufficient and the cluster cannot be expanded, and
> the state backend needs to be switched at this time. And there is a need to
> ensure data consistency. Unfortunately, currently flink does not provide an
> elegant way to switch state backend, can the community consider this proposal
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
