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

ASF GitHub Bot updated HDDS-14070:
----------------------------------
    Labels: pull-request-available  (was: )

> SCM safemode exit quickly for follower when ideal
> -------------------------------------------------
>
>                 Key: HDDS-14070
>                 URL: https://issues.apache.org/jira/browse/HDDS-14070
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: Sumit Agrawal
>            Assignee: Sumit Agrawal
>            Priority: Major
>              Labels: pull-request-available
>
> When no activity is going on at SCM, and follower SCM is restarted,
> - SCM do not exit from safe mode as it depends on 
> notifyConfigurationChanged() to exit safe mode notification.
>  
> This is for the purpose HDDS-5263  where it needs all previous raft log being 
> applied to SCM to have consistent state.
> But in ideal system, there will not be any pending transaction and it keeps 
> wait till some action happens, like,
> - leader change
> - sync of new raft log
>  
>  
>  



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to