Thank you Vino for the information.
Best,
Ethan
> On Dec 17, 2019, at 8:29 PM, vino yang wrote:
>
> Hi Ethan,
>
> Share two things:
>
> I have found "taskmanager.memory.preallocate" config option has been removed
> in the master codebase.
> After researching git history, I found the
Hi Ethan,
Share two things:
- I have found "taskmanager.memory.preallocate" config option has been
removed in the master codebase.
- After researching git history, I found the description of "
taskmanager.memory.preallocate" was written by @Chesnay Schepler
(from 1.8 branch).
I didn’t realize we was not chatting in the mailing list :)
I think it’s wrong because it kind of says full GC is triggered by reaching
MaxDirecMemorySize.
> On Dec 16, 2019, at 11:03 PM, Xintong Song wrote:
>
> Glad that helped. I'm also posting this conversation to the public mailing
>
Glad that helped. I'm also posting this conversation to the public mailing
list, in case other people have similar questions.
And regarding the GC statement, I think the document is correct.
- Flink Memory Manager guarantees that the amount of allocated managed
memory never exceed the configured
Hi Ethan,
For now, my suggestion is that you can set "preallocate" to false. The
description(the link provided by you) of "taskmanager.memory.preallocate"
says:
"When taskmanager.memory.off-heap is set to true, then it is advised that
this configuration is also set to true."
Best,
Vino
Ethan
Hi Community,
I have a question about the taskmanager.memory.preallocate config in the doc
https://ci.apache.org/projects/flink/flink-docs-release-1.8/ops/config.html#taskmanager-memory-preallocate
