[
https://issues.apache.org/jira/browse/HADOOP-12057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15263265#comment-15263265
]
Chen He commented on HADOOP-12057:
----------------------------------
What object store you are talking about. It is also a server side
configuration. If your server's config for the maximum size of a object is
10GB, you will not meet this problem. Try to get this info first. Or try to
copy a 1TB file to object store, see what happend. :). I just suspect that no
server will support this large single object . Please feel free to provide
feedback. Thanks!
> swiftfs rename on partitioned file attempts to consolidate partitions
> ---------------------------------------------------------------------
>
> Key: HADOOP-12057
> URL: https://issues.apache.org/jira/browse/HADOOP-12057
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/swift
> Reporter: David Dobbins
> Assignee: David Dobbins
> Attachments: HADOOP-12057-006.patch, HADOOP-12057-008.patch,
> HADOOP-12057.007.patch, HADOOP-12057.patch, HADOOP-12057.patch,
> HADOOP-12057.patch, HADOOP-12057.patch, HADOOP-12057.patch
>
>
> In the swift filesystem for openstack, a rename operation on a partitioned
> file uses the swift COPY operation, which attempts to consolidate all of the
> partitions into a single object. This causes the rename to fail when the
> total size of all the partitions exceeds the maximum object size for swift.
> Since partitioned files are primarily created to allow a file to exceed the
> maximum object size, this bug makes writing to swift extremely unreliable.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
