Amazon Technologies, Inc.

Microsoft Technology Licensing, LLC

Other

Norbert Paul Kusters

Danny Wei

Marc John Brooker

John Luther Guthrie, Ii

Nachiappan Arumugam

Luis Felipe Cabrera

Jianhua Fan

David R Richardson

Catharine Van Ingen

Christopher Nathan Watson

Benjamin Arthur Hawks

Marc Stephen Olson

Divya Ashok Kumar Jain

Marc Levy

Rod N Gamache

Fan Ping

John Robert Smiley

Bei-Jing Guo

Mark Bradley Davis

James T Pinkerton

Robert Michael Johnson

Andrew Boyer

Thomas Tarak Mathew Veppumthara

Oleksandr Chychykalo

Sebastiano Peluso

Leah Shalev

James Michael Thompson

Brian Thomas Berkowitz

Shuvabrata Ganguly

Peter W Wieland

Shobha Agrawal

Brian D Andrew

Charles E Park

Avram Israel Blaszka

Robert Dale Rinne

Andre Podnozov

Shreyas Ramalingam

Ravi Nankani

Tate Andrew Certain

Thomas A Volpe

Anthony Nicholas Liguori

Peng T Li

Asif Khan

William J Bolosky

Mark Joseph Zbikowski

Kiran-Kumar Muniswamy-Reddy

Kerry Quintin Lee

Wells Lin

Benjamin A Leis

John Luther Guthrie

William Zaharchuk

Rahul Upadhyaya

Hon Ping Shea

Romain Benoit Seguy

Swapnil Vinay Dinkar

David Matthew Buches

Pradeep Kunni Raman

Raghav Vijay Pisolkar

Randolph B Haagens

Karan Mehra

Surendra Verma

Ran Kalach

Rajsekhar Das

James Ernest Johnson

Paul Adrian Oltean

Jonathan M Cargille

Michael T Massa

Kun Tang

Sriram Venugopal

David Golds

Tao Chen

Saar Gross

Dragos Sambotin

Glenn R Peterson

Dana D Groff

Lonny Dean McMichael

Daniel Edward Lovinger

Lakshmi N Pallikila

Kristina Kraemer Brenneman

Alexander Matushevsky

Supriya Wickrematillake

Catherine Van Ingen

Thothathri Vanamamalai

Behnam Fathi

Shyam Prasad Rajagopal

Ehab Wattad

Ii John Luther Guthrie

A data storage system includes a head node and mass storage devices. The head node is configured to flush data stored in a storage of the head node to a set of the mass storage devices of the data storage system. A head node may flush both current version data and point-in-time version data to the set of mass storage devices. Also, the data storage system maintains an index that indicates storage locations of data for particular portions of a volume before and after the data is flushed to the set of mass storage devices. In some embodiments an index includes a current version reference for a volume or portion of a volume and one or more point-in-time snapshot references.

Data system with flush views

A block-based storage system hosts logical volumes that are implemented via multiple replicas of volume data stored on multiple resource hosts in different failure domains. Also, the block-based storage service allows multiple client computing devices to attach to a same given logical volume at the same time. In order to prevent unnecessary failovers, a primary node storing a primary replica is configured with a health check application programmatic interface (API) and a secondary node storing a secondary replica determines whether or not to initiate a failover based on the health of the primary replica.

Block-storage service supporting multi-attach and health check failover mechanism

A storage service supports attachment of multiple clients to a distributed storage object and further supports persistent reservations that govern types of access the respective clients are granted with respect to the distributed storage object. In order to efficiently distribute reservation state changes to multiple partitions of the distributed storage object hosted by different data storage units/servers, existing connections are used between the data storage units/servers hosting the partitions of the distributed storage object and the connected clients to propagate reservation state changes.

Fault tolerant reservation state distribution for multi-partition logical volumes

A data storage system includes multiple head nodes and data storage sleds. Volume data is replicated between a primary and one or more secondary head nodes for a volume partition and is further flushed to a set of mass storage devices of the data storage sleds. Volume metadata is maintained in a primary and one or more secondary head nodes for a volume partition and is updated in response to volume data being flushed to the data storage sleds. Also, the primary and secondary head nodes store check-points of volume metadata to the data storage sleds, wherein in response to a failure of a primary or secondary head node for a volume partition, a replacement secondary head node for the volume partition recreates a secondary replica for the volume partition based, at least in part, on a stored volume metadata checkpoint.

Data storage system with metadata check-pointing

A data storage system includes a head node and mass storage devices. The head node is configured to store volume data and flush volume data to the mass storage devices. Additionally, the head node is configured to determine a quantity of data partitions and/or parity partitions to store for a chunk of volume data being flushed to the mass storage devices in order to satisfy a durability guarantee. For chunks of data for which complete copies are also stored in an additional data storage system, the head node is configured to reduce the quantity of data partitions and/or parity partitions stored such that required storage space is reduced while still ensuring that the durability guarantee is satisfied.

Durable data storage with snapshot storage space optimization

A data storage system includes multiple head nodes and multiple data storage sleds mounted in a rack. For a particular volume or volume partition one of the head nodes is designated as a primary head node for the volume or volume partition. The primary head node is configured to store data for the volume in a data storage of the primary head node and cause the data to be replicated to a secondary head node. The primary head node is also configured to cause the data for the volume to be stored in a plurality of respective mass storage devices each in different ones of the plurality of data storage sleds of the data storage system.

Data storage system with multiple durability levels

A data storage system includes multiple head nodes and data storage sleds. The data storage sleds include multiple mass storage devices and a sled controller. Respective ones of the head nodes are configured to obtain credentials for accessing particular portions of the mass storage devices of the data storage sleds. A sled controller of a data storage sled determines whether a head node attempting to perform a write on a mass storage device of a data storage sled that includes the sled controller is presenting with the write request a valid credential for accessing the mass storage devices of the data storage sled. If the credentials are valid, the sled controller causes the write to be performed and if the credentials are invalid, the sled controller returns a message to the head node indicating that it has been fenced off from the mass storage device.

Data storage system with enforced fencing

A data storage system includes a rack, multiple head nodes, multiple data storage sleds, and at least two networking devices. The at least two network devices are configured to implement at least two redundant networks within the data storage system. Also, each of the head nodes is assigned at least two network addresses for communication with the data storage sleds of the data storage system via the at least two networking devices. The data storage sleds each include multiple mass storage devices and a sled controller that is configured to couple with the at least two network switches. IO In some embodiments, the data storage system further includes redundant power systems within a rack in which the head nodes, the data storage sleds, and the at least two networking devices are mounted.

Data storage system with redundant internal networks

A data storage system includes multiple head nodes and data storage sleds. A control plane of the data storage system designates, for a volume partition, one of the head nodes to function as a primary head node storing a primary replica of the volume partition and designates two or more other head nodes to function as reserve head nodes storing reserve replicas of the volume partition. Additionally, the primary head node causes volume data for the volume partition to be erasure encoded and stored on multiple mass storage devices in different ones of the data storage sleds.

Data storage system

A data storage system includes multiple data storage units and a zonal control plane. The zonal control plane assigns volumes to respective ones of the data storage units. The data storage units include multiple head nodes and data storage sleds. At least one of the head nodes implements a local control plane for the data storage unit. Also, the head nodes of each data storage unit are configured to service read and write requests directed to one or more volumes serviced by the data storage unit independent of the zonal control plane.

Data storage system with multi-tier control plane

The present disclosure generally relates to creating virtualized block storage devices whose data is replicated across isolated computing systems to lower risk of data loss even in wide-scale events, such as natural disasters. The virtualized device can include at least two volumes, each of which is implemented in a distinct computing system. In the case of a failed volume, a new volume can be created and populated with data from the surviving volume. During population, new writes can continue to be replicated to the new volume. The population process can write data from the surviving volume to the new volume 'under' new writes, such that the population process does not overwrite data included in the new writes.

Failover for failed secondary in cross-zone replicated block storage devices

The present disclosure generally relates to creating virtualized block storage devices whose data is replicated across isolated computing systems to lower risk of data loss even in wide-scale events, such as natural disasters. The virtualized device can include at least two volumes, each of which is implemented in a distinct computing system. Each volume can be implemented by at least two computing devices, a first of which is configured as a primary device to which reads from and writes to the volume are directed. To ensure consistency in the distributed device, a multi-tier authority service is implemented, in which a cross-computing system authority service designates a volume as having authority to accept writes to the virtualized device, and in which a second tier authority service designates a computing device as having authority to accept writes to the volume.

Hierarchical authority store for cross-zone replicated block storage devices

A block-based storage system may implement page cache write logging. Write requests for a data volume maintained at a storage node may be received at a storage node. A page cache for may be updated in accordance with the request. A log record describing the page cache update may be stored in a page cache write log maintained in a persistent storage device. Once the write request is performed in the page cache and recorded in a log record in the page cache write log, the write request may be acknowledged. Upon recovery from a system failure where data in the page cache is lost, log records in the page cache write log may be replayed to restore to the page cache a state of the page cache prior to the system failure.

Page cache write logging at block-based storage

Growing community of inventors

Redmond, WA, United States of America

Norbert Paul Kusters