Hi Senthil,
We never did get to the root cause unfortunately. Our kafka cluster is
currently owned by a different team and it wasn't a priority for them to
figure that out, or at least communicate the problem to us :(
Cheers,
Craig
On Thu, Jul 19, 2018 at 8:13 AM SenthilKumar K
wrote:
> Hi Cr
Hi Craig Ching,
Reg. *We did end up turning on debug logs for the console consumer and
found that one broker seemed to be having problems, it would lead to
timeouts communicating with it. After restarting that broker, things
sorted themselves out.*
We had similar problem on prod cluster and i'm
Hi Manikumar!
Thanks for responding! Sorry it took me so long to get back!
We did end up turning on debug logs for the console consumer and found that one
broker seemed to be having problems, it would lead to timeouts communicating
with it. After restarting that broker, things sorted themselv
Can you post consumer debug logs?
You can enable console consumer debug logs here:
kafka/config/tools-log4j.properties
On Wed, Jun 13, 2018 at 9:55 AM Craig Ching wrote:
> Hi!
>
> We’re having a problem with a new kafka cluster at 1.1.0. The problem is,
> in general, that consumers can’t consum
Hi!
We’re having a problem with a new kafka cluster at 1.1.0. The problem is, in
general, that consumers can’t consume from the different broker (old broker was
0.11 I think). The easiest recipe I have for reproducing the problem is that
downloading kafka 1.0.1 and running console consumer ca