[
https://issues.apache.org/jira/browse/FLINK-27274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523592#comment-17523592
]
macdoor615 commented on FLINK-27274:
------------------------------------
Here is my command log
{code:java}
> cast(null as string)[INFO] Submitting SQL update statement to the cluster...
[INFO] SQL update statement has been successfully submitted to the cluster:
Job ID: 0f574f248180b8f8656cbab5916a151d
Flink SQL>
Shutting down the session...
done.
end flink job @ Mon Apr 18 15:30:39 CST 2022
[gum@hb3-dev-gem-bnpmp-002 pyflk]$ cd ../flink
[gum@hb3-dev-gem-bnpmp-002 flink]$ bin/stop-cluster.sh
/etc/host.conf: line 3: bad command `nospoof on'
Stopping taskexecutor daemon (pid: 12511) on host hb3-dev-gem-bnpmp-002.
/etc/host.conf: line 3: bad command `nospoof on'
Stopping standalonesession daemon (pid: 12216) on host hb3-dev-gem-bnpmp-002.
[gum@hb3-dev-gem-bnpmp-002 flink]$ bin/start-cluster.sh
Starting HA cluster with 1 masters.
/etc/host.conf: line 3: bad command `nospoof on'
Starting standalonesession daemon on host hb3-dev-gem-bnpmp-002.
/etc/host.conf: line 3: bad command `nospoof on'
Starting taskexecutor daemon on host hb3-dev-gem-bnpmp-002.
{code}
> 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)