you can use one more auto.offset.reset=smallest/largest. I ALSO face
the same issue and it work fine for me . Might be my key name is not
correct, please check the key in kafka doxumentation ?..
On 4/6/15, Madhukar Bharti wrote:
> Hi Mayuresh,
>
> We are having only one consumer in the group and
Can you resend the logs?
Also I did not get what you meant by :
"Sometimes after restart consumers picks the messages sometimes it starts
but not receives any messages. "
Thanks,
Mayuresh
On Wed, Apr 22, 2015 at 5:20 AM, Madhukar Bharti
wrote:
> Hi All,
>
> Any update on this? We are facing s
Hi All,
Any update on this? We are facing same issue all the time when ever we
re-start consumers.
On Mon, Apr 6, 2015 at 11:19 PM, Madhukar Bharti
wrote:
> Hi Mayuresh,
>
> We are having only one consumer in the group and only one partition for
> that topic.
> We have set auto.commit.enable fa
Hi Mayuresh,
We are having only one consumer in the group and only one partition for
that topic.
We have set auto.commit.enable false, zookeeper.session.timeout.ms=6,
rebalance.backoff.ms to 2000 and rebalance.max.retries to 20.
Thanks!
On Mon, Apr 6, 2015 at 9:59 PM, Mayuresh Gharat
wrote:
It actually depends on how many consumers you have in the same group and
how many partitions the particular topic has.
Can you elaborate on your configuration?
Thanks,
Mayuresh
On Mon, Apr 6, 2015 at 3:35 AM, Madhukar Bharti
wrote:
> Hi All,
>
> We are facing issue with Kafka high Level consu
Hi All,
We are facing issue with Kafka high Level consumers. We are using 0.8.1.1
version. Sometimes after restart consumers picks the messages sometimes it
starts but not receives any messages. Is high level consumer is not
reliable?
I have checked with the log. Even if re-balance succeed, consu
