You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "Siddharth Wagle (Jira)" <ji...@apache.org> on 2020/01/16 06:14:00 UTC
[jira] [Updated] (HDDS-2869) Handle Create pipeline & container use
case in Recon
[ https://issues.apache.org/jira/browse/HDDS-2869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Wagle updated HDDS-2869:
----------------------------------
Summary: Handle Create pipeline & container use case in Recon (was: Handle Create pipeline & container use case in Recon.)
> Handle Create pipeline & container use case in Recon
> ----------------------------------------------------
>
> Key: HDDS-2869
> URL: https://issues.apache.org/jira/browse/HDDS-2869
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: Ozone Recon
> Reporter: Aravindan Vijayan
> Assignee: Aravindan Vijayan
> Priority: Major
> Fix For: 0.5.0
>
>
> CREATE pipeline needs to be handled explicitly in Recon since it is initiated in the SCM, and Recon does not know about that.
> A pipeline is created on the Datanode through an SCM command. Currently, the Datanode does not send any ACK to the SCM when it has created/deleted a container. We can add an ACK command to the Create Pipeline processing in the Datanode. The SCM will not consume the ACK command, but Recon can use it to update its internal state.
> Pipeline destroy is inferred in SCM through node staleness. Hence, recon already takes care of that through its handlers.
> Also, Recon's pipeline manager should be stubbed so that it can not create a pipeline even mistakenly.
--
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