公开(公告)号：US20140279929A1

公开(公告)日：2014-09-18

申请号：US14201493

申请日：2014-03-07

Applicant: Amazon Technologies, Inc.

Inventor： ANURAG WINDLASS GUPTA ,  NEAL FACHAN ,  SAMUEL JAMES MCKELVIE ,  LAURION DARRELL BURCHALL ,  CHRISTOPHER RICHARD NEWCOMBE ,  PRADEEP JNANA MADHAVARAPU ,  BENJAMIN TOBLER ,  JAMES MCCLELLAN COREY

IPC: G06F11/14

CPC classification number: G06F17/30371 ,  G06F11/1451 ,  G06F11/1471 ,  G06F11/2094 ,  G06F17/30345 ,  G06F2201/80

Abstract: A database system may include a database service and a separate distributed storage service. The database service (or a database engine head node thereof) may be responsible for query parsing, optimization, and execution, transactionality, and consistency, while the storage service may be responsible for generating data pages from redo log records and for durability of those data pages. For example, in response to a write request directed to a particular data page, the database engine head node may generate a redo log record and send it, but not the data page, to a storage service node. The storage service node may store the redo log record and return a write acknowledgement to the database service prior to applying the redo log record. The server node may apply the redo log record and other redo log records to a previously stored version of the data page to create a current version.

Abstract translation: 数据库系统可以包括数据库服务和单独的分布式存储服务。 数据库服务（或其数据库引擎头节点）可以负责查询解析，优化和执行，事务性和一致性，而存储服务可能负责从重做日志记录生成数据页面以及对这些数据的耐久性 页面。 例如，响应于针对特定数据页的写请求，数据库引擎头节点可以生成重做日志记录，并将其发送到存储服务节点，而不是数据页。 存储服务节点可以存储重做日志记录，并在应用重做日志记录之前向数据库服务返回写入确认。 服务器节点可以将重做日志记录和其他重做日志记录应用于先前存储的数据页面版本，以创建当前版本。

公开(公告)号：US20170083565A1

公开(公告)日：2017-03-23

申请号：US15369681

申请日：2016-12-05

Applicant: Amazon Technologies, Inc.

Inventor： ANURAG WINDLASS GUPTA ,  NEAL FACHAN ,  SAMUEL JAMES MCKELVIE ,  LAURION DARRELL BURCHALL ,  CHRISTOPHER RICHARD NEWCOMBE ,  PRADEEP JNANA MADHAVARAPU ,  BENJAMIN TOBLER ,  JAMES MCCLELLAN COREY

IPC: G06F17/30 ,  G06F11/14

Abstract: A database system may include a database service and a separate distributed storage service. The database service (or a database engine head node thereof) may be responsible for query parsing, optimization, and execution, transactionality, and consistency, while the storage service may be responsible for generating data pages from redo log records and for durability of those data pages. For example, in response to a write request directed to a particular data page, the database engine head node may generate a redo log record and send it, but not the data page, to a storage service node. The storage service node may store the redo log record and return a write acknowledgement to the database service prior to applying the redo log record. The server node may apply the redo log record and other redo log records to a previously stored version of the data page to create a current version.

公开(公告)号：US20140337393A1

公开(公告)日：2014-11-13

申请号：US13893004

申请日：2013-05-13

Applicant: Amazon Technologies, Inc.

Inventor： LAURION DARRELL BURCHALL ,  PRADEEP JNANA MADHAVARAPU ,  CHRISTOPHER RICHARD NEWCOMBE ,  ANURAG WINDLASS GUPTA

IPC: G06F17/30

CPC classification number: G06F17/30377 ,  G06F9/466 ,  G06F17/30351 ,  G06F17/30359 ,  G06F17/30371

Abstract: Nodes of a database service may receive a read request to perform a read of a record stored by the database service and a transaction request to perform a transaction to the record. First and second indications of time may be associated with the read and transaction, respectively. A potential read anomaly (e.g., fuzzy read, read skew, etc.) may be detected based, at least in part, on a determination that the first indication of time is within a threshold value of the second indication of time. In response to detecting the potential read anomaly, the read may be performed after the transaction specified by the transaction request, regardless of whether the first indication of time is indicative of an earlier point in time than the second indication of time.

Abstract translation: 数据库服务的节点可以接收读请求，以执行由数据库服务存储的记录的读取和用于对记录执行事务的事务请求。 时间的第一和第二指示可能分别与读取和交易相关联。 至少部分地可以基于时间的第一指示在第二时间指示的阈值内的确定来检测潜在的读取异常（例如，模糊读取，读取偏移等）。 响应于检测到潜在的读取异常，可以在由事务请求指定的事务之后执行读取，而不管时间的第一指示是否指示比第二时间指示更早的时间点。