[
https://issues.apache.org/jira/browse/HADOOP-14220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16156031#comment-16156031
]
Steve Loughran edited comment on HADOOP-14220 at 9/7/17 3:25 PM:
-----------------------------------------------------------------
bq. On that topic, is there a way to mark CLI interface as unstable?
mention it in the docs :)
you are right about the troubleshooting docs, I'll do that. But only after I've
got the doc reorg of -HADOOP-14220- in.(correction HADOOP-14738)
I'll be adding some more CLI options related to the committer next, I think
I'll want to list & drop multipart uploads under a path, maybe do some more
low-levelness.
And at some point soon we'll need to think of a "hadoop cloudstore" CLI entry
point for the stores & options related to them, such as my HADOOP-14766 util
was (Author: [email protected]):
bq. On that topic, is there a way to mark CLI interface as unstable?
mention it in the docs :)
you are right about the troubleshooting docs, I'll do that. But only after I've
got the doc reorg of HADOOP-14220 in.
I'll be adding some more CLI options related to the committer next, I think
I'll want to list & drop multipart uploads under a path, maybe do some more
low-levelness.
And at some point soon we'll need to think of a "hadoop cloudstore" CLI entry
point for the stores & options related to them, such as my HADOOP-14766 util
> Enhance S3GuardTool with bucket-info and set-capacity commands, tests
> ---------------------------------------------------------------------
>
> Key: HADOOP-14220
> URL: https://issues.apache.org/jira/browse/HADOOP-14220
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.0.0-beta1
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Attachments: HADOOP-14220-006.patch,
> HADOOP-14220-HADOOP-13345-001.patch, HADOOP-14220-HADOOP-13345-002.patch,
> HADOOP-14220-HADOOP-13345-003.patch, HADOOP-14220-HADOOP-13345-004.patch,
> HADOOP-14220-HADOOP-13345-005.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]
