[
https://issues.apache.org/jira/browse/HADOOP-14220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-14220:
------------------------------------
Attachment: HADOOP-14220-HADOOP-13345-002.patch
HADOOP-14220
* new s3guad CLI command bucket-info
* change how all S3GuardTools fail: they now through an ExitUtils.ExitException
with a status code (from the LauncherExitCodes list). Its easier to bail out
and tests can get the full stack trace on any failure instead of some "return
code wrong check the logs" kind of report
* unit test for invalid args to the CLI
* test for some more invalid states of existing ops
* some new tests for bucket-info, though not enough (need some on DDB + bucket)
* address various other s3guard tool issues discussed elsewhere
This is a big enough change that it's not stable yet, it'll be targeting
post-merge s3guard.
> Add S3GuardTool diagnostics command
> -----------------------------------
>
> Key: HADOOP-14220
> URL: https://issues.apache.org/jira/browse/HADOOP-14220
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: HADOOP-13345
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Attachments: HADOOP-14220-HADOOP-13345-001.patch,
> HADOOP-14220-HADOOP-13345-002.patch
>
>
> Add a diagnostics command to s3guard which does whatever we need to diagnose
> problems for a specific (named) s3a url. This is something which can be
> attached to bug reports as well as used by developers.
> * Properties to log (with provenance attribute, which can track bucket
> overrides: s3guard metastore setup, autocreate, capacity,....
> * table present/absent
> * # of keys in DDB table for that bucket?
> * any other stats?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
