hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Work logged] (HDDS-1610) applyTransaction failure should not be lost on restart
Date Wed, 07 Aug 2019 02:25:00 GMT

     [ https://issues.apache.org/jira/browse/HDDS-1610?focusedWorklogId=290175&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-290175

ASF GitHub Bot logged work on HDDS-1610:

                Author: ASF GitHub Bot
            Created on: 07/Aug/19 02:24
            Start Date: 07/Aug/19 02:24
    Worklog Time Spent: 10m 
      Work Description: bshashikant commented on issue #1226: HDDS-1610. applyTransaction
failure should not be lost on restart.
URL: https://github.com/apache/hadoop/pull/1226#issuecomment-518913410
   Thanks @mukul1987 . In ratis, as fara as my understanding goes, before taking a snapshot
we wait for all the pending applyTrannsaction futures to complete and since now with the patch,
the applyTransaction exception is being propagated to Ratis, ideally snapshot creation will
fail in Ratis.
   I will address the remaining review comments as part of the next 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:

Issue Time Tracking

    Worklog Id:     (was: 290175)
    Time Spent: 3h 10m  (was: 3h)

> applyTransaction failure should not be lost on restart
> ------------------------------------------------------
>                 Key: HDDS-1610
>                 URL: https://issues.apache.org/jira/browse/HDDS-1610
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Shashikant Banerjee
>            Assignee: Shashikant Banerjee
>            Priority: Blocker
>              Labels: pull-request-available
>          Time Spent: 3h 10m
>  Remaining Estimate: 0h
> If the applyTransaction fails in the containerStateMachine, then the container should
not accept new writes on restart,.
> This can occur if
> # chunk write applyTransaction fails
> # container state update to UNHEALTHY also fails
> # Ratis snapshot is taken
> # Node restarts
> # container accepts new transactions

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org

View raw message