[
https://issues.apache.org/jira/browse/HADOOP-18425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17701538#comment-17701538
]
ASF GitHub Bot commented on HADOOP-18425:
-----------------------------------------
sreeb-msft commented on PR #5485:
URL: https://github.com/apache/hadoop/pull/5485#issuecomment-1473280328
Hello, here is the PR relevant to
[HADOOP-18012](https://issues.apache.org/jira/browse/HADOOP-18012). The code
change is slightly different, but could similar tests be useful in this case
too? The tests mock the entire scenario of a retry happening with first 500 and
then a source not found error, and triggers an idempotency check.
https://github.com/apache/hadoop/pull/5488
> [ABFS]: RenameFilePath Source File Not Found (404) error in retry loop
> ----------------------------------------------------------------------
>
> Key: HADOOP-18425
> URL: https://issues.apache.org/jira/browse/HADOOP-18425
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs/azure
> Reporter: Sree Bhattacharyya
> Assignee: Sree Bhattacharyya
> Priority: Minor
> Labels: pull-request-available
>
> RenameFilePath on its first try receives a Request timed out error with code
> 500. On retrying the same operation, a Source file not found (404) error is
> received.
> Possible mitigation: Check whether etags remain the same before and after the
> retry and accordingly send an Operation Successful result, instead of source
> file not found.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
