Abstract: Technologies are provided for storing data in a storage device based on an associated attribute or attributes. A storage device can be configured to write data to a storage location of the storage device based on an associated attribute. The attribute can describe one or more storage-related requirements of the data. The storage device can identify one or more storage locations where the data can be stored that meet the storage-related requirements described by the attribute. A host computer can transmit an updated attribute for the data to the storage device to reflect new storage-related requirements for the data. The storage device can write the data to a new storage location that meets the new requirements. A mapping table can be maintained that associates a logical identifier for the data with the actual storage location where the data is stored.

Abstract: Technologies are provided for a storage device data move command. A storage device can be configured to receive a data move (or garbage collection) command and, responsive to receiving the command, move data from one zone of the storage device (or range of storage locations within the storage device) to another zone (or another range of storage locations) within the storage device. The command can comprise a source zone identifier and a target zone identifier. The storage device can read data from a storage zone associated with the source zone identifier and write the data to another storage zone associated with the target zone identifier. The identifiers can include ranges of storage location addresses within the separate storage zones. In at least some embodiments, a host bus adapter can be configured to support the data move (or garbage collection) command for a storage device attached to the host bus adapter.

Abstract: Technologies are provided for storing data in a storage device based on an associated attribute or attributes. A storage device can be configured to write data to a storage location of the storage device based on an associated attribute. The attribute can describe one or more storage-related requirements of the data. The storage device can identify one or more storage locations where the data can be stored that meet the storage-related requirements described by the attribute. A host computer can transmit an updated attribute for the data to the storage device to reflect new storage-related requirements for the data. The storage device can write the data to a new storage location that meets the new requirements. A mapping table can be maintained that associates a logical identifier for the data with the actual storage location where the data is stored.

Abstract: A data storage service stores a dataset on a set of storage nodes in accordance with a first encoding. A set of shards constituting quorum, and one or more additional shards, are stored on the storage nodes. The data storage system determines to store the dataset according to a second encoding, in which the second encoding has fewer total shards. The data storage system reconfigures the storage of the dataset in accordance with the second encoding, such that the reconfigured storage comprises subsets of shards from the first encoding that were not re-encoded in forming the second encoding.

Abstract: Technologies are provided for storing data in a storage device based on an associated attribute or attributes. A storage device can be configured to write data to a storage location of the storage device based on an associated attribute. The attribute can describe one or more storage-related requirements of the data. The storage device can identify one or more storage locations where the data can be stored that meet the storage-related requirements described by the attribute. A host computer can transmit an updated attribute for the data to the storage device to reflect new storage-related requirements for the data. The storage device can write the data to a new storage location that meets the new requirements. A mapping table can be maintained that associates a logical identifier for the data with the actual storage location where the data is stored.

Abstract: A fleet node management system may include a metadata store, a plurality of fleet nodes, and one or more metadata mutation devices. The metadata store may be configured to store dynamic metadata. The plurality of fleet nodes may be configured to determine, based on a gossip protocol, whether to continue performance of a function that uses a local version of the metadata. The one or more metadata mutation devices may be configured to determine, based on a global state of the fleet nodes, whether to modify the dynamic metadata for the fleet nodes.

Abstract: Routing data is copied from a primary data store to a local data store of a computing device. As the routing data is being copied by the computing device, changes to the data continue to occur. After copying all or a portion of the data, the computing device uses a value of a global sequence number (GSN) to determine if mutations have been made to the primary data. The routing data in the local data store is not consistent with the routing data stored in the primary data store when the value of the GSN is larger after the copying of the routing data as compared to the initial value of the GSN when the copying started. When changes have been made to the data, the computing device integrates the changes into the local data store before beginning routing operations.

Abstract: A data storage service stores a dataset on a set of storage nodes in accordance with a first encoding. A set of shards constituting quorum, and one or more additional shards, are stored on the storage nodes. The data storage system determines to store the dataset according to a second encoding, in which the second encoding has a greater number of shards. The data storage system reconfigures the storage of the dataset in accordance with the second encoding, such that the reconfigured storage forms additional shards for the second encoding by combining portions of shards of the first encoding.

Abstract: A key-value store is adapted to represent hierarchical structures, such as directory structures, to be associated with objects otherwise mapped to a flat keyspace. For example, one or more key-value pairs stored in the key-value store are designated to have a key indicating the name of a hierarchical structure, and an associated value that maps the structure to a namespace (e.g., of a group of objects to be associated with a directory). Inbound requests for operations related to the objects in a given namespace and defining the structure are checked against such “redirecting” key-value pairs, as well as one or more policies associated with the structure, the namespace, the key-value pairs, or some combination thereof, to determine whether the structure is related to the namespace objects and whether one or more requested actions are authorized against that structure.

Abstract: A key-value store is adapted to represent hierarchical structures, such as directory structures, to be associated with objects otherwise mapped to a flat keyspace. For example, one or more key-value pairs stored in the key-value store are designated to have a key indicating the name of a hierarchical structure, and an associated value that maps the structure to a namespace (e.g., of a group of objects to be associated with a directory). Inbound requests for operations related to the objects in a given namespace and defining the structure are checked against such “redirecting” key-value pairs to determine whether the structure is related to the namespace objects, and if so, the request is internally processed to perform the requested operations against the actual key-value pair(s) associated with the objects without necessitating identification of the objects with a fully qualified name as represented in the flat keyspace.

Abstract: Functionality is disclosed herein for providing an asynchronous processing service for processing storage mapping information. The asynchronous processing service is configured to receive a storage request including identification of a storage object and a description of a storage operation, perform the storage operation for the storage object in response to receiving the storage request, and asynchronously update mapping information for the performed storage operation.

Abstract: Functionality is disclosed herein for providing an asynchronous processing service for processing storage mapping information. The asynchronous processing service is configured to receive a storage request including identification of a storage object and a description of a storage operation, perform the storage operation for the storage object in response to receiving the storage request, and asynchronously update mapping information for the performed storage operation.