hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lokesh Jain (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDDS-733) Create container if not exist, as part of chunk write
Date Thu, 01 Nov 2018 14:42:00 GMT

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

Lokesh Jain updated HDDS-733:
-----------------------------
    Description: 
The current implementation requires a container to be created in datanode before starting
the chunk write. This can be optimized by creating the container on the first chunk write.
 During chunk write, if the container is missing, we can go ahead and create the container.

Along with this change ALLOCATED and CREATING container states can be removed as they were
used to track which containers have been successfully created. Also there is a shouldCreateContainer
flag which is used by client to know if it needs to create container. This flag can be removed.

  was:
The current implementation requires a container to be created in datanode before starting
the chunk write. This can be optimized by creating the container on the first chunk write.
During chunk write, if the container is missing, we can go ahead and create the container.


> Create container if not exist, as part of chunk write
> -----------------------------------------------------
>
>                 Key: HDDS-733
>                 URL: https://issues.apache.org/jira/browse/HDDS-733
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: Ozone Datanode
>            Reporter: Nanda kumar
>            Assignee: Lokesh Jain
>            Priority: Major
>         Attachments: HDDS-733.001.patch, HDDS-733.002.patch
>
>
> The current implementation requires a container to be created in datanode before starting
the chunk write. This can be optimized by creating the container on the first chunk write.
>  During chunk write, if the container is missing, we can go ahead and create the container.
> Along with this change ALLOCATED and CREATING container states can be removed as they
were used to track which containers have been successfully created. Also there is a shouldCreateContainer
flag which is used by client to know if it needs to create container. This flag can be removed.



--
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


Mime
View raw message