Same error again today. Any tips ? I'm considering downgrading to Flink
1.14 ?
On Wed, Dec 14, 2022 at 11:51 AM Lars Skjærven wrote:
> As far as I understand we are not specifying anything on restore mode. so
> I guess default (NO_CLAIM) is what we're using.
>
> We're using ververica platform to
As far as I understand we are not specifying anything on restore mode. so I
guess default (NO_CLAIM) is what we're using.
We're using ververica platform to handle deploys, and things are a bit
obscure on what happens underneath.
It happened again this morning:
Caused by: java.io.FileNotFoundExce
Hi Lars,
Have you used any of the new restore modes that were introduced with 1.15?
https://flink.apache.org/2022/05/06/restore-modes.html
Best regards,
Martijn
On Fri, Dec 9, 2022 at 2:52 PM Lars Skjærven wrote:
> Lifecycle rulesNone
>
> On Fri, Dec 9, 2022 at 3:17 AM Hangxiang Yu wrote:
>
Lifecycle rulesNone
On Fri, Dec 9, 2022 at 3:17 AM Hangxiang Yu wrote:
> Hi, Lars.
> Could you check whether you have configured the lifecycle of google cloud
> storage[1] which is not recommended in the flink checkpoint usage?
>
> [1] https://cloud.google.com/storage/docs/lifecycle
>
> On Fri,
Hi, Lars.
Could you check whether you have configured the lifecycle of google cloud
storage[1] which is not recommended in the flink checkpoint usage?
[1] https://cloud.google.com/storage/docs/lifecycle
On Fri, Dec 9, 2022 at 2:02 AM Lars Skjærven wrote:
> Hello,
> We had an incident today with
Hello,
We had an incident today with a job that could not restore after crash (for
unknown reason). Specifically, it fails due to a missing checkpoint file.
We've experienced this a total of three times with Flink 1.15.2, but never
with 1.14.x. Last time was during a node upgrade, but that was not
