kafka-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jun Rao (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KAFKA-2017) Persist Coordinator State for Coordinator Failover
Date Mon, 12 Oct 2015 20:16:05 GMT

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

Jun Rao updated KAFKA-2017:
---------------------------
    Affects Version/s:     (was: 0.10.0.0)
                       0.9.0.0
        Fix Version/s:     (was: 0.10.0.0)
                       0.9.0.0

An impact is that if we don't persist the coordinator state, during the coordinator failover,
existing consumers won't be able to commit offsets during rebalances since the new coordinator
doesn't know existing members of the group. This can potentially introduce duplicates in the
new consumer, which is a degradation from the old consumer.

> Persist Coordinator State for Coordinator Failover
> --------------------------------------------------
>
>                 Key: KAFKA-2017
>                 URL: https://issues.apache.org/jira/browse/KAFKA-2017
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: consumer
>    Affects Versions: 0.9.0.0
>            Reporter: Onur Karaman
>            Assignee: Guozhang Wang
>             Fix For: 0.9.0.0
>
>         Attachments: KAFKA-2017.patch, KAFKA-2017_2015-05-20_09:13:39.patch, KAFKA-2017_2015-05-21_19:02:47.patch
>
>
> When a coordinator fails, the group membership protocol tries to failover to a new coordinator
without forcing all the consumers rejoin their groups. This is possible if the coordinator
persists its state so that the state can be transferred during coordinator failover. This
state consists of most of the information in GroupRegistry and ConsumerRegistry.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message