You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Yangze Guo (Jira)" <ji...@apache.org> on 2020/08/04 04:29:00 UTC

[jira] [Commented] (FLINK-18806) Taskmanager doesn't start up with error in config

    [ https://issues.apache.org/jira/browse/FLINK-18806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17170542#comment-17170542 ] 

Yangze Guo commented on FLINK-18806:
------------------------------------

FYI: That has been fixed in FLINK-18639.

> Taskmanager doesn't start up with error in config
> -------------------------------------------------
>
>                 Key: FLINK-18806
>                 URL: https://issues.apache.org/jira/browse/FLINK-18806
>             Project: Flink
>          Issue Type: Bug
>          Components: Deployment / Scripts
>    Affects Versions: 1.11.1
>            Reporter: Nico Kruber
>            Priority: Major
>
> With the following (wrong) configuration setting in {{flink-conf.yaml}}, a taskmanager will not start up, basically print nothing on the command line, and have no log file to look at:
> {code}
> taskmanager.memory.managed.fraction: '0.4'
> {code}
> Console output:
> {code}
> > ./bin/start-cluster.sh 
> Starting cluster.
> Starting standalonesession daemon on host Nico-PC.lan.
> [ERROR] The execution result is empty.
> [ERROR] Could not get JVM parameters and dynamic configurations properly.
> {code}



--
This message was sent by Atlassian Jira
(v8.3.4#803005)