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/07 18:48:00 UTC
[jira] [Created] (HDDS-2850) Handle Create/Delete container use
case in Recon.
Aravindan Vijayan created HDDS-2850:
---------------------------------------
Summary: Handle Create/Delete container use case in Recon.
Key: HDDS-2850
URL: https://issues.apache.org/jira/browse/HDDS-2850
Project: Hadoop Distributed Data Store
Issue Type: Bug
Components: Ozone Recon
Reporter: Aravindan Vijayan
Assignee: Aravindan Vijayan
CREATE/DELETE container needs to be handled differently in Recon since these actions are initiated in the SCM, and Recon does not know about that.
It may suddenly see a new container and should not throw ContainerNotFoundException for that.
A container is created in the Datanode through an SCM command, and is deleted in the Datanode when the SCM Replication Manager finds that it is over replicated. 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/Delete Container processing in the Datanode. The SCM will not consume the ACK command, but Recon can use it to update its internal container state.
--
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