[
https://issues.apache.org/jira/browse/FLINK-23952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17404531#comment-17404531
]
Leonid Ilyevsky commented on FLINK-23952:
-----------------------------------------
[~xtsong] I have my own python script to start the jobmanager and taskmanager,
I've been using it for a couple of years, and it worked fine, including 1.13.1.
Something broke when I upgraded to 1.13.2, I wonder what that is.
Btw., the jobmanager still starts fine, only taskmanager has a problem.
It started complaining about the number of cores parameter; just for an
experiment, I set the number of cores, and then it complained about memory
parameters. Looks like a lot of parameters that it should calculate itself, are
not calculated.
Maybe I will try to start it with the shell script as you suggested, to see if
it starts.
> 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)
