Hi Ken,

Yes, it is a kind of behavior change even though we are fixing the "broken
logic". There may be users who want to override the whole logger definition
via our exposed envs. Therefore, I'm ok with adding the "needs-kip" label
to the ticket.

I have created
https://www.google.com/url?q=https://issues.apache.org/jira/browse/KAFKA-21556&source=gmail&ust=1795006614092000&sa=E,
and more feedback is still welcome.

Best,
Chia-Ping

On Tue, Nov 17, 2026 05:31 PM, Luke Chen <[email protected]> wrote:

> Hi Chia-Ping,
>
> To be honest, I'm not familiar with the log4j2 composite, but if the log4j2
> composite configuration solution can simplify our setup and reduce the pain
> of merging the custom log4j2 configs, I think that's a good idea.
>
>
> Thanks,
> Luke
>
>
> On Tue, Nov 17, 2026 at 12:56 AM 黃竣陽 <[email protected]> wrote:
>
> > Hello Chia,
> >
> > Thanks for raising this. +1 on the direction.
> >
> > The current mechanism has quite a few bugs, but switching to Log4j2
> > composite
> > configuration would still change user-visible behavior. Some combinations
> > of environment
> > variables that work a certain way today could result in a different
> > effective configuration.
> >
> > Since the Docker image and its environment-variable-based configuration
> > are effectively
> > user-facing, should we write a KIP to document the proposed changes?
> >
> > Best Regards,
> > Jiunn-Yang
> >
> > > Chia-Ping Tsai <[email protected]> 於 2026年11月15日 下午5:39 寫道:
> > >
> > > Hi all,
> > >
> > > I'd like to raise a behavior change to the wrapper of our Docker image
> > > (KafkaDockerWrapper).
> > >
> > > Our wrapper supports configuring the log4j2 yaml via env, but it has
> many
> > > issues after we migrated to log4j2 (KAFKA-21460, KAFKA-21520). The root
> > > cause is that we are re-implementing the log4j2 composition in Kafka.
> > >
> > > That is weird to me. As an OSS project, why don't we reuse the log4j2
> > > composition instead of maintaining a duplicate implementation that does
> > not
> > > work well? To be fair, I am the one who merged it, so I am mostly
> > > complaining about myself.
> > >
> > > Therefore, I'd like to propose delegating this function to log4j2
> itself.
> > > We can generate an extra yaml file according to the envs, and then pass
> > the
> > > original yaml together with this extra yaml file via the log4j2
> composite
> > > configuration.
> > >
> > > Of course, the delegation brings both good things and bad things. I can
> > > list all of them later if anyone has enough tokens to parse this mail,
> > but
> > > it would be good to hear any feedback about this idea first.
> > >
> > > Best,
> > > Chia-Ping
> >
> >
>

Reply via email to