[
https://issues.apache.org/jira/browse/FLINK-18153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17140387#comment-17140387
]
Chesnay Schepler commented on FLINK-18153:
------------------------------------------
The issue imo isn't so much about this particular case; more generally, if the
JVM startup fails _for any reason_, we don't really handle it.
> flink-daemon does not detect errors if JVM crashes immediately
> --------------------------------------------------------------
>
> Key: FLINK-18153
> URL: https://issues.apache.org/jira/browse/FLINK-18153
> Project: Flink
> Issue Type: Bug
> Components: Runtime / Coordination
> Affects Versions: 1.11.0
> Reporter: Chesnay Schepler
> Priority: Major
>
> Configuring obscenely large amounts of memory that exceed the machine, which
> prevents the JVM startup, does not result in any error to be printed to the
> console. The logs are empty, and the only hint for an error is found in the
> .out file.
> {code}
> OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00007aaf70000000,
> 5241403604992, 0) failed; error='Not enough space' (errno=12)
> #
> # There is insufficient memory for the Java Runtime Environment to continue.
> # Native memory allocation (mmap) failed to map 5241403604992 bytes for
> committing reserved memory.
> {code}
> This behavior is just a bit too subtle.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
