[
https://issues.apache.org/jira/browse/HADOOP-14098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253589#comment-16253589
]
Steve Loughran edited comment on HADOOP-14098 at 11/16/17 3:33 PM:
-------------------------------------------------------------------
The issue with rename() is that its fundamentally not what object stores offer,
not just in performance but in failure handling
To get performance in apps which depend on it for committing work, you need to
provide an alternative for renaming when committing work. We're doing that for
s3a in HADOOP-13786, and have structured our extension point in the
MAPREDUCE-6823 patch. Accordingly: don't worry so much about rename perf.
Nice numbers.
was (Author: [email protected]):
The issue with rename() is that its fundamentally not what object stores offer,
not just in performance but in failure handling
To get performance there,
> AliyunOSS: improve the performance of object metadata operation
> ---------------------------------------------------------------
>
> Key: HADOOP-14098
> URL: https://issues.apache.org/jira/browse/HADOOP-14098
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs
> Affects Versions: 3.0.0-alpha2
> Reporter: Genmao Yu
> Assignee: Genmao Yu
>
> Open this JIRA to research and address the potential request performance
> issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
