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 "Thomas Marqardt (Jira)" <ji...@apache.org> on 2020/07/25 13:54:00 UTC
[jira] [Updated] (HADOOP-17015) ABFS: Make PUT and POST operations
idempotent
[ https://issues.apache.org/jira/browse/HADOOP-17015?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Marqardt updated HADOOP-17015:
-------------------------------------
Fix Version/s: 3.3.1
eed06b4 branch-3.3@\{2020-07-25 13:08:01 +0000}: cherry-pick: Hadoop-17015. ABFS: Handling Rename and Delete idempotency
> ABFS: Make PUT and POST operations idempotent
> ---------------------------------------------
>
> Key: HADOOP-17015
> URL: https://issues.apache.org/jira/browse/HADOOP-17015
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.2.1
> Reporter: Sneha Vijayarajan
> Assignee: Sneha Vijayarajan
> Priority: Major
> Fix For: 3.3.1, 3.4.0
>
>
> Currently when a PUT or POST operation timeouts and the server has already successfully executed the operation, there is no check in driver to see if the operation did succeed or not and just retries the same operation again. This can cause driver to through invalid user errors.
>
> Sample scenario:
> # Rename request times out. Though server has successfully executed the operation.
> # Driver retries rename and get source not found error.
> In the scenario, driver needs to check if rename is being retried and success if source if not found, but destination is present.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org