[
https://issues.apache.org/jira/browse/FLINK-18639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17161079#comment-17161079
]
Xintong Song edited comment on FLINK-18639 at 7/20/20, 9:45 AM:
----------------------------------------------------------------
Fixed via:
* master: 7adbbd3d1f085789dfd31eab4b170838ef665255
* release-1.11: 85e66e856d11151da61ef5677941c99809c01f4c
was (Author: xintongsong):
Fixed via:
master: 7adbbd3d1f085789dfd31eab4b170838ef665255
release-1.11: 85e66e856d11151da61ef5677941c99809c01f4c
> Error messages from BashJavaUtils are eaten
> -------------------------------------------
>
> Key: FLINK-18639
> URL: https://issues.apache.org/jira/browse/FLINK-18639
> Project: Flink
> Issue Type: Bug
> Components: Deployment / Scripts
> Affects Versions: 1.11.0, 1.12.0
> Reporter: Xintong Song
> Assignee: Xintong Song
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.12.0, 1.11.1
>
>
> Shell scripts execute BashJavaUtils for generating memory related JVM
> parameters and dynamic configurations. When there's a problem in
> configuration that the memory sizes cannot be properly calculated, the script
> will not launch the Flink daemon and exit with non-zero code. In such cases,
> error messages from BashJavaUtils describing the reason of failure are
> missing, making it hard for users to understand what's wrong and how to fix
> the problem.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
