`max.poll.intervall.ms` is the maximum allowed time between two calls to
`poll()`.
Hence, this config seems to be unrelated. For the background heartbeat
thread there would be `session.timeout.ms` config but this also seems to
be unrelated.
What I don't fully understand is, what you try to
Hi Ryan,
Have you tried Consumer's pause/resume methods?
Steve
On Wed, Mar 25, 2020, 17:13 Kamal Chandraprakash <
kamal.chandraprak...@gmail.com> wrote:
> With group coordination protocol, you only have to increase the `
> max.poll.interval.ms` / `max.poll.records`.
> Ignore the above
With group coordination protocol, you only have to increase the `
max.poll.interval.ms` / `max.poll.records`.
Ignore the above messages. Consumer heartbeats are processed in a separate
thread.
On Wed, Mar 25, 2020 at 2:35 PM Kamal Chandraprakash <
kamal.chandraprak...@gmail.com> wrote:
> Yes,
Yes, with `assign` you'll lose the group coordination. You can still use
the `subscribe` mode, update the above mentioned configs.
You're ask is kind of Delay Queue. Kafka Consumer doesn't support that
feature. You've to manually `sleep` in between the poll calls.
On Tue, Mar 24, 2020 at 11:56 PM
Don't I lose consumer group coordination with assign?
On Mon, Mar 23, 2020 at 11:49 PM Kamal Chandraprakash <
kamal.chandraprak...@gmail.com> wrote:
> Hi Ryan,
>
> The maxPollInterval waits for at-most the given time duration and returns
> ASAP even if a single record is available.
> If you want
Hi Ryan,
The maxPollInterval waits for at-most the given time duration and returns
ASAP even if a single record is available.
If you want to collect data once 30-45 minutes, better to use the Consumer
with `assign` mode and poll for records
once in 30 minutes.
If you're using the consumer with
