[
https://issues.apache.org/jira/browse/HDDS-1603?focusedWorklogId=267770&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-267770
]
ASF GitHub Bot logged work on HDDS-1603:
----------------------------------------
Author: ASF GitHub Bot
Created on: 26/Jun/19 16:39
Start Date: 26/Jun/19 16:39
Worklog Time Spent: 10m
Work Description: supratimdeka commented on pull request #1019:
HDDS-1603. Handle Ratis Append Failure in Container State Machine. Contributed
by Supratim Deka
URL: https://github.com/apache/hadoop/pull/1019
https://issues.apache.org/jira/browse/HDDS-1603
The scope of this jira is to build on
https://issues.apache.org/jira/browse/RATIS-573
and define the handling for Ratis log append failure in Ozone Container
State Machine.
1. Enqueue pipeline unhealthy action to SCM, add a reason code to the
message.
2. Trigger immediate heartbeat to SCM
Ratis-573 is not available in trunk. So this patch starts with an entry
point in XceiverServerRatis which will be hooked up to notifyLogFailed()
callback defined in StateMachine as part of RATIS-573.
Notify Ratis volume unhealthy to the Datanode is not implemented in this
patch
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 267770)
Time Spent: 10m
Remaining Estimate: 0h
> 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
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
