[
https://issues.apache.org/jira/browse/FLINK-15488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009331#comment-17009331
]
Xintong Song commented on FLINK-15488:
--------------------------------------
Thanks for reporting this issue, [~dwysakowicz]. This is indeed a design defect.
I think the simplest solution might be {{BashJavaUtils}} output the result with
a specific key or pattern, so that {{taskmanager.sh} can find result among
other potential outputs.
Or we can write the results into a temporal file. This is safer but a bit more
complicate. We need to have unique per-TM file paths to avoid potential
conflicts between multiple TMs, and also handle the file clean-ups
I think the first approach might be good enough. WDYT?
[~azagrebin][~dwysakowicz][~gjy]
> 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)
