[
https://issues.apache.org/jira/browse/FLINK-15488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009803#comment-17009803
]
Andrey Zagrebin commented on FLINK-15488:
-----------------------------------------
After offline discussion with [~trohrmann], we think that making the logs ofÂ
BashJavaUtils available for the user is important because it operates with
initial user configuration and started TM process already gets all calculated
values. Ideally, the logs should go into the same place as they configured by
user for the JVM process of TM. Whatever approach we take, we should try to
ensure that and check if possible. If the logs are outputted to stdout and the
program result as well then we could grep the result out by a special marker as
[~xintongsong]Â suggested but we need also to separate logs (e.g. inverse grep)
and forward them to stdout of taskmanager.sh. If it is too complicated we can
try the temporary file approach.
> 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)
