[
https://issues.apache.org/jira/browse/HDDS-13980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Agrawal resolved HDDS-13980.
----------------------------------
Fix Version/s: 2.2.0
Resolution: Fixed
> SCM start DN protocol server during startup
> -------------------------------------------
>
> Key: HDDS-13980
> URL: https://issues.apache.org/jira/browse/HDDS-13980
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Sumit Agrawal
> Assignee: Sumit Agrawal
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.2.0
>
>
> Follower SCM never comes out of safe mode, as RPC server for DN HB is not
> started at SCM. Its started if certain action like leader change happens, Or
> leader is doing some update to SCM.
>
> So, DatanodeProtocolServer can be started immediately when scm starts so that
> DN register/re-register can happen immediately
>
> Safemode exit still depends on trigger of notifyTermIndex()
>
> Changes for SCM to have quick Safemode rule exist as soon satisfied,
> 1) DatanodeProtocolServer can be started immediately when scm starts so that
> DN register/re-register can happen immediately on startup.
> 2) StateMachineReadyRule triggered by StateMachine using refreshAndvalidate()
> all rules, ensure all rules are re-checked, and exit safemode status after
> start machine has flushed / applied all raft log on startup to avoid
> in-progress raft log transaction issue as referred by
> HDDS-5263(https://issues.apache.org/jira/browse/HDDS-5263).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
