[
https://issues.apache.org/jira/browse/RATIS-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16867886#comment-16867886
]
Tsz Wo Nicholas Sze commented on RATIS-573:
-------------------------------------------
{code}
- task.getFuture().completeExceptionally(e);
- throw e;
+ task.failed(e);
{code}
We should keep throwing the exception. Otherwise, the worker will continue
writing to the log. The log may end up corrupted silently. For example, one
entry has failed but then following entries are success. The log end up with
one entry missing.
> Handle Raft Log Append Failure
> ------------------------------
>
> Key: RATIS-573
> URL: https://issues.apache.org/jira/browse/RATIS-573
> Project: Ratis
> Issue Type: Improvement
> Components: server
> Reporter: Supratim Deka
> Assignee: Supratim Deka
> Priority: Major
> Attachments: RATIS-573.00.patch, RATIS-573.01.patch,
> RATIS-573.02.patch, RATIS-573.03.patch
>
>
> As part of Handling IO Failures, HDDS-1595.
> The scope of this jira is to handle failure in RAFT log append by:
> 1. notify the error to the state machine for consumer specific handling
> 2. propagate the error to the initiator (to the client from leader, to the
> leader from follower).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
