hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-4523) Fix concat for snapshots
Date Tue, 26 Feb 2013 01:22:14 GMT

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

Aaron T. Myers commented on HDFS-4523:
--------------------------------------

Why can't we wrap up the discussion here? I'm currently -1 on a design which makes the read-only
snapshots in fact not read-only in the case of concat.
                
> Fix concat for snapshots
> ------------------------
>
>                 Key: HDFS-4523
>                 URL: https://issues.apache.org/jira/browse/HDFS-4523
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: namenode
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Tsz Wo (Nicholas), SZE
>         Attachments: h4523_20130222.patch, h4523_20130223.patch, h4523_20130225b.patch,
h4523_20130225.patch
>
>
> The use case of concat is for copying large files across clusters using the following
steps.
> - Step 1: The blocks of a file in the source cluster are copied in parallel to transient
files in the destination cluster.
> - Step 2: Then the transient files in the destination cluster are concatenated in order
to obtain the original file.
> If a snapshot is taken in the destination cluster before Step 2, some transient files
may be captured in the snapshot.  These transient files should be removed in Step 2.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message