flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yangze Guo (Jira)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-15488) Cannot start a taskmanger if using logback
Date Tue, 07 Jan 2020 09:56:00 GMT

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

Yangze Guo commented on FLINK-15488:

Disable logging makes sense to me. Actually, it's a bit odd to allow logging in this utility

> Cannot start a taskmanger if using logback
> ------------------------------------------
>                 Key: FLINK-15488
>                 URL: https://issues.apache.org/jira/browse/FLINK-15488
>             Project: Flink
>          Issue Type: Bug
>          Components: API / Core, Deployment / Scripts
>    Affects Versions: 1.10.0
>            Reporter: Dawid Wysakowicz
>            Priority: Blocker
>             Fix For: 1.10.0
> When using logback it is not possible to start the taskmanager using {{taskamanger.sh}}
scripts. The same problem (probably) occurs when using slf4j that logs into the console.
> The problem is that when calculating memory configuration with {{BashJavaUtils}} class
the result is returned through standard output. If something is logged into the console it
may result in undefined behavior such as e.g. 
> {code}
> Error: Could not find or load main class 13:51:23.961
> {code}

This message was sent by Atlassian Jira

View raw message