Amazon Technologies, Inc.

Aanchal Gupta

Kiran Kumar Muniswamy Reddy

Pejus Manoj Das

Shirley Xue Yi Ly

Swaminathan Sivasubramanian

Wei Xiao

David Craig Yanacek

Khawaja Salman Shams

Yijun Lu

Johanna S Olson

Stuart Henry Seelye Marshall

Omer Ahmed Zaki

Prashant Pandey

Lokendra Singh Panwar

Johnny Ying Wu

Hendrik De Kock

A distributed data storage system may implement determining indexing progress for a table stored in the distributed data storage system. A table may be stored in multiple table partitions. When a secondary index is created for the table, each partition may independently index the items stored within the table partition in order to identify those items in the partition that should be stored in the secondary index. During creation of the secondary index, creation progress points that indicate the progress of the indexing across the table partitions may be determined. The creation progress points may be provided via a programmatic, textual, or graphical interface to the distributed data storage system.

Determining indexing progress for a table in a distributed data store

A data storage system may implement recommending throughput capacity for generating a secondary index for an online table. Secondary indexes may be created for a table stored in multiple partitions in the data storage system. The data storage system may allow users to provision throughput capacity to process access requests at secondary indexes. The throughput capacity may also be used to perform updates at the secondary index as part of generating the secondary index. A creation throughput capacity may be determined that compensates for performing the updates to generate the secondary index. A user may receive a recommendation with the creation throughput capacity for creating the secondary index and may accept or modify the creation throughput capacity. The creation throughput may be automatically provisioned to create the secondary index, in some embodiments.

Recommending provisioned throughput capacity for generating a secondary index for an online table

A data storage system may implement generating creation performance metrics for a secondary index of a table. Metrics may be collected from different partitions of a table and different partitions of a secondary index in a table store upon initiating creation of the secondary index for the table that utilize provisioned resources for creating the secondary index. The metrics may be analyzed to generate performance metrics for the creation of the table. The performance metrics may be provided to clients of the data store or to monitoring systems. Monitoring systems may send performance event notifications to clients or automatically perform modifications to the provisioned throughput capacity.

Generating creation performance metrics for a secondary index of a table

A local data store may also be configured to process updates using a common API with reference to a common schema. The common API and common schema may also be employed by hosted applications utilizing a remote distributed data store. Behavior of the remote distributed data store may be emulated by the local data store. Behaviors of the distributed data store that may be simulated include eventual consistency, provisioned throughput and latency based on horizontal partitioning.

Local emulation of distributed key-value data store

Growing community of inventors

Mountain View, CA, United States of America

Aanchal Gupta