tomma-a commented on issue #10177:
URL: https://github.com/apache/seatunnel/issues/10177#issuecomment-3639680166
@yzeng1618 First ,Really appreciate your input!
here is my above test settings:
seatunnel job setting, it's a streaming job
`
env {
parallelism = 1
job.mode = "STREAMING"
checkpoint.interval=60000
flink.execution.checkpointing.mode = "EXACTLY_ONCE"
flink.execution.checkpointing.timeout = 600000
}
source {
Kafka {
plugin_output="fake2"
topic = info
consumer.group="testr"
bootstrap.servers =
"tom-cluster-kafka-bootstrap.kafka.svc.cluster.local:9092"
format = json
}
}
sink {
Kafka {
plugin_input="fake2"
topic = topc
bootstrap.servers =
"tom-cluster1-kafka-bootstrap.kafka.svc.cluster.local:9092"
format = json
kafka.request.timeout.ms = 60000
semantics = EXACTLY_ONCE
}
}
`
Then I run the seatunnel job in flink (by flink k8s operator) CDR
FlinkDeployment
`
apiVersion: flink.apache.org/v1beta1
kind: FlinkDeployment
metadata:
name: seatunnel-flink-streaming-example-2
namespace: kafka
spec:
......
volumes:
- name: seatunnel-config
configMap:
name: seatunnel-config
job:
jarURI: local:///opt/seatunnel/starter/seatunnel-flink-15-starter.jar
entryClass: org.apache.seatunnel.core.starter.flink.SeaTunnelFlink
args: ["--config", "/data/seatunnel.streaming.conf"]
parallelism: 2
upgradeMode: savepoint
`
The first time , i kubectl apply the above yaml into a k8s cluster, the the
seatunnel job is running as normal. the flink checkpoints saved periodically
successfully.
Then i make some changes the above yaml file , then apply the yaml again in
k8s. It's a kind of uprading mode
Because my flink upgradeMode is savepoint (if last-state also doesn't work
which uses the last checkpoint)
The above error happen, can NOT restore from last checkpoint/or savepoint!
Please correct me if i'm wrong about this, thanks
Tom
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
