[
https://issues.apache.org/jira/browse/FLINK-18829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17327702#comment-17327702
]
Flink Jira Bot commented on FLINK-18829:
----------------------------------------
This major issue is unassigned and itself and all of its Sub-Tasks have not
been updated for 30 days. So, it has been labeled "stale-major". If this ticket
is indeed "major", please either assign yourself or give an update. Afterwards,
please remove the label. In 7 days the issue will be deprioritized.
> Remove logback-related codepaths and configuration file
> -------------------------------------------------------
>
> Key: FLINK-18829
> URL: https://issues.apache.org/jira/browse/FLINK-18829
> Project: Flink
> Issue Type: Task
> Components: Deployment / Scripts, Runtime / Coordination
> Reporter: Robert Metzger
> Priority: Major
> Labels: stale-major, starter
>
> Flink currently (1.12-SNAPSHOT) provides support for two logging backends:
> Log4j2 (default) and logback.
> The logback support is not really covered by our testing, and there's little
> evidence of widespread use.
> Users can use a custom logging backend (as long as it's supported by slf4j)
> by providing the appropriate configuration files and jars in the classpath of
> all Flink services. Therefore, we should remove the logback-related files and
> codepaths in Flink and let our users set things up themselves.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
