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

Posted to hdfs-issues@hadoop.apache.org by "Lokesh Jain (JIRA)" <ji...@apache.org> on 2018/11/13 05:25:00 UTC

[jira] [Resolved] (HDDS-735) Remove ALLOCATED and CREATING state from ContainerStateManager

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

Lokesh Jain resolved HDDS-735.
------------------------------
    Resolution: Duplicate

This issue has been fixed via HDDS-733.

> Remove ALLOCATED and CREATING state from ContainerStateManager
> --------------------------------------------------------------
>
>                 Key: HDDS-735
>                 URL: https://issues.apache.org/jira/browse/HDDS-735
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: SCM
>            Reporter: Nanda kumar
>            Assignee: Lokesh Jain
>            Priority: Major
>
> After HDDS-733 and HDDS-734, we don't need ALLOCATED and CREATING state for containers in SCM. The container will move to OPEN state as soon as it is allocated in SCM. Since the container creation happens as part of the first chunk write and container creation operation in datanode idempotent we don't have to worry about giving out the same container to multiple clients as soon as it is allocated.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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