[
https://issues.apache.org/jira/browse/RATIS-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16674034#comment-16674034
]
Hadoop QA commented on RATIS-352:
---------------------------------
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue} 0m
24s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red} 0m 4s{color}
| {color:red} RATIS-352 does not apply to master. Rebase required? Wrong
Branch? See https://yetus.apache.org/documentation/0.5.0/precommit-patchnames
for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| Docker | Client=17.05.0-ce Server=17.05.0-ce Image:yetus/ratis:date2018-11-03
|
| JIRA Issue | RATIS-352 |
| JIRA Patch URL |
https://issues.apache.org/jira/secure/attachment/12946188/r352_20181030.patch |
| Console output |
https://builds.apache.org/job/PreCommit-RATIS-Build/486/console |
| Powered by | Apache Yetus 0.5.0 http://yetus.apache.org |
This message was automatically generated.
> 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_20181030.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)
