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

Stephen O'Donnell updated HDDS-13618:
-------------------------------------
    Fix Version/s: 2.1.0
       Resolution: Fixed
           Status: Resolved  (was: Patch Available)

> Avoid frequent pipeline close action from DN
> --------------------------------------------
>
>                 Key: HDDS-13618
>                 URL: https://issues.apache.org/jira/browse/HDDS-13618
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: Sumit Agrawal
>            Assignee: Sarveksha Yeshavantha Raju
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 2.1.0
>
>
> When DN ratis identify issues over pipeline, it trigger close pipeline 
> action, below are few cases:
>  # When follower is slow
>  # When leader is not elected and remain in candidate for longer duration
>  # Any other issue in pipeline like disk out of space trigger failure
> This keeps triggering close pipeline action, even though close actions are 
> queued in DN command queue. And if there is any issue for DN pipeline 
> closure, it can result in huge such action every HB.
>  
> Already there is an optimization that within one HB, it will avoid duplicate 
> pipeline close action.
>  
> So this repeatative trigger can be avoided by checking the command queue.



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

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

Reply via email to