You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "huxihx (JIRA)" <ji...@apache.org> on 2019/05/15 04:02:00 UTC

[jira] [Assigned] (KAFKA-8338) Improve consumer offset expiration logic to take subscription into account

     [ https://issues.apache.org/jira/browse/KAFKA-8338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

huxihx reassigned KAFKA-8338:
-----------------------------

    Assignee: huxihx

> Improve consumer offset expiration logic to take subscription into account
> --------------------------------------------------------------------------
>
>                 Key: KAFKA-8338
>                 URL: https://issues.apache.org/jira/browse/KAFKA-8338
>             Project: Kafka
>          Issue Type: Improvement
>            Reporter: Gwen Shapira
>            Assignee: huxihx
>            Priority: Major
>
> Currently, we expire consumer offsets for a group after the group is considered gone.
> There is a case where the consumer group still exists, but is now subscribed to different topics. In that case, the offsets of the old topics will never expire and if lag is monitored, the monitors will show ever-growing lag on those topics. 
> We need to improve the logic to expire the consumer offsets if the consumer group didn't subscribe to specific topics/partitions for enough time.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)