Hi Till, definitely seems to be a strange issue. The first time the job is loaded (with a clean instance of the Cluster) the job goes well, but if it is canceled or started again the issue came.
I built an example here https://github.com/congd123/flink-s3-example You can generate the artifact of the Flink Job and start the cluster with the configuration on the docker-compose. Thanks for helping -- Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/