[
https://issues.apache.org/jira/browse/FLINK-23952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404567#comment-17404567
]
Leonid Ilyevsky commented on FLINK-23952:
-----------------------------------------
I think I know what is going on. When I started with the taskmanager.sh, i saw
it sets a lot of options in command line:
-D taskmanager.memory.network.min=134217730b -D taskmanager.cpu.cores=1.0 -D
taskmanager.memory.task.off-heap.size=0b -D
taskmanager.memory.jvm-metaspace.size=268435456b -D external-resources=none -D
taskmanager.memory.jvm-overhead.min=201326592b -D
taskmanager.memory.framework.off-heap.size=134217728b -D
taskmanager.memory.network.max=134217730b -D
taskmanager.memory.framework.heap.size=134217728b -D
taskmanager.memory.managed.size=536870920b -D
taskmanager.memory.task.heap.size=402653174b -D taskmanager.numberOfTaskSlots=1
-D taskmanager.memory.jvm-overhead.max=201326592b
I think the automatic calculation of those parameters is deprecated in 1.13,
and it was finally turned off in 1.13.2 (because in 1.13.1 my python wrapper
still worked without setting those parameters).
Could somebody please confirm this?
In any case, I would still prefer to set those parameters in the configuration
file. The headache is, I need to think about the proper values for them now,
because the defaults above may not be good for my environment.
Or maybe there is still a way to turn on the automatic settings?
> Taskmanager fails to start complaining about missing configuration option
> -------------------------------------------------------------------------
>
> Key: FLINK-23952
> URL: https://issues.apache.org/jira/browse/FLINK-23952
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Configuration
> Affects Versions: 1.13.2
> Reporter: Leonid Ilyevsky
> Priority: Major
> Attachments: flink-conf.yaml, taskmanager.log, taskmanager_start.txt
>
>
> Taskmanager now fails to start, after I upgraded to 1.13.2. It worked fine in
> 1.13.1.
> It suddenly started complaining about missing configuration options that are
> not really required, according to documentation. When I tried to set the one
> it complained about, it started complaining about another one.
>
> Please see attached files:
> taskmanager_start.txt - actual command that is used to start the program
> flink-conf.yaml - configuration file
> taskmanager.log - logfile where you can see the exception
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
