Anuj Modi created HADOOP-19208:
----------------------------------
Summary: ABFS: Fixing logic to determine HNS nature of account to
avoid extra getAcl() calls
Key: HADOOP-19208
URL: https://issues.apache.org/jira/browse/HADOOP-19208
Project: Hadoop Common
Issue Type: Sub-task
Components: fs/azure
Affects Versions: 3.4.0
Reporter: Anuj Modi
Fix For: 3.5.0, 3.4.1
ABFS driver needs to know the type of account being used. It relies on the user
to inform the account type using the config `fs.azure.account.hns.enabled`.
If not configured, driver makes a getAcl call to determine the account type.
Expectation is getAcl() will fail with 400 Bad Request if made on the FNS
Account.
For any other case including 200, 404 it will indicate account is HNS.
Today, when determining this, the logic only checks status code to be either
200 or 400. In case of 404, nothing is inferred, and this leads to more getAcl
again again untill 200 or 400 comes.
Fix is to update the logic such that if getAl() fails with 400, it is FNS
account. For all other cases it will be an HNS account. In case of throttling,
if all retries are exhausted, FS init itself will fail.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
