VARIABLE DRIVE HEALTH DETERMINATION AND DATA PLACEMENT

• US 20150234716A1
• Filed: 05/06/2015
• Published: 08/20/2015
• Est. Priority Date: 03/29/2012
• Status: Active Grant

• Current Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Original Assignee: Amazon Technologies, Inc. (Amazon.com, Inc.)
• Inventors: Brooker, Marc J., Holgers, Tobias L., Parthasarathy, Madhuvanesh, Wei, Danny
• Granted Patent: US 10,204,017 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 11/008 Reliability or availability analysis
• CPC Class Codes: G06F 11/1458 Management of the backup or restore process
• CPC Class Codes: G06F 11/30 Monitoring
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3419 by assessing time
• CPC Class Codes: G06F 11/3485 for I/O devices
• CPC Class Codes: G06F 12/02 Addressing or allocation; Relocation program address sequencing G06F9/00; arrangements for selecting an address in a digital store G11C8/00
• CPC Class Codes: G06F 2201/815 Virtual middleware or OS functionality using virtual machines to implement generic software techniques for error detection or fault masking G06F11/1484
• CPC Class Codes: G06F 2201/86 Event-based monitoring
• CPC Class Codes: G06F 3/0619 in relation to data integrity, e.g. data losses, bit errors
• CPC Class Codes: G06F 3/0653 Monitoring storage devices or systems
• CPC Class Codes: G06F 3/0683 Plurality of storage devices

Abstract

The relative health of data storage drives may be determined based, at least in some aspects, on data access information and/or other drive operation information. In some examples, upon receiving the operation information from a computing device, a health level of a drive may be determined. The health level determination may be based at least in part on operating information received from a client entity. Additionally, a storage space allocation instruction or operation may be determined for execution. The allocation instruction or operation determined to be performed may be based at least in part on the determined health level.

Claims

1. A computer-implemented method for data storage management, comprising:

under control of one or more computer systems configured with executable instructions,

receiving operating information associated with a first data storage device, the received operating information indicating an ability to perform operations on data stored in the first data storage device;

determining, based at least in part on the received operating information, a health level for the first data storage device, the health level determined from a plurality of possible health levels in a range of health levels;

receiving an operational parameter associated with a first data object stored in the first data storage device, where the operational parameter indicates performance information of the first data object;

causing, based at least in part on the health level of the first data storage device and the operational parameter, the first data object to be stored in a second data storage device determined to be within a healthy level; and

reallocating storage space of the first data storage device such that it is available for reading or writing a second data object with a second operational parameter indicating second performance information.

2. The computer-implemented method of claim 1, further comprising:

determining that the health level of the first data storage device is within an unhealthy level; and

as a result of determining that the health level of the first data storage device is within the unhealthy level;

causing the first data object to be stored in a second data storage device within the healthy level; and

causing one or more actions to be performed that disable reading or writing to storage space of the first data storage device.

3. The computer-implemented method of claim 1, wherein the operating information includes a performance threshold is based at least in part on a number of lost data packets during a client read or write operation of the first data storage device.

4. The computer-implemented method of claim 1, wherein the operational parameter is based at least in part on at least one of a desired reliability level, a desired performance level, a desired persistence level, or a desired security level.

5. A system, comprising:

one or more processors;

memory with instructions that, when executed by the one or more processors, cause the system to;

receive an operating parameter associated with a first storage system;

determine a health level of the first storage system, wherein the health level is based at least in part on data indicating that the first storage system has a higher probability of failure than a storage system operating normally; and

determine that the health level of the first storage system fails a set of one or more criteria associated with a first data object stored within the first storage system; and

store the first data object in a second storage system with a second health level above the health level.

6. The system of claim 5, wherein a third health level comprising an unhealthy level indicates a storage device with a higher probability of failure than a suspect level.

7. The system of claim 6, wherein the memory further includes instructions that, when executed by the one or more processors, cause the system to:

cause the first data to be stored in a third storage system with the health level comprising the healthy level; and

cause one or more actions to be performed that disable reading or writing to a storage space of the first storage system.

8. The system of claim 6, wherein the memory further includes instructions that, when executed by the one or more processors, cause the system to:

cause the first data to be stored in a third storage system with the health level comprising the suspect level; and

cause one or more actions to be performed that disable reading or writing to a storage space of the first storage system.

9. The system of claim 5, wherein the memory further includes instructions that, when executed by the one or more processors, cause the system to reallocate storage space of the first storage system such that it is not available for storing second data with a data parameter above the one or more criteria.

10. The system of claim 5, wherein the memory further includes instructions that, when executed by the one or more processors, cause the system to:

cause the first data to be stored in a third storage system with a health level of the third storage system comprising the healthy level; and

cause one or more actions to be performed that disable writing to the first storage system.

11. The system of claim 5, wherein the operating parameter is based at least in part on a latency for a read request made, by a client entity, to the first storage system.

12. The system of claim 5, wherein the operating parameter is based at least in part on a latency for a write request made, by a client entity, to the first storage system.

13. The system of claim 5, wherein the health level further comprises a particular health level selected from a multi-variable sliding scale of health levels.

14. The system of claim 13, wherein determining that the health level of the first storage system fails a set of one or more criteria based at least in part on a location, of the first storage system, on the sliding scale of health levels.

15. One or more non-transitory computer-readable media collectively storing computer-executable instructions for data storage management that, when executed by one or more processors, configures the one or more processors to perform operations comprising:

determining, based at least in part on operation information of a remote storage system, a health level of the remote storage system, the health level selected from one or more health levels in a range of health levels;

receiving a parameter associated with data stored in the remote storage system;

determining, based at least in part on the determined health level and the received parameter, storage space allocation associated with data stored in the remote storage system; and

allocating space in the remote storage based storage space allocation.

16. The one or more non-transitory computer-readable media of claim 15, wherein the remote storage system is virtually attached to a client entity.

17. The one or more non-transitory computer-readable media of claim 15, wherein the health level of the remote storage system is based at least in part on a level on a sliding scale of health.

18. The one or more non-transitory computer-readable media of claim 17, wherein the sliding scale of health comprises at least a healthy level, a suspect level that is less healthy than the healthy level, and an unhealthy level that is less healthy than the suspect level.

19. The one or more non-transitory computer-readable media of claim 15, wherein allocating space in the remote storage system further comprises allocating space such that the data stored in the remote storage system is stored in a second remote storage system with a second health level above a predefined level.

20. The one or more non-transitory computer-readable media of claim 19, wherein allocating space in the remote storage system further comprises preventing new data from being written to the remote storage system.