[
https://issues.apache.org/jira/browse/HADOOP-15210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16370030#comment-16370030
]
Steve Loughran commented on HADOOP-15210:
-----------------------------------------
In auth mode, we absolutely must have the connection. In non-auth mode, well,
you could imagine downgrading. But there is that risk that you have 1+ client
in non-auth mode writing to the tables, and 1+ client running in auth-mode,
expecting all clients.
Overall, I think you are right. Closing as a WONTFIX
> Handle FNFE from S3Guard.getMetadataStore() in S3A initialize()
> ---------------------------------------------------------------
>
> Key: HADOOP-15210
> URL: https://issues.apache.org/jira/browse/HADOOP-15210
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.0.0
> Reporter: Steve Loughran
> Priority: Minor
> Fix For: 3.1.0
>
>
> {{S3Guard.getMetadataStore()}} throws FileNotFoundExceptions up, as the
> comments say " rely on callers to catch and treat specially"
> S3A Filesystem doesn't do that, instead it will just fail
> FileSystem.initialize; the FNFE is generated by DynamoDBMetadataStore.
> Are we happy with this?
> Downgrading has some appeal: if you don't have the table, it will keep going.
> But failures could be a sign of bad config, so maybe silent recovery is bad.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
