Arpit, Unfortunately from that description nothing specific is coming to mind. The max.poll.interval indicates that the consumer is losing contact with the Kafka cluster, but that may be caused by the replication application hanging somewhere else.
Some clarifying questions, and things you can look into: 1. Are you using MirrorMaker, or MirrorMaker 2.0? 2. What version of MM or MM2 are you using, and with what Kafka broker version? 3. How is your replication flow configured? 4. What is the frequency and duration of these interruptions? 5. When did the interruptions start? 6. Has anything changed in your environment recently, such as new partitions or an upgrade? 7. Are you seeing any ERROR logs or other unique logs from the replication flow? 8. Have you tried enabling more detailed logs and watched the progress of the replication flow around the time it stops replicating? Thanks, Greg Harris On Tue, Feb 7, 2023 at 6:27 AM Arpit Jain <jain.arp...@gmail.com> wrote: > Hi, > > Hope this is the right forum to ask for Kafka mirror maker issues. > We are facing an issue where the mirror maker replicates the trades and > then doesn't work for long time and again replicates. > Also seeing the warning message to increase the poll interval or decrease > the maximum batch size (max.poll.records). > > I have tried reducing max.poll.records to 250 but still same issues. > > Could anyone suggest what could be wrong? > > Thanks >
