[
https://issues.apache.org/jira/browse/KAFKA-7095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16522504#comment-16522504
]
Jason Gustafson commented on KAFKA-7095:
----------------------------------------
See
[KIP-211|https://cwiki.apache.org/confluence/display/KAFKA/KIP-211%3A+Revise+Expiration+Semantics+of+Consumer+Group+Offsets]
which will go into the next release. You shouldn't need to restart your
application in order to consumer the next offset even if the committed offset
is lost. What `auto.offset.reset` policy are you using?
> Low traffic consumer is not consuming messages after the offsets is deleted
> by Kafka
> ------------------------------------------------------------------------------------
>
> Key: KAFKA-7095
> URL: https://issues.apache.org/jira/browse/KAFKA-7095
> Project: Kafka
> Issue Type: Bug
> Components: clients
> Affects Versions: 0.10.1.1
> Reporter: Aldo Sinanaj
> Priority: Minor
>
> Hello guys.
> I have a low traffic consumers for a given consumer group and I have the
> default broker setting for this property *offsets.retention.minutes*. So if a
> messages is coming after 2 days and Kafka has deleted the offset for that
> given consumer, then the consumer will not consume the new incoming messages.
> If I restart the application it will consume from the earliest which is
> obvious since the offset is deleted.
> My question is why it doesn't consume the new messages if I don't restart the
> application? And how does this version of Kafka understands if a consumer is
> active or inactive? Is my consumer considered inactive in this case?
> Thanks,
> Aldo
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
