[
https://issues.apache.org/jira/browse/HADOOP-16118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16802215#comment-16802215
]
Steve Loughran commented on HADOOP-16118:
-----------------------------------------
with the forthcoming patch, you will see an error earlier. The error message ==
that you get from the AWS service itself, to make things consistent with other
apps.
{code}
bin/hadoop s3guard set-capacity s3a://hwdev-steve-ireland-new/
2019-03-26 21:53:20,725 [main] INFO s3guard.S3GuardTool
(S3GuardTool.java:initMetadataStore(318)) - Metadata store
DynamoDBMetadataStore{region=eu-west-1, tableName=hwdev-steve-ireland-new,
tableArn=arn:aws:dynamodb:eu-west-1:980678866538:table/hwdev-steve-ireland-new}
is initialized.
java.io.IOException: Neither ReadCapacityUnits nor WriteCapacityUnits can be
specified when BillingMode is PAY_PER_REQUEST
at
org.apache.hadoop.fs.s3a.s3guard.DynamoDBMetadataStore.updateParameters(DynamoDBMetadataStore.java:1546)
at
org.apache.hadoop.fs.s3a.s3guard.S3GuardTool$SetCapacity.run(S3GuardTool.java:587)
at
org.apache.hadoop.fs.s3a.s3guard.S3GuardTool.run(S3GuardTool.java:398)
at org.apache.hadoop.util.ToolRunner.run(ToolRunner.java:76)
at
org.apache.hadoop.fs.s3a.s3guard.S3GuardTool.run(S3GuardTool.java:1628)
at
org.apache.hadoop.fs.s3a.s3guard.S3GuardTool.main(S3GuardTool.java:1637)
2019-03-26 21:53:20,825 [main] INFO util.ExitUtil
(ExitUtil.java:terminate(210)) - Exiting with status -1: java.io.IOException:
Neither ReadCapacityUnits nor WriteCapacityUnits can be specified when
BillingMode is PAY_PER_REQUEST
{code}
> S3Guard to support on-demand DDB tables
> ---------------------------------------
>
> Key: HADOOP-16118
> URL: https://issues.apache.org/jira/browse/HADOOP-16118
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: fs/s3
> Affects Versions: 3.3.0
> Reporter: Steve Loughran
> Priority: Major
>
> AWS now supports [on demand DDB
> capacity|https://aws.amazon.com/blogs/aws/amazon-dynamodb-on-demand-no-capacity-planning-and-pay-per-request-pricing/]
>
> This has lowest cost and best scalability, so could be the default capacity.
> + add a new option to set-capacity.
> Will depend on an SDK update: created HADOOP-16117.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]