I am using the 0.9.0.0 log4j appender for Kafka because I have a lot of apps
dependent on log4j 1.2.x that cannot be upgraded to use newer versions of
log4j. It appears that the appender has become part of log4j code in later
versions of both tools.
When I start my test app, the first message
Hello Laven / Eric,
I personally cannot think of any more bug fixes than KAFKA-5152 that is
trying to solve a relative issue, and we would love to know what did you
observe that in 0.11.0.1 this issue still exists: i.e. the first instance
is stuck with the rebalance state, as we have moved the res
Hi all,
Recently we have upgraded our cluster from 0.10.0.1 to 0.11.0.1. After few
hours of upgrade we faced issue of too many closed_wait connection. Latter
got to know that this is a bug and got fixed in 1.0.0.
As of now we can’t take this as there is still possible known bugs are
there, we nee
If you could provide more details about the kind of issues you saw when you
downgraded (e.g. error logs, behavior, etc) it might help folks help you.
At the moment, I wouldn't know where to begin with the issue you've
described as there's not a ton of detail about what, exactly, went wrong.
On Sun
Is the topic to which the message is being produced, already present or
is it auto created?
-Jaikiran
On 05/11/17 3:43 PM, Dale wrote:
I am using the 0.9.0.0 log4j appender for Kafka because I have a lot of apps
dependent on log4j 1.2.x that cannot be upgraded to use newer versions of
log4j
Hi Guozhang, I will talk to the team about prioritizing the recreation of this
scenario and gathering logs.
- Eric
> On Nov 5, 2017, at 9:39 AM, Guozhang Wang wrote:
>
> Hello Laven / Eric,
>
> I personally cannot think of any more bug fixes than KAFKA-5152 that is
> trying to solve a relativ
