You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2017/08/29 10:40:00 UTC
[jira] [Commented] (HADOOP-14109) improvements to S3GuardTool
destroy command
[ https://issues.apache.org/jira/browse/HADOOP-14109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16145090#comment-16145090 ]
Steve Loughran commented on HADOOP-14109:
-----------------------------------------
# destroy must clear demand-create table flag.
# if the version marker is missing/inconsistent, it may be due to some configuration problem & the client is connected to something which isn't a s3guard table. Safest to say "use the AWS console here"
> improvements to S3GuardTool destroy command
> -------------------------------------------
>
> Key: HADOOP-14109
> URL: https://issues.apache.org/jira/browse/HADOOP-14109
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: HADOOP-13345
> Reporter: Steve Loughran
> Priority: Minor
>
> The S3GuardTool destroy operation initializes dynamoDB, and in doing so has some issues
> # if the version of the table is incompatible, init fails, so table isn't deleteable
> # if the system is configured to create the table on demand, then whenever destroy is called for a table that doesn't exist, it gets created and then destroyed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org