[
https://issues.apache.org/jira/browse/FLINK-18438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17361826#comment-17361826
]
Derek Moore commented on FLINK-18438:
-------------------------------------
[~JohnSiro], [~cr0566], [~xintongsong], et al.,
The issue a ^M character at the end of the argument. In this bug report it
shows as a space in the original report. In FLINK-18792, it is shown as a
newline (notice the wrapped quote character).
A number followed by ^M is an improperly specified option. You can use `less`
to see the control character in the logs.
Haven't figured out how to get rid of the ^M character yet!
I recently pulled down Flink 1.13.1 & latest Cygwin, and I get this error.
Things work even less under Git Bash.
> TaskManager start failed
> ------------------------
>
> Key: FLINK-18438
> URL: https://issues.apache.org/jira/browse/FLINK-18438
> Project: Flink
> Issue Type: Bug
> Components: Client / Job Submission
> Affects Versions: 1.10.1
> Environment: Java: java version "1.8.0_101"
> Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)
> Flink: 1.10.1 (flink-1.10.1-bin-scala_2.12.tgz)
> OS: Windows 10 (1903) / 64-bits
> Reporter: JohnSiro
> Priority: Minor
> Labels: auto-deprioritized-major
> Fix For: 1.10.4, 1.11.4, 1.14.0
>
>
>
> Error: in file xxx-taskexecutor-0-xxx.out is:
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> Improperly specified VM option 'MaxMetaspaceSize=268435456 '
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
