[FLINK-17527] kubernetes-session.sh uses log4j-console.properties

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.10.0
• Fix Version/s: 1.11.0
• Component/s: Deployment / Kubernetes
• Labels: pull-request-available
• Release Note: The logging properties files `log4j-yarn-session.properties` and `logback-yarn.xml` haven been renamed into `log4j-session.properties` and `logback-session.xml`. Moreover, `yarn-session.sh` and `kubernetes-session.sh` use these logging properties files.
• Assignee: Yang Wang
• Reporter: Till Rohrmann
• Created: 05/May/20 13:42
• Updated: 16/Oct/20 10:50
• Resolved: 19/May/20 13:01

Description

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.

Issue Links

• links to: GitHub Pull Request #12236