[ 
https://issues.apache.org/jira/browse/HDDS-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814957#comment-16814957
 ] 

Hudson commented on HDDS-1417:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16380 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/16380/])
HDDS-1417. After successfully importing a container, datanode should (bharat: 
rev e9c4109004ca378806f167ed580b57fd0d191fd4)
* (edit) 
hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/replication/DownloadAndImportReplicator.java


> After successfully importing a container, datanode should delete the 
> container tar.gz file from working directory
> -----------------------------------------------------------------------------------------------------------------
>
>                 Key: HDDS-1417
>                 URL: https://issues.apache.org/jira/browse/HDDS-1417
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>          Components: Ozone Datanode
>    Affects Versions: 0.3.0
>            Reporter: Sandeep Nemuri
>            Assignee: Nanda kumar
>            Priority: Blocker
>              Labels: pull-request-available
>             Fix For: 0.4.0, 0.5.0
>
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> Whenever we want to replicate or copy a container from one datanode to 
> another, we compress the container data and create a tar.gz file. This tar 
> file is then copied from source datanode to destination datanode. In 
> destination, we use a temporary working directory where this tar file is 
> copied. Once the copying is complete we import the container. After importing 
> the container we no longer need the tar file in the working directory of 
> destination datanode, this has to be deleted.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to