[
https://issues.apache.org/jira/browse/HDDS-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Kumar Singh updated HDDS-1603:
------------------------------------
Resolution: Fixed
Fix Version/s: 0.5.0
Status: Resolved (was: Patch Available)
Thanks for the contribution [~sdeka] and [~arp] for the review.
Lets create 2 followups,
a) A end to end unit test with failures in raft log to test the handling of the
code
b) Also lets add new failures in the enum to ensure that all the errors are
propagated correctly to SCM.
> Handle Ratis Append Failure in Container State Machine
> ------------------------------------------------------
>
> Key: HDDS-1603
> URL: https://issues.apache.org/jira/browse/HDDS-1603
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: Ozone Datanode, SCM
> Reporter: Supratim Deka
> Assignee: Supratim Deka
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.5.0
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> RATIS-573 would add notification to the State Machine on encountering failure
> during Log append.
> The scope of this jira is to build on RATIS-573 and define the handling for
> log append failure in Container State Machine.
> 1. Enqueue pipeline unhealthy action to SCM, add a reason code to the message.
> 2. Trigger heartbeat to SCM
> 3. Notify Ratis volume unhealthy to the Datanode, so that DN can trigger
> async volume checker
> Changes in the SCM to leverage the additional failure reason code, is outside
> the scope of this jira.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
