[
https://issues.apache.org/jira/browse/FLINK-23952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404748#comment-17404748
]
Leonid Ilyevsky commented on FLINK-23952:
-----------------------------------------
[~chesnay] , I have some ideas about how I want to run flink, I would
appreciate if you can tell me what you think.
I looked at the scripts and tried them. They did start the processes, but it is
not exactly the way I would like.
The thing is, we have many other apps in the ecosystem, and I use a consistent
framework with python wrappers, so they all have similar layout (places for
configuration, logs, etc.).
Here are my complaints about taskmanager.sh and jobmanager.sh. Maybe I am
missing something, but I don't see how I can control the classpath without
tampering with the scripts. I use some additional jars. Also I am using log4j2
with yaml configuration for the logging. The taskmanager.sh sets logging
differently.
Also I need to add one plugin jar (prometheus). I see that config.sh sets the
FLINK_PLUGINS_DIR, but taskmanager.sh is not using it.
On the other hand, my python wrapper works fine, and the only missing part is
that set of dynamic parameters. So I am thinking of adding to my python script
a call to bash-java-utils and add the results to the command arguments.
> 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)
