[
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-004.patch
Patch 004;
# Adds the set-capacity call
# Test tuning so that they handle the situation of a per-bucket config on the
s3a test bucket declaring this as s3guarded.
As a result, you can get away with running the full test suite against a real
s3guard bucket, though there are still a corner or two of the s3guard tests
which get confused. Best to split into: running s3guard tests against a
non-s3guard bucket & everything else with s3guard enabled in the bucket (and
leaving off the -Ds3guard profile) as you don't need it.
> Add S3GuardTool bucket-info 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, HADOOP-14220-HADOOP-13345-003.patch,
> HADOOP-14220-HADOOP-13345-004.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]
