You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2018/06/26 19:48:00 UTC

[jira] [Created] (HADOOP-15563) s3guard init and set-capacity to support DDB autoscaling

Steve Loughran created HADOOP-15563:
---------------------------------------

             Summary: s3guard init and set-capacity to support DDB autoscaling
                 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
         Environment: 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.
            Reporter: Steve Loughran






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org