hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mingliang Liu (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-14345) S3Guard: S3GuardTool to support provisioning metadata store
Date Wed, 26 Apr 2017 20:11:04 GMT

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

Mingliang Liu commented on HADOOP-14345:
----------------------------------------

The `init` subcommand is performing the one-time initialization of metadata store, honoring
the read/write capacity settings (which is good). If the DDB table is there and active, the
`init` will be a no-op, that is it will not change the existing table's read/write capacity.
I'm fine with the existing behavior. Here I'm thinking of provisioning existing tables. Users
may need this according to the DDB table usage, as high read/write capacity wastes money if
load is lower while lower read/write capacity gets request throttled.

> S3Guard: S3GuardTool to support provisioning metadata store
> -----------------------------------------------------------
>
>                 Key: HADOOP-14345
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14345
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: fs/s3
>            Reporter: Mingliang Liu
>            Priority: Minor
>
> I don't know if this is considered a requested feature from S3Guard code, as the user
can always provision the DDB tables via the cloud portal.
> Implementing should be straightforward. The {{DynamoDBMetadataStore}} has provision method
to use.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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


Mime
View raw message