[
https://issues.apache.org/jira/browse/FLINK-20645?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17251348#comment-17251348
]
Li Wang commented on FLINK-20645:
---------------------------------
Yes, in k8s we actually want to have one cluster dedicated for one single job,
named as job cluster or application mode. We copied the flink job jar into lib
and bring the cluster up, and the logic is similar as the instruction
[here|https://ci.apache.org/projects/flink/flink-docs-stable/deployment/resource-providers/standalone/#application-mode].
It works for us for Flink 1.6 and 1.7, and recently want to support 1.11 as
well, but got the issue above.
> Extra space typo when assembling dynamic configs
> ------------------------------------------------
>
> Key: FLINK-20645
> URL: https://issues.apache.org/jira/browse/FLINK-20645
> Project: Flink
> Issue Type: Bug
> Reporter: Li Wang
> Priority: Major
> Labels: pull-request-available
> Attachments: jm.log, tm.log
>
>
> while starting task manager, I got the error below
> {code:java}
> "Caused by: org.apache.flink.configuration.IllegalConfigurationException: The
> required configuration option Key: 'taskmanager.cpu.cores' , default: null
> (fallback keys: []) is not set
> {code}
>
> Checking TM starting command I got something like
> {code:java}
> -D taskmanager.memory.framework.off-heap.size=134217728b -D
> taskmanager.memory.network.max=67108864b -D
> taskmanager.memory.network.min=67108864b -D
> taskmanager.memory.framework.heap.size=134217728b -D
> taskmanager.memory.managed.size=57346620b -D taskmanager.cpu.cores=1.0 -D
> taskmanager.memory.task.heap.size=1518663108b -D
> taskmanager.memory.task.off-heap.size=0b
> {code}
> Looks like the extra spaces between "-D" and parameters causes those dynamic
> options can't be passed in correctly.
> Related code is
> [here|https://github.com/apache/flink/blob/2ad92169a4a4ffc92d32783f8777a132e1dac7c4/flink-core/src/main/java/org/apache/flink/configuration/ConfigurationUtils.java#L180]
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
