公开(公告)号：US09372911B2

公开(公告)日：2016-06-21

申请号：US14281508

申请日：2014-05-19

Applicant: Amazon Technologies, Inc.

Inventor： Stefano Stefani ,  Timothy Andrew Rath ,  Jakub Kulesza ,  Wei Xiao

IPC: G06F11/00 ,  G06F17/30 ,  G06F11/14 ,  G06F11/20

CPC classification number: G06F17/30584 ,  G06F11/1471 ,  G06F11/2023 ,  G06F11/2094

Abstract: A system that implements a data storage service may maintain tables in a data store on behalf of clients. The service may maintain table data in multiple replicas of partitions of the data that are stored on respective computing nodes in the system. In response to detecting a failure or fault condition, or receiving a service request from a client to move or copy a partition replica, the data store may copy a partition replica to another computing node using a physical copy mechanism. The physical copy mechanism may copy table data from physical storage locations in which it is stored to physical storage locations allocated to a destination replica on the other computing node. During copying, service requests to modify table data may be logged and applied to the replica being copied. A catch-up operation may be performed to apply modification requests received during copying to the destination replica.

Abstract translation: 实现数据存储服务的系统可以代表客户端在数据存储中维护表。 该服务可以在存储在系统中的相应计算节点上的数据的分区的多个副本中维护表数据。 响应于检测到故障或故障状况，或者从客户端接收到移动或复制分区副本的服务请求，数据存储可以使用物理复制机制将分区副本复制到另一个计算节点。 物理复制机制可以将表数据从其存储的物理存储位置复制到分配给另一个计算节点上的目标副本的物理存储位置。 在复制期间，可能会记录修改表数据的服务请求并将其应用于复制副本。 可以执行追赶操作以将复制期间接收的修改请求应用于目的地复本。

公开(公告)号：US09128965B1

公开(公告)日：2015-09-08

申请号：US13961778

申请日：2013-08-07

Applicant: Amazon Technologies, Inc.

Inventor： David Craig Yanacek ,  Mohammad Zeeshan Qureshi ,  Jai Vasanth ,  Pejus Manoj Das ,  Stefano Stefani ,  Stuart Henry Seelye Marshall ,  Wei Xiao

IPC: G06F17/30

CPC classification number: G06F17/30297 ,  G06F17/30292 ,  G06F17/30339 ,  G06F17/30876

Abstract: Methods and apparatus for configurable-capacity time-series tables are disclosed. A schedule of database table management operations, including at least an operation to change a throughput constraint associated with a table in response to a triggering event, is generated. The table is instantiated with an initial throughput constraint in accordance with the schedule. Work requests directed to the table are accepted based on the initial throughput constraint. The throughput constraint is modified in response to the triggering event. Subsequent work requests are accepted based on the modified throughput constraint.

Abstract translation: 公开了可配置容量时间序列表的方法和装置。 生成数据库表管理操作的调度表，其包括响应于触发事件而至少改变与表关联的吞吐量约束的操作。 该表根据时间表以初始吞吐量约束进行实例化。 基于初始吞吐量约束接受指向表的工作请求。 响应于触发事件修改吞吐量约束。 基于修改的吞吐量约束接受后续工作请求。

公开(公告)号：US09053167B1

公开(公告)日：2015-06-09

申请号：US13922001

申请日：2013-06-19

Applicant: Amazon Technologies, Inc.

Inventor： Bjorn Patrick Swift ,  Wei Xiao ,  Stuart Henry Seelye Marshall ,  Stefano Stefani ,  Timothy Andrew Rath ,  David Alan Lutz

IPC: G06F17/00 ,  G06F17/30

CPC classification number: G06F17/30584 ,  G06F17/30575

Abstract: A system that implements a data storage service may store data in multiple replicated partitions on respective storage nodes. The selection of the storage nodes (or storage devices thereof) on which to store the partition replicas may be performed by administrative components that are responsible for partition management and resource allocation for respective groups of storage nodes (e.g., based on a global view of resource capacity or usage), or the selection of particular storage devices of a storage node may be determined by the storage node itself (e.g., based on a local view of resource capacity or usage). Placement policies applied at the administrative layer or storage layer may be based on the percentage or amount of provisioned, reserved, or available storage or IOPS capacity on each storage device, and particular placements (or subsequent operations to move partition replicas) may result in an overall resource utilization that is well balanced.

Abstract translation: 实现数据存储服务的系统可以将数据存储在相应存储节点上的多个复制分区中。 存储分区副本的存储节点（或其存储设备）的选择可以由负责相应组的存储节点的分区管理和资源分配的管理组件执行（例如，基于资源的全局视图 容量或使用），或存储节点的特定存储设备的选择可以由存储节点本身（例如，基于资源容量或用途的本地视图）来确定。 在管理层或存储层应用的布局策略可以基于每个存储设备上的配置，保留或可用存储或IOPS容量的百分比或数量，以及特定展示位置（或后续的移动分区副本的操作）可能会导致 整体资源利用情况良好。