[
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16662354#comment-16662354
]
Tsz Wo Nicholas Sze commented on RATIS-352:
-------------------------------------------
Thanks [~jnp] for reviewing the patch.
Since this feature add Metadata entries to the Raft log, the tests expecting
consecutive log index fail intermittently. It seems better to first fix the
tests (so that they won't depends on consecutive log index) and then commit
this patch. Let me file a JIRA.
> Persist commit index in Raft log.
> ---------------------------------
>
> Key: RATIS-352
> URL: https://issues.apache.org/jira/browse/RATIS-352
> Project: Ratis
> Issue Type: Improvement
> Components: server
> Reporter: Tsz Wo Nicholas Sze
> Assignee: Tsz Wo Nicholas Sze
> Priority: Major
> Attachments: r352_20181024.patch
>
>
> Current the commit index is not persisted in the Raft log. When a server
> restarts, it cannot apply its log until it has joined a Raft group. There is
> no problem if there is a Raft group.
> However, a server cannot recover its data when formatting a Raft group is
> impossible (e.g. a majority of servers are dead). Ideally, a server can
> safely apply the log up to the commit index. The JIRA is to persist the
> commit index so that such recovery is possible.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
