Hi Shimi, Could you provide more info on your setup? How many kafka streams processes do you have and from how many partitions are they consuming from. If you have more processes than partitions some of the processes will be idle and won’t do anything.
Eno > On Apr 30, 2017, at 5:58 PM, Shimi Kiviti <shim...@gmail.com> wrote: > > Hi Everyone, > > I have a problem and I hope one of you can help me figuring it out. > One of our kafka-streams processes stopped processing messages > > When I turn on debug log I see lots of these messages: > > 2017-04-30 15:42:20,228 [StreamThread-1] DEBUG o.a.k.c.c.i.Fetcher: Sending > fetch for partitions [devlast-changelog-2] to broker ip-x-x-x-x > .ec2.internal:9092 (id: 1 rack: null) > 2017-04-30 15:42:20,696 [StreamThread-1] DEBUG o.a.k.c.c.i.Fetcher: > Ignoring fetched records for devlast-changelog-2 at offset 2962649 since > the current position is 2963379 > > After a LONG time, the only messages in the log are these: > > 2017-04-30 16:46:33,324 [kafka-coordinator-heartbeat-thread | sa] DEBUG > o.a.k.c.c.i.AbstractCoordinator: Sending Heartbeat request for group sa to > coordinator ip-x-x-x-x.ec2.internal:9092 (id: 2147483646 rack: null) > 2017-04-30 16:46:33,425 [kafka-coordinator-heartbeat-thread | sa] DEBUG > o.a.k.c.c.i.AbstractCoordinator: Received successful Heartbeat response for > group same > > Any idea? > > Thanks, > Shimi
