You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Dawid Wysakowicz (Jira)" <ji...@apache.org> on 2020/01/13 11:53:00 UTC
[jira] [Assigned] (FLINK-15519) Preserve logs from BashJavaUtils
and make them part of TM logs
[ https://issues.apache.org/jira/browse/FLINK-15519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dawid Wysakowicz reassigned FLINK-15519:
----------------------------------------
Assignee: Dawid Wysakowicz
> Preserve logs from BashJavaUtils and make them part of TM logs
> --------------------------------------------------------------
>
> Key: FLINK-15519
> URL: https://issues.apache.org/jira/browse/FLINK-15519
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Configuration
> Affects Versions: 1.10.0
> Reporter: Andrey Zagrebin
> Assignee: Dawid Wysakowicz
> Priority: Blocker
> Fix For: 1.10.0
>
>
> In FLINK-13983 we introduced BashJavaUtils utility to call in taskmanager.sh before starting TM and calculate memory configuration for the JVM process of TM.
> Ideally, it would be nice to preserve BashJavaUtils logs and make them part of the TM logs. Currently, logging for BashJavaUtils is configured from the class path and can differ from TM logging. Moreover TM logging can rewrite BashJavaUtils even if we align their loggings (e.g. log4j.appender.file.append=false in default log4j.properties for Flink).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)