[
https://issues.apache.org/jira/browse/FLINK-15488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009802#comment-17009802
]
Dawid Wysakowicz commented on FLINK-15488:
------------------------------------------
[~gjy] [~fly_in_gis]'s explanation is on point.
[~xintongsong] I think using a regex is very fragile, I would not go that
route. I would rather change the utility class to produce a deterministic
result and disabling the logging sounds like a sensible solution. Maybe it
could also make sense to overwrite the std out to make sure nothing else writes
there. Similar to what
{{org.apache.flink.client.program.OptimizerPlanEnvironment#getPipeline}} does.
I don't have a strong opinion though.
> 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)
