You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2021/10/20 20:39:11 UTC

[jira] [Updated] (HDDS-618) Separate DN registration from Heartbeat

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

Ethan Rose updated HDDS-618:
----------------------------
    Target Version/s: 1.3.0  (was: 1.2.0)

I am managing the 1.2.0 release and we currently have more than 600 issues targeted for 1.2.0. I am moving the target field to 1.3.0.

If you are actively working on this jira and believe this should be targeted for the 1.2.0 release, Please reach out to me via Apache email or Slack.

> 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.3.4#803005)

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