You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Aravindan Vijayan (Jira)" <ji...@apache.org> on 2020/01/06 23:23:00 UTC
[jira] [Commented] (HDDS-2624) Configure Datanodes to push
registration request and reports to Recon.
[ https://issues.apache.org/jira/browse/HDDS-2624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17009230#comment-17009230 ]
Aravindan Vijayan commented on HDDS-2624:
-----------------------------------------
Handled as part of HDDS-2763.
> Configure Datanodes to push registration request and reports to Recon.
> ----------------------------------------------------------------------
>
> Key: HDDS-2624
> URL: https://issues.apache.org/jira/browse/HDDS-2624
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: Ozone Datanode, Ozone Recon
> Affects Versions: 0.5.0
> Reporter: Aravindan Vijayan
> Assignee: Aravindan Vijayan
> Priority: Major
>
> The first step in bringing Recon into the SCM - DN communication is to make the Recon endpoint known to Datanodes. The SCM can get the address of Recon through its config and then can pass it down to DNs in the registration response. In the DN-SCM registration response protobuf, there is an ‘SCMNodeAddressList’ field that is meant to notify the Datanode to send its reports to additional SCMs. This can be modified to a generic field like ‘AdditionalMasterAddressList’ that SCM uses to pass in the Recon address. Everytime a DN sends a report to SCM, it can also send the report to Recon. In this case, we can think of Recon as something like an Auxiliary NameNode (ANN).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org