You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Attila Doroszlai (Jira)" <ji...@apache.org> on 2024/01/29 07:13:00 UTC

[jira] [Resolved] (HDDS-9823) Pipeline failure should trigger heartbeat immediately

     [ https://issues.apache.org/jira/browse/HDDS-9823?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Attila Doroszlai resolved HDDS-9823.
------------------------------------
    Fix Version/s: 1.5.0
       Resolution: Implemented

> Pipeline failure should trigger heartbeat immediately
> -----------------------------------------------------
>
>                 Key: HDDS-9823
>                 URL: https://issues.apache.org/jira/browse/HDDS-9823
>             Project: Apache Ozone
>          Issue Type: Improvement
>          Components: Ozone Datanode, SCM
>            Reporter: Ivan Andika
>            Assignee: Ivan Andika
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.5.0
>
>
> XceiverServerRatis#handlePipelineFailure is called in CSM failure scenarios
>  * XceiverServerRatis#handleNodeSlowness
>  ** From StateMachine#notifyFollowerSlowness 
>  ** Set to hdds.ratis.rpc.slowness.timeout (default value 300s)
>  *** Note: Ratis default value is 60s
>  * XceiverServerRatis#handleNoLeader
>  ** From StateMachine#notifyExtendedNoLeader
>  ** Set to hdds.ratis.notification.no-leader.timeout (default value 300s)
>  *** Note: Ratis default value is 60s
>  * XceiverServerRatis#handleInstallSnapshotFromLeader
>  ** From StateMachine#notifyInstallSnapshotFromLeader
> Currently, XceiverServerRatis#handlePipelineFailure does not trigger Heartbeat to SCM immediately. Instead, it waits until the next heartbeat (default 60s) to send the pipeline close action command. This might cause SCM to still allocate blocks to these "failed" pipelines during this duration which might impact on client writing to these blocks.
> To minimize the impact on the client and the datanodes on the failed pipeline. I suggest that the datanode trigger the pipeline close command immediately for every pipeline action close command triggered due to pipeline failure.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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