[
https://issues.apache.org/jira/browse/HDDS-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nandakumar resolved HDDS-618.
-----------------------------
Resolution: Won't Do
SCM doesn't maintain the list of datanodes that needs to be registered. So,
it's not possible for the SCM to identify/detect if a datanode should register
or not, unless the datanode heartbeats.
Adding this logic will bring in additional complexities (like initiating
connection from SCM to datanode, which we don't do right now) which is
unnecessary.
Until now we haven't seen any scenario where this feature was required.
We can revisit this later, if required.
> Separate DN registration from Heartbeat
> ---------------------------------------
>
> Key: HDDS-618
> URL: https://issues.apache.org/jira/browse/HDDS-618
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Hanisha Koneru
> Priority: Major
>
> Currently, if SCM has to send ReRegister command to a DN, it can only do so
> through heartbeat response. Due to this, DN reregistration can take upto 2
> heartbeat intervals.
> We should decouple registration requests from heartbeat, so that DN can
> reregister as soon as SCM detects that the node is not registered.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
