hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Prasanth Jayachandran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-15563) S3guard init and set-capacity to support DDB autoscaling
Date Fri, 15 Feb 2019 20:28:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-15563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16769693#comment-16769693

Prasanth Jayachandran commented on HADOOP-15563:

Does s3guard support "on-demand" mode (introduced recently) for DDB tables?

> 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
>            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

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

View raw message