[
https://issues.apache.org/jira/browse/HADOOP-17215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17947145#comment-17947145
]
Mukund Thakur commented on HADOOP-17215:
----------------------------------------
Thanks [~bhattmanish98] Could you please give an example case which can lead
to data loss? A consecutive retry will still override the same data unless
application is doing something wrong.
I have asked the customer about the use and why there are so many parallel
create requests. i will let you know once they respond.
> ABFS: Support for conditional overwrite
> ---------------------------------------
>
> Key: HADOOP-17215
> URL: https://issues.apache.org/jira/browse/HADOOP-17215
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.3.0
> Reporter: Sneha Vijayarajan
> Assignee: Sneha Vijayarajan
> Priority: Major
> Labels: abfsactive
> Fix For: 3.3.1, 3.4.0
>
>
> Filesystem Create APIs that do not accept an argument for overwrite flag end
> up defaulting it to true.
> We are observing that request count of creates with overwrite=true is more
> and primarily because of the default setting of the flag is true of the
> called Create API. When a create with overwrite ends up timing out, we have
> observed that it could lead to race conditions between the first create and
> retried one running almost parallel.
> To avoid this scenario for create with overwrite=true request, ABFS driver
> will always attempt to create without overwrite. If the create fails due to
> fileAlreadyPresent, it will resend the request with overwrite=true.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
