[
https://issues.apache.org/jira/browse/FLINK-17527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17102558#comment-17102558
]
Yang Wang commented on FLINK-17527:
-----------------------------------
Yes, we could start with renaming {{log4j-yarn-session.properties}} to
{{log4j-session.properties}} and used by yarn session and K8s session. It will
have very similar functionality with {{log4j-console.properties}}. And we could
do the unification later.
> kubernetes-session.sh uses log4j-console.properties
> ---------------------------------------------------
>
> Key: FLINK-17527
> URL: https://issues.apache.org/jira/browse/FLINK-17527
> Project: Flink
> Issue Type: Sub-task
> Components: Deployment / Kubernetes
> Affects Versions: 1.10.0
> Reporter: Till Rohrmann
> Priority: Major
> Fix For: 1.11.0, 1.10.2
>
>
> It is a bit confusing that {{kubernetes-session.sh}} uses the
> {{log4j-console.properties}}. At the moment, {{flink}} used
> {{log4j-cli.properties}}, {{yarn-session.sh}} uses
> {{log4j-yarn-session.properties}} and {{kubernetes-session.sh}} uses
> {{log4j-console.properties}}.
> I would suggest to let all scripts use the same logger configuration file
> (e.g. {{logj4-cli.properties}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
