[
https://issues.apache.org/jira/browse/HADOOP-18012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran resolved HADOOP-18012.
-------------------------------------
Resolution: Fixed
> ABFS: Enable config controlled ETag check for Rename idempotency
> ----------------------------------------------------------------
>
> Key: HADOOP-18012
> URL: https://issues.apache.org/jira/browse/HADOOP-18012
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.3.2
> Reporter: Sneha Vijayarajan
> Assignee: Sree Bhattacharyya
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0, 3.3.9
>
>
> To support recovery of comms failure during rename, the abfs client fetches
> the etag of the source file, and when recovering from a failure uses this tag
> to determine whether the rename succeeded *before the failure happened*
> # This works for files, but not directories
> # this adds the overhead of a HEAD request before each rename.
> # the option can be disabled by setting "fs.azure.enable.rename.resilience"
> to false
> Note: the manifest committer collects etags during task commitklkl and
> supplies them to the abfs client for the rename, which avoids the need for a
> HEAD call.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
