[
https://issues.apache.org/jira/browse/HADOOP-17002?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17087863#comment-17087863
]
Bilahari T H commented on HADOOP-17002:
---------------------------------------
*Driver test results using accounts in Central India*
mvn -T 1C -Dparallel-tests=abfs -Dscale -DtestsThreadCount=8 clean verify
*Account with HNS Support*
[INFO] Tests run: 52, Failures: 0, Errors: 0, Skipped: 0
[WARNING] Tests run: 424, Failures: 0, Errors: 0, Skipped: 66
[WARNING] Tests run: 206, Failures: 0, Errors: 0, Skipped: 24
*Account without HNS support*
[INFO] Tests run: 52, Failures: 0, Errors: 0, Skipped: 0
[WARNING] Tests run: 424, Failures: 0, Errors: 0, Skipped: 240
[WARNING] Tests run: 206, Failures: 0, Errors: 0, Skipped: 24
> ABFS: Avoid storage calls to check if the account is HNS enabled or not
> -----------------------------------------------------------------------
>
> Key: HADOOP-17002
> URL: https://issues.apache.org/jira/browse/HADOOP-17002
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/azure
> Affects Versions: 3.4.0
> Reporter: Bilahari T H
> Assignee: Bilahari T H
> Priority: Minor
> Fix For: 3.4.0
>
>
> Each time an FS instance is created a Getacl call is made. If the call fails
> with 400 Bad request, the account is determined to be a non-HNS account.
> Recommendation is to create a config and be able to avoid store calls to
> determine account HNS status,
> If config is available, use that to determine account HNS status. If config
> is not present in core-site, default behaviour will be calling getAcl.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
