[ 
https://issues.apache.org/jira/browse/KAFKA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14981552#comment-14981552
 ] 

ASF GitHub Bot commented on KAFKA-2017:
---------------------------------------

GitHub user guozhangwang opened a pull request:

    https://github.com/apache/kafka/pull/386

    KAFKA-2017: Persist Group Metadata and Assignment before Responding

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/guozhangwang/kafka K2017

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/kafka/pull/386.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #386
    
----
commit c00cebd93262ab9e0f1a9ea164902ab7ef0c800a
Author: Guozhang Wang <wangg...@gmail.com>
Date:   2015-10-29T22:07:17Z

    move group metadata into offset manager

commit 17a83eb8529a57a97826473919764a02db1ca3b4
Author: Guozhang Wang <wangg...@gmail.com>
Date:   2015-10-29T22:10:50Z

    add back package.html

commit 1f2579d941fe25038738ec8e93f8b480ab7e7fe7
Author: Guozhang Wang <wangg...@gmail.com>
Date:   2015-10-29T23:28:32Z

    persist synced assignment and client side error handling

----


> 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
>            Priority: Blocker
>             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)

Reply via email to