[
https://issues.apache.org/jira/browse/RATIS-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16431688#comment-16431688
]
Kit Hui commented on RATIS-208:
-------------------------------
# Combine runTestBasicAppendEntries and runTestBasicAppendEntries2 by setting
up the parameter ReplicationLevel.
# To make sure all the server is running in the test case
"runTestBasicAppendEntries", restart all server before the test code.
# Testing if it is work when the server is killed and restart after few
seconds.
Thanks.
> Allow client to specify replication level in a request
> ------------------------------------------------------
>
> Key: RATIS-208
> URL: https://issues.apache.org/jira/browse/RATIS-208
> Project: Ratis
> Issue Type: New Feature
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Kit Hui
> Priority: Major
> Attachments: r208_20180410.patch, r208_20180410b.patch
>
>
> In Raft protocol, the leader sends a reply to client once the request is
> committed and applied to its state machine. A request is committed when the
> leader get a majority of responses from all the members in the raft group.
> In some applications, the client may want to wait for all member responses
> instead of a majority. For example, the application wants to support reading
> even if there is only one machine remaining in the group.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
