[
https://issues.apache.org/jira/browse/HADOOP-15975?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-15975:
------------------------------------
Resolution: Fixed
Fix Version/s: 3.2.1
Status: Resolved (was: Patch Available)
+1
couldn't see any way to test this at all, other than having a mock store
simulate an operation taking so long the timeouts kicked in, and then verify
that with this patch that timeout didn't happen. But that would be a fairly
brittle test, i.e. it wouldn't necessarily catch regressions, maybe even have
false positives.
Taking it as is.
> ABFS: remove timeout check for DELETE and RENAME
> ------------------------------------------------
>
> Key: HADOOP-15975
> URL: https://issues.apache.org/jira/browse/HADOOP-15975
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.2.0
> Reporter: Da Zhou
> Assignee: Da Zhou
> Priority: Major
> Fix For: 3.2.1
>
> Attachments: HADOOP-15975-001.patch, HADOOP-15975-002.patch,
> HADOOP-15975-003.patch
>
>
> Currently, ABFS rename and delete is doing a timeout check, which will fail
> the request for rename/delete when the target contains tons of file/dirs.
> Because timeout check is already there for each HTTP call, we should remove
> the timeout check in RENAME and DELETE.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
