Hi Sergei, If you want just to try increasing the timeouts, you could change the checkpoint timeout in env.getCheckpointConfig().setCheckpointTimeout(...) [1] or s3 client timeouts (see presto or hdfs for s3 configuration, there are some network timeouts) [2].
Otherwise it would be easier to investigate the reason of failures if you provide JM and TM logs. Best, Andrey [1] https://ci.apache.org/projects/flink/flink-docs-release-1.7/dev/stream/state/checkpointing.html#enabling-and-configuring-checkpointing <https://ci.apache.org/projects/flink/flink-docs-release-1.8/dev/stream/state/checkpointing.html#enabling-and-configuring-checkpointing> [2] https://ci.apache.org/projects/flink/flink-docs-release-1.7/ops/filesystems.html#built-in-file-systems <https://ci.apache.org/projects/flink/flink-docs-release-1.8/ops/filesystems.html#built-in-file-systems> On Thu, Jul 18, 2019 at 5:00 PM spoganshev <s.pogans...@slice.com> wrote: > The image should be visible now at > > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Checkpoints-timing-out-for-no-apparent-reason-td28793.html#none > > It doesn't look like it is a disk performance or network issue. Feels more > like some buffer overflowing or timeout due to slightly bigger files being > uploaded to S3. > > > > -- > Sent from: > http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/ >
