You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Gary Yao (Jira)" <ji...@apache.org> on 2020/01/13 09:45:00 UTC
[jira] [Closed] (FLINK-15488) Cannot start a taskmanger if using
logback
[ https://issues.apache.org/jira/browse/FLINK-15488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Yao closed FLINK-15488.
----------------------------
Resolution: Fixed
1.10: 6c886ade7c02840423552025f5d5da535ae40d02
master: d76f2166396e3758c08851d024e2c23c8a297062
> 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
> Assignee: Yangze Guo
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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
(v8.3.4#803005)