[
https://issues.apache.org/jira/browse/KAFKA-17860?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910056#comment-17910056
]
Piotr Karwasz commented on KAFKA-17860:
---------------------------------------
[~vedarth]
I don't think it is worth the effort.
The {{Kafka}} appender in Log4j is also deprecated for *removal*. Before
deprecating it, we published a [poll on
{{log4j-user@logging}}|https://lists.apache.org/thread/76f260b933ol7og757123lyl1ckjvm8y]
in September 2023. I also created a [thread on
{{dev@kafka}}|https://lists.apache.org/thread/9logy8yv3v3tom8kd45sq01nl2qfxcx7]
in October 2024. In both threads there were no messages to keep the appender.
No user ever asked to keep the {{Kafka}} appender, sent a PR to fix its bugs or
proposed to co-maintain it in the past few years. I think it is safe to assume
that the appender is not used in production.
The `Kafka` appender needs a lot of love that nobody has time to give. The
current version can even [cause deadlocks if
misconfigured|https://github.com/apache/logging-log4j2/issues/2893] if both the
Kafka client and Log4j are using asynchronous threads.
> Remove log4j-appender module
> ----------------------------
>
> Key: KAFKA-17860
> URL: https://issues.apache.org/jira/browse/KAFKA-17860
> Project: Kafka
> Issue Type: Sub-task
> Reporter: Chia-Ping Tsai
> Assignee: TengYao Chi
> Priority: Major
> Fix For: 4.0.0
>
>
> as title, we need to remove it first in order to upgrade log4j
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
