[
https://issues.apache.org/jira/browse/FLINK-23952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404605#comment-17404605
]
Chesnay Schepler commented on FLINK-23952:
------------------------------------------
The settings are automatically derived by the BashJavaUtils. I would recommend
digging through the Flink start scripts a bit to figure out how Flink
bootstraps the processes. Essentially a separate java process is started that
reads the config, checks the environment, and then derives the final
configuration parameters which are send to stdout, parsed in the scripts, then
passed on to the final Flink process.
For completeness sake I would discourage you from manually creating Flink
processes in that way and to just rely on the existing scripts. We essentially
provide 0 guarantees that these things don't change from one release to the
next (bugfix releases included), as they are considered implementation details.
The flink-conf.yaml does not support nesting, because years ago we started with
the simple custom parsing, probably to avoid more dependencies. There are
thoughts to switch to a proper yaml parser, but nothing concrete yet.
> 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)