[
https://issues.apache.org/jira/browse/RATIS-573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16866802#comment-16866802
]
Supratim Deka commented on RATIS-573:
-------------------------------------
addressed comments from [~szetszwo] in patch 02 :
1. resolved the conflict with trunk.
2. passing LogEntryProto as a Optional to notifyLogFailed(). Made it a Optional
because the same notification also triggers for FinalizeLogSegment. As of now,
imho, there is no requirement to separate out the 2 scenarios. Later if the
need arises, we can revisit.
> 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
>
>
> 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)
