[
https://issues.apache.org/jira/browse/FLINK-27274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523587#comment-17523587
]
macdoor615 commented on FLINK-27274:
------------------------------------
[~zhuzh] you said "By design, if a cluster was normally shutdown (e.g. via
stop-cluster.sh), all data will be cleaned and no job will be recovered if a
new Flink cluster is launched later."
Here I have a contrary example. I put all files in log.recover.debug.zip
# start cluster at 2022-04-18 15:29:42,604
log file: flink-gum-standalonesession-0-hb3-dev-gem-bnpmp-002.log.1
# load the job 0f574f248180b8f8656cbab5916a151d at 2022-04-18 15:30:36,163
log file: flink-gum-standalonesession-0-hb3-dev-gem-bnpmp-002.log.1
{code:java}
sql-client.sh -f new_cf_alarm_recover.yaml.sql{code}
# stop cluster at 2022-04-18 15:30:51,255
log file: flink-gum-standalonesession-0-hb3-dev-gem-bnpmp-002.log.1
{code:java}
stop-cluster.sh{code}
# restart cluster at 2022-04-18 15:31:12,686
log file: flink-gum-standalonesession-0-hb3-dev-gem-bnpmp-002.log
{code:java}
start-cluster.sh{code}
# Retrieved job ids [0f574f248180b8f8656cbab5916a151d] from
ZooKeeperStateHandleStore at 2022-04-18 15:32:07,686
log file: flink-gum-standalonesession-0-hb3-dev-gem-bnpmp-002.log
# job 0f574f248180b8f8656cbab5916a151d recovered at 2022-04-18 15:32:08,345
log file: flink-gum-standalonesession-0-hb3-dev-gem-bnpmp-002.log
> Job cannot be recovered, after restarting cluster
> -------------------------------------------------
>
> Key: FLINK-27274
> URL: https://issues.apache.org/jira/browse/FLINK-27274
> Project: Flink
> Issue Type: Bug
> Components: Table SQL / API
> Affects Versions: 1.15.0
> Environment: Flink 1.15.0-rc3
> [https://github.com/apache/flink/archive/refs/tags/release-1.15.0-rc3.tar.gz]
> Reporter: macdoor615
> Priority: Blocker
> Fix For: 1.15.1
>
> Attachments: flink-conf.yaml,
> flink-gum-standalonesession-0-hb3-dev-flink-000.log.3.zip,
> flink-gum-standalonesession-0-hb3-dev-flink-000.log.zip,
> flink-gum-taskexecutor-2-hb3-dev-flink-000.log, log.recover.debug.zip,
> new_cf_alarm_no_recover.yaml.sql
>
>
> 1. execute new_cf_alarm_no_recover.yaml.sql with sql-client.sh
> config file: flink-conf.yaml
> the job run properly
> 2. restart cluster with command
> stop-cluster.sh
> start-cluster.sh
> 3. job cannot be recovered
> log files
> flink-gum-standalonesession-0-hb3-dev-flink-000.log
> flink-gum-taskexecutor-2-hb3-dev-flink-000.log
> 4. not all job can not be recovered, some can, some can not, at same time
> 5. all job can be recovered on Flink 1.14.4
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
