[
https://issues.apache.org/jira/browse/RATIS-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16687364#comment-16687364
]
Tsz Wo Nicholas Sze commented on RATIS-409:
-------------------------------------------
> commitIndexChanged method doesn't set ReplicationLevel.MAJORITY. ...
ReplicationLevel.MAJORITY is taken care in LeaderState.updateCommit(long
majority, long min). It will call ServerState.updateStatemachine(..) and then
log.updateLastCommitted(..). It is the only way that the index for
eplicationLevel.MAJORITY will change.
> 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
>
>
> 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)
