[
https://issues.apache.org/jira/browse/HADOOP-15563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16804916#comment-16804916
]
Steve Loughran commented on HADOOP-15563:
-----------------------------------------
[~prasanth_j] HADOOP-16118 has looked at that. I've got a patch there which
covers it in the docs & makes the tests resilient to running against an
on-demand store.
changing the title and goal of this Jira from autoscale to on demand. Needs
HADOOP-16117 for an SDK update
> S3guard init and set-capacity to support on-demand DDB
> ------------------------------------------------------
>
> Key: HADOOP-15563
> URL: https://issues.apache.org/jira/browse/HADOOP-15563
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.1.0
> Reporter: Steve Loughran
> Assignee: Gabor Bota
> Priority: Major
>
> To keep costs down on DDB, autoscaling is a key feature: you set the max
> values and when idle, you don't get billed, *at the cost of delayed scale
> time and risk of not getting the max value when AWS is busy*
> It can be done from the AWS web UI, but not in the s3guard init and
> set-capacity calls
> It can be done [through the
> API|https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/AutoScaling.HowTo.SDK.html]
> Usual issues then: wiring up, CLI params, testing. It'll be hard to test.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
