flink-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Lasse Nedergaard <lassenedergaardfl...@gmail.com>
Subject Re: Savepoint memory overhead
Date Thu, 30 Apr 2020 08:37:35 GMT

Thanks for the reply. 
The link you provide make us thinking of some old rocksdb cfg. We was still using and it could
cause our container killing problems so I will do a test without specific  rocksdb cfg. 
But we also see RocksDbExceptions “cannot allocate memory” while appending to a file.
And that make me think the managed men is to small for the state size. Please see below for
a specific job with parallelism 4

So task managers as we have can’t handle infinite size so I was looking for the understanding
and guidelines for getting the config right in relation to the state size. 
For now we run in session mode and the setting is shared between all job and we have job that
don’t require many resources therefore the low settings 

Jvm heap size 734 mb
Flink managed men 690 mb
1 slot for each task manager. 

By a mistake we had some rocksdb Settings from prev. Version. I have removed this configuration
and will test again. 

For jobs with restart and failed checkpoints/savepoints there is a common trend that they
have larger state than without problems. We have on some of the failing jobs reduced our retention
so our state got smaller and then they run ok. We do tests where we increase parallelism and
they’ve reduce the state size for each task manager and then they run ok. 

We don’t use windows functions and the jobs use standard value, list and map state. 

Med venlig hilsen / Best regards
Lasse Nedergaard

> Den 30. apr. 2020 kl. 08.55 skrev Yun Tang <myasuka@live.com>:
> Hi Lasse
> Would you please give more details?
> What is the memory configuration of your task manager? e.g the memory size of process,
managed memory. And how large the memory would increase to once you meet problem.
> Did you use managed memory to control RocksDB? [1]
> Why you give the assumption that memory problem has relationship with savepoint?
> What is the topology of you streaming job: how many states and window you use, how many
slots per task manager?
> [1] https://ci.apache.org/projects/flink/flink-docs-release-1.10/ops/memory/mem_tuning.html#rocksdb-state-backend
> Best
> Yun Tang
> From: Lasse Nedergaard <lassenedergaardflink@gmail.com>
> Sent: Thursday, April 30, 2020 12:39
> To: Yun Tang <myasuka@live.com>
> Cc: user <user@flink.apache.org>
> Subject: Re: Savepoint memory overhead
> We using Flink 1.10 running on Mesos. 
> Med venlig hilsen / Best regards
> Lasse Nedergaard
>>> Den 30. apr. 2020 kl. 04.53 skrev Yun Tang <myasuka@live.com>:
>> Hi Lasse
>> Which version of Flink did you use? Before Flink-1.10, there might exist memory problem
when RocksDB executes savepoint with write batch[1].
>> [1] https://issues.apache.org/jira/browse/FLINK-12785
>> Best
>> Yun Tang
>> From: Lasse Nedergaard <lassenedergaardflink@gmail.com>
>> Sent: Wednesday, April 29, 2020 21:17
>> To: user <user@flink.apache.org>
>> Subject: Savepoint memory overhead
>> Hi.
>> I would like to know if there are any guidelines/recommendations for the memory overhead
we need to calculate for when doing savepoint to s3. We use RockDb state backend.
>> We run our job on relative small task managers and we can see we get memory problems
if the state size for each task manager get "big" (we haven't found the rule of thumbs yet)
and we can remove the problem if we reduce the state size, or increase parallelism and jobs
with none or small state don't have any problems.
>> So I see a relation between between allocated memory to a task manager and the state
it can handle. 
>> So do anyone have any recommendations/ base practices for this and can someone explain
why savepoint requires memory.
>> Thanks
>> In advance
>> Lasse Nedergaard 

View raw message