You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Supratim Deka (JIRA)" <ji...@apache.org> on 2019/07/01 15:43:00 UTC
[jira] [Assigned] (HDDS-1603) Handle Ratis Append Failure in
Container State Machine
[ https://issues.apache.org/jira/browse/HDDS-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Supratim Deka reassigned HDDS-1603:
-----------------------------------
Assignee: Supratim Deka
> 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
> Time Spent: 20m
> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org