unsubscribe

Re: Flink 1.14 stuck on INITIALIZING state after job restarting

create connection at > function initializes. > > > > On Nov 11, 2021, at 18:01, Xiangyu Su wrote: > > Thank you Jake! > Enable debug level logging have to ask system engineer first ;) > do you know how to resolve this issue? > > Best > > On Thu, 11 Nov 202

Re: Flink 1.14 stuck on INITIALIZING state after job restarting

Thank you Jake! Enable debug level logging have to ask system engineer first ;) do you know how to resolve this issue? Best On Thu, 11 Nov 2021 at 10:57, Jake wrote: > > Set log root level is DEBUG and check Job manager logs, you will get it. > > > > On Nov 11, 2021, at

Flink 1.14 stuck on INITIALIZING state after job restarting

for Task manager, once spot instances get lost and then get new instances this issue will always happen. Best, -- Xiangyu Su Senior Data Engineer xian...@smaato.com Smaato Inc. San Francisco - New York - Hamburg - Singapore www.smaato.com Germany: Barcastraße 5 22087 Hamburg Germany M 0049(176

Re: Potential bug when assuming roles from AWS EKS when using S3 as RocksDb checkpoint backend?

lease see AWS doc here: >> https://docs.aws.amazon.com/eks/latest/userguide/iam-roles-for-service-accounts-minimum-sdk.html >> >> Could someone help me confirm this bug and maybe have it fixed some time? >> Thanks. >> >> Thomas >> > -- Xiangyu Su Java Deve

Re: FLINK-14316 happens on version 1.13.2

us? That might help investigating > what's going on. > > Best, > Matthias > > On Fri, Sep 3, 2021 at 10:07 AM Xiangyu Su wrote: > >> Hi Yun, >> Thanks alot. >> I am running a test, and facing the "Job Leader lost leadership..." >>

Re: FLINK-14316 happens on version 1.13.2

; in the TM log ? If so, the root cause might be that the connection between > the TM and ZK is lost or > timeout. Have you checked the GC status of the TM side ? If the GC is ok, > could you provide more detailed > exception stack ? > > Best, > Yun > > > -

Checkpointing failure, subtasks get stuck

, -- Xiangyu Su Java Developer xian...@smaato.com Smaato Inc. San Francisco - New York - Hamburg - Singapore www.smaato.com Germany: Barcastraße 5 22087 Hamburg Germany M 0049(176)43330282 The information contained in this communication may be CONFIDENTIAL and is intended only for the use of

Job leader ... lost leadership with version 1.13.2

uggestions? Best Regards, -- Xiangyu Su Java Developer xian...@smaato.com Smaato Inc. San Francisco - New York - Hamburg - Singapore www.smaato.com Germany: Barcastraße 5 22087 Hamburg Germany M 0049(176)43330282 The information contained in this communication may be CONFIDENTIAL and is intende

Checkpointing failure, subtasks get stuck

checkpoint timeout without huge increasing of incoming data... and also seen the checkpointing progress of some subtasks get stuck by e.g 7% for 10 mins. My guess would be somehow the thread for doing checkpointing get blocked... Any suggestions? idea will be helpful, thanks Best Regards, -- Xiangyu

FLINK-14316 happens on version 1.13.2

st Regards, -- Xiangyu Su Java Developer xian...@smaato.com Smaato Inc. San Francisco - New York - Hamburg - Singapore www.smaato.com Germany: Barcastraße 5 22087 Hamburg Germany M 0049(176)43330282 The information contained in this communication may be CONFIDENTIAL and is intended only for

flink: keyed process function, why are timestamp of register event timer different as "on timer" function timestamp

Hi User, We are using keyed process function with Event time for flink streaming application. We register event time on "processElement" function, and mentioned that "onTimer" function had different "timestamp" as registered on "processElement" function. If we understand correctly, "onTimer" shou

Re: apache flink: Why checkpoint coordinator takes long time to get completion

th version 1.8.0, and it does not happen with version 1.8.1 until now. Best regards Xiangyu On Tue, 23 Jul 2019 at 08:49, Zili Chen wrote: > Hi Xiangyu, > > Could you share the corresponding JIRA that fixed this issue? > > Best, > tison. > > > Xiangyu Su 于2019年7月19日周五 下

Re: apache flink: Why checkpoint coordinator takes long time to get completion

btw. it seems like this issue has been fixed in 1.8.1 On Fri, 19 Jul 2019 at 12:21, Xiangyu Su wrote: > Ok, thanks. > > and this time-consuming until now always happens after 3rd checkpointing, > and this unexpected time-consuming was always consistent (~ 4 min by under >

Re: apache flink: Why checkpoint coordinator takes long time to get completion

ant codes. There is a gap between > calculating the duration and logging it out. I guess the checkpoint 4 is > finished in 1 minute, but there is an unexpected time-consuming operation > during that time. But I can't tell which part it is. > > > Xiangyu Su 于2019年7月19日周五 下午4

apache flink: Why checkpoint coordinator takes long time to get completion

t; for few minutes after 3 checkpointing? Best Regards -- Xiangyu Su Java Developer xian...@smaato.com Smaato Inc. San Francisco - New York - Hamburg - Singapore www.smaato.com Germany: Valentinskamp 70, Emporio, 19th Floor 20355 Hamburg M 0049(176)22943076 The information contained in this com