[ https://issues.apache.org/jira/browse/FLINK-15488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009568#comment-17009568 ]
Yang Wang commented on FLINK-15488: ----------------------------------- I think using a fixed pattern to extract the wanted information makes sense to me. It is more straightforward. Maybe we could add an argument {{--disable-logging}} to the {{BashJavaUtils}}. The new added arg is used to disable all the logs so that the stdout is cleaner. {code:java} Logger.getRootLogger().setLevel(Level.OFF); {code} > 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 (v8.3.4#803005)