You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/11/24 17:40:00 UTC
[jira] [Resolved] (HADOOP-14714) handle InternalError in bulk
object delete through retries
[ https://issues.apache.org/jira/browse/HADOOP-14714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steve Loughran resolved HADOOP-14714.
-------------------------------------
Resolution: Fixed
Fix Version/s: 3.1.0
Done in HADOOP-13786: we *do* consider delete to be idempotent. This fact is declared in a boolean constant DELETE_CONSIDERED_IDEMPOTENT, so if it were to be changed (or made a config option), it would be straightforward
> handle InternalError in bulk object delete through retries
> ----------------------------------------------------------
>
> Key: HADOOP-14714
> URL: https://issues.apache.org/jira/browse/HADOOP-14714
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 2.8.0
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Fix For: 3.1.0
>
>
> There's some more detail appearing on HADOOP-11572 about the errors seen here; sounds like its large fileset related (or just probability working against you). Most importantly: retries may make it go away.
> Proposed: implement a retry policy.
> Issue: delete is not idempotent, not if someone else adds things.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org