Configurable-capacity time-series tables

Patent metadata

Field	Value
Publication number	US-10459898-B2
Application number	US-201514845220-A
Country	US
Kind code	B2
Filing date	Sep 3, 2015
Priority date	Aug 7, 2013
Publication date	Oct 29, 2019
Grant date	Oct 29, 2019

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.

First claim

What is claimed is:

1. A system, comprising:
one or more computing devices configured to:
select history records that identify previously performed table management operations of a database service;
analyze the selected history records that identify previously performed table management operations of the database service;
generate, based at least on the analysis of the selected history records that identify previously performed table management operations of the database service, a schedule of table management operations to be performed on a table of the database service, wherein the schedule of table management operations comprises a first table management operation to be performed on the table in response to a future detection of a first triggering condition; and
perform the first table management operation on the table in response to the detection of the first triggering condition.

2. The system as recited in claim 1 , wherein the one or more computing devices are configured to:
collect one or more metrics corresponding to reads or writes performed at the database service;
analyze the collected one or more metrics; and
generate at least a portion of the schedule of table management operations to be performed on the table based on the analysis of the collected one or more metrics of the database service.

3. The system as recited in claim 2 , wherein the one or more computing devices are further configured to:
receiving one or more additional metrics of the database service; and
modify the schedule of table management operations based on the additional metrics.

4. The system as recited in claim 2 , wherein the one or more metrics comprises a storage device utilization level and/or a memory utilization level.

5. The system as recited in claim 2 , wherein the one or more metrics comprises a size of the table and/or a number of rows of the table.

6. The system as recited in claim 2 , wherein the one or more metrics comprises one or more of a trend in a read arrival rate, a trend in a write arrival rate, a work request arrival rate, a work request rejection rate, or latency.

7. The system as recited in claim 1 , wherein the previous table management operations comprises a table creation and/or a table deletion.

8. The system as recited in claim 1 , wherein the schedule of table management operations further comprises a second table management operation to be performed on the table in response to a detection of a second triggering condition, and the one or more computing devices are further configured to:
perform the second table management operation on the table in response to the detection of the second triggering condition.

9. A method, comprising:
performing, by one or more computing devices:
selecting history records that identify previously performed table management operations of a database service;
analyzing the selected history records that identify previously performed table management operations of the database service;
generating, based at least on the analysis of the selected history records that identify previously performed table management operations of the database service, a schedule of table management operations to be performed on a table of the database service, wherein the schedule of table management operations comprises at least one table management operation to be performed on the table in response to a future detection of a triggering condition; and
performing the at least one table management operation on the table in response to the detection of the first triggering condition.

10. The method as recited in claim 9 , wherein at least a portion of the schedule of table management operations is generated based on analysis of one or more collected metrics corresponding to reads or writes performed at the database service.

11. The method as recited in claim 10 , wherein the one or more metrics comprises a value of content of the table.

12. The method as recited in claim 10 , wherein at least a portion of the schedule of table management operations is generated based on a trend in a read arrival rate, a trend in a write arrival rate, a work request arrival rate, a work request rejection rate, or latency.

13. The method as recited in claim 9 , wherein the previously performed table management operations identified by the selected history records comprise at least one of table creation, table deletion, change in table throughput, change in a table configuration setting, splitting a table, an alert indicating a throughput threshold for a table is reached or exceeded, an alert indicating new partitions were added to a table, or an alert indicating one or more replicas of a table partition became unavailable or inaccessible.

14. The method as recited in claim 9 , wherein the schedule of table management operations comprises at least one of: (a) an operation to merge the table with another table, (b) an operation to backup contents of the table, (c) an operation to configure the table as a read-only table, (d) an operation to export contents of the table in accordance with a specified format, (e) an operation to archive contents of the table, (f) an operation to delete the table, (g) an operation to split the table into a plurality of tables, (h) an operation to send a notification associated with the table, (i) an operation to perform a specified type of computation on at least a subset of the contents of the table, (j) an operation to delete a portion of the table based on specified deletion criteria, or (k) an index-management operation on the table.

15. A non-transitory computer-accessible storage medium storing program instructions that when executed on one or more processors:
select history records that identify previously performed table management operations of a database service;
analyze the selected history records that identify previously performed table management operations of the database service;
generate, based at least on the analysis of the selected history records that identify previously performed table management operations of the database service, a schedule of table management operations to be performed on a table of the database service, wherein the schedule of table management operations comprises at least one table management operation to be performed on the table in response to a future detection of a triggering condition; and
perform the at least one table management operation on the table in response to the detection of the triggering condition.

16. The non-transitory computer-accessible storage medium as recited in claim 15 , wherein the instructions when executed on the one or more processors:
receive one or more metrics from the database over a time period, wherein the one or more metrics correspond to reads or writes performed at the database service;
analyze the received one or more metrics; and
generate at least a portion of the schedule of table management operations based at least in part on the analysis of the one or more metrics.

17. The non-transitory computer-accessible storage medium as recited in claim 16 , wherein the one or more metrics comprises properties of the table.

18. The non-transitory computer-accessible storage medium as recited in claim 15 , wherein the triggering condition comprises an expiration of a time interval.

19. The non-transitory computer-accessible storage medium as recited in claim 15 , wherein the schedule is based at least in part on one or more parameters indicated in a request.

20. The non-transitory computer-a

Assignees

• Amazon Tech Inc

Inventors

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

Classifications

• G06F16/213 Primary

  with details for schema evolution support · CPC title

• G06F16/2282

  Tablespace storage structures; Management thereof · CPC title

• G06F16/955

  using information identifiers, e.g. uniform resource locators [URL] · CPC title

• G06F16/211

  Schema design and management · CPC title