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

Posted to issues@ratis.apache.org by "Tsz Wo Nicholas Sze (JIRA)" <ji...@apache.org> on 2018/11/16 02:46:00 UTC

[jira] [Comment Edited] (RATIS-409) Watch requests may not work if there is a conf change

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

Tsz Wo Nicholas Sze edited comment on RATIS-409 at 11/16/18 2:45 AM:
---------------------------------------------------------------------

r409_20181115.patch: fixes a bug: commitIndex should be updated using max.

It also keeps updating MAJORITY in commitIndexChanged().


was (Author: szetszwo):
r409_20181115.patch: fixes a bug: commitIndex should be updated using max.

> Watch requests may not work if there is a conf change
> -----------------------------------------------------
>
>                 Key: RATIS-409
>                 URL: https://issues.apache.org/jira/browse/RATIS-409
>             Project: Ratis
>          Issue Type: Bug
>          Components: server
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>            Priority: Major
>         Attachments: r409_20181112.patch, r409_20181113.patch, r409_20181113b.patch, r409_20181115.patch
>
>
> When there is commitIndex changed, the watchRequests is updated with the indices in SenderList.  However, when there is a conf change, SenderList includes all servers in both old and new confs.  As a result, the computed indices may be incorrect.



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