[
https://issues.apache.org/jira/browse/FLINK-15488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17010737#comment-17010737
]
Andrey Zagrebin commented on FLINK-15488:
-----------------------------------------
BashJavaUtils is single-threaded atm. I do not see any reason for the result
not to be the last line of stdout. In that case, we can just tail it from the
output. We can have a sanity check by prefixing result with some string and
assert it in bash to fail fast if this contract breaks.
For the logs, this looks like another issue which we have to tackle
independently. Ideally, it would be nice to preserve BashJavaUtils logs and
make them part of the task manager logs. I have created an issue for that
[FLINK-15519|https://jira.apache.org/jira/browse/FLINK-15519].
> 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)
