[jira] [Updated] (HADOOP-15210) Handle FNFE from S3Guard.getMetadataStore() in S3A initialize()
[
https://issues.apache.org/jira/browse/HADOOP-15210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vinod Kumar Vavilapalli updated HADOOP-15210:
-
Fix Version/s: (was: 3.1.0)
Removing 3.1.0 fix-version from all JIRAs which are Invalid / Won't Fix /
Duplicate / Cannot Reproduce.
> 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
>
> {{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: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
[jira] [Updated] (HADOOP-15210) Handle FNFE from S3Guard.getMetadataStore() in S3A initialize()
[
https://issues.apache.org/jira/browse/HADOOP-15210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-15210:
Parent Issue: HADOOP-14825 (was: HADOOP-15226)
> 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: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
