You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Steve Loughran (Jira)" <ji...@apache.org> on 2023/05/03 13:18:00 UTC

[jira] [Created] (HADOOP-18728) ABFS handles nonexistent/non-auth accounts badly

Steve Loughran created HADOOP-18728:
---------------------------------------

             Summary: ABFS handles nonexistent/non-auth accounts badly
                 Key: HADOOP-18728
                 URL: https://issues.apache.org/jira/browse/HADOOP-18728
             Project: Hadoop Common
          Issue Type: Bug
          Components: fs/azure
    Affects Versions: 3.3.5
            Reporter: Steve Loughran


Testing storediag with a nonexistent account/bucket raises interesting failures modes

# DNS failures are retried, rather than fail fast
# a container which exists but you can't access fails with the wrong exception


{code}
org.apache.hadoop.fs.FileAlreadyExistsException: Operation failed: "This endpoint does not support BlobStorageEvents or SoftDelete. Please disable these account features if you would like to use this endpoint.", 409, HEAD, https://somewhere.dfs.core.windows

{code}


Proposed
# failfast on host not found, escalate to an account not found
# recognise and translate that does not support BlobStorageEvents 

side issue: is that failure leaking secrets about another a/c? or is it always raised if not authed




--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org