Hello Everyone, Today i have a very unique issue....
# troubleshooting
h
Hello Everyone, Today i have a very unique issue. We are dealing with issue with Flink Restart. We are using Kinesis, Rocksdb and dynmodb as our infrastructure. Here everything is working fine, we can see that records are fetch, processed and pushed to dynamodb, until there is a restart. Following thing we have observed when restart occurs. 1- There is constant back pressure 2- Nothing In/out buffers for like 20min before restart 3- no resource usage, CPU usage is close to nothing 4- I see checkpoints faling at 20 minutes before that 5- Batch write to dynamodb is constant in that window. Sharing your monitoring result as well. We are still not sure what can be the cause of issue, any suggestions would really help.
g
What does the Flink UI suggest for the checkpoint duration and size?
How large is the state that needs to be recovered?
h
This is the size of checkpoint, we are using unalligned checkpoint.
I mean when the issue occurs the checkpoint size of the checkpoint in also too low.
g
what about watermarks? do you see watermarks progressing?
h
Not sure about the time the issue happens because its kinda random.
g
can you provide some more context on what the pipeline actually does and if you are using processing or event time?
and what should be the expected result? i.e on restart are you reprocessing from the start of the topic? and expect many messages to be processed?
h
So we are basic fetching events, processing using hash map and then save in dynamodb. What we have seen that 20 min before restart i.e. when checkpoint start to fails we stop consuming as you can see in screenshot as well. And soon as we restart we get back to track and reconsume it again.
So i monitor the job and seems like when this issue its stucks in dynamodb sink, i tried to check flame-graph On-CPU but i cannot see any threads. Not sure what is causing it.