You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ratis.apache.org by "Supratim Deka (JIRA)" <ji...@apache.org> on 2019/08/06 11:12:00 UTC
[jira] [Resolved] (RATIS-644) Handle failures encountered in
applyLog
[ https://issues.apache.org/jira/browse/RATIS-644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Supratim Deka resolved RATIS-644.
---------------------------------
Resolution: Not A Problem
HDDS-1610 takes care of Ozone, closing the pipeline on applyLog failure, new transactions for the Unhealthy Container get failed anyway. So, the behaviour suggested in this Jira is not required for the Datanode. And as pointed out by [~bharatviswa] would not have been acceptable for the OM.
Closing this Jira.
> Handle failures encountered in applyLog
> ---------------------------------------
>
> Key: RATIS-644
> URL: https://issues.apache.org/jira/browse/RATIS-644
> Project: Ratis
> Issue Type: Bug
> Components: server
> Reporter: Supratim Deka
> Assignee: Supratim Deka
> Priority: Major
>
> This is related to HDDS-1739 which detects and reports IO failures during applyTransaction.
> Currently, the StateMachineUpdater in response to a failed applyLog/applyTransaction operation triggers a shutdown of the Ratis server.
> Instead, the desired behaviour is to stop accepting new append requests on the group. For the case of Ozone, the state machine will initiate destruction/closing of the Ratis group - this is implemented as a part of HDDS-1739.
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)