[
https://issues.apache.org/jira/browse/HDDS-579?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16647940#comment-16647940
]
Jitendra Nath Pandey commented on HDDS-579:
-------------------------------------------
The patch assumes that their can be no applyTransaction in CLOSING state. It
means CLOSING state is also propagated via Ratis.
CLOSING and CLOSED state both being propagated via Ratis makes one of them
redundant. However, that is a state machine optimization to be considered in a
separate jira.
This patch marks container unhealthy only in the OPEN state, because in any
other state it will not accept applyTransaction. Therefore, the patch is
correct.
I am +1 with the patch, pending the analysis of failed unit tests.
> ContainerStateMachine should fail subsequent transactions per container in
> case one fails
> -----------------------------------------------------------------------------------------
>
> Key: HDDS-579
> URL: https://issues.apache.org/jira/browse/HDDS-579
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Reporter: Shashikant Banerjee
> Assignee: Shashikant Banerjee
> Priority: Major
> Labels: recovery
> Attachments: HDDS-579.000.patch, HDDS-579.001.patch
>
>
> ContainerStateMachine will keep of track of the last successfully applied
> transaction index and on restart inform Ratis the index, so that the
> subsequent transactions can be reapplied from here.
> Moreover, in case one transaction fails, all the subsequent transactions on
> the container should fail in the containerStateMachine and a container close
> action to SCM needs to be initiated to close the container.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
