There's a simliar issue FLINK-19816[1]
[1] [ https://issues.apache.org/jira/browse/FLINK-19816 |
https://issues.apache.org/jira/browse/FLINK-19816 ]
Best regards,
Yuxia
发件人: "tao xiao"
收件人: "User"
发送时间: 星期四, 2022年 5 月 19日 下午 9:16:34
主题: Re: Incorrect check
Hi team,
Can anyone shed some light?
On Sat, May 14, 2022 at 8:56 AM tao xiao wrote:
> Hi team,
>
> Does anyone have any ideas?
>
> On Thu, May 12, 2022 at 9:20 PM tao xiao wrote:
>
>> Forgot to mention the Flink version is 1.13.2 and we use kubernetes
>> native mode
>>
>> On Thu, May 12, 2022
Hi team,
Does anyone have any ideas?
On Thu, May 12, 2022 at 9:20 PM tao xiao wrote:
> Forgot to mention the Flink version is 1.13.2 and we use kubernetes native
> mode
>
> On Thu, May 12, 2022 at 9:18 PM tao xiao wrote:
>
>> Hi team,
>>
>> I met a weird issue when a job tries to recover from
Forgot to mention the Flink version is 1.13.2 and we use kubernetes native
mode
On Thu, May 12, 2022 at 9:18 PM tao xiao wrote:
> Hi team,
>
> I met a weird issue when a job tries to recover from JM failure. The
> success checkpoint before JM crashed is 41205
>
> ```
>
> {"log":"2022-05-10 14:5
Hi team,
I met a weird issue when a job tries to recover from JM failure. The
success checkpoint before JM crashed is 41205
```
{"log":"2022-05-10 14:55:40,663 INFO
org.apache.flink.runtime.checkpoint.CheckpointCoordinator[] -
Completed checkpoint 41205 for job 0
