A storage management method, device, equipment and readable storage medium

Abstract

This specification provides a storage management method, apparatus, device, and readable storage medium. The method includes: acquiring the wear life of each managed flash drive according to a preset plan; sorting the wear life of each flash drive in response to an event that a flash drive's wear life has reached a preset first threshold; updating a load balancing strategy based on the sorting result of the wear life of each flash drive, the load balancing strategy including writing more data to flash drives with higher wear life than to flash drives with lower wear life; and distributing a corresponding proportion of business I / O load to each flash drive according to the load balancing strategy. Through the technical solution of this specification, the wear life of each flash drive is actively monitored, and the write load strategy is dynamically adjusted when a preset threshold is reached, so that flash drives with higher wear levels bear more business write volume, actively guiding the wear progress of multiple flash drives in the cluster to differentiate, and avoiding concentrated simultaneous failures.

Description

Technical Field

[0001] This specification relates to the field of communication technology, and in particular to a storage management method, apparatus, device, and readable storage medium. Background Technology

[0002] In distributed storage systems, common disk media include low-cost, large-capacity mechanical hard drives (HDDs) and high-performance, but also expensive, solid-state drives (SSDs). To optimize resource allocation, a current mainstream technical solution is to divide a single SSD into multiple partitions, with each partition serving as a cache for one HDD. This allows one SSD to accelerate multiple HDDs, fully leveraging the performance potential of a single SSD while simultaneously improving the read / write performance of multiple HDDs, thus enhancing the overall performance of the distributed storage system. The advantage of this approach is that it can significantly improve the performance of the entire storage system with a relatively small number of SSDs, greatly reducing costs compared to using all SSDs. However, as a storage medium, SSDs have a limited number of programmable / erase cycles for their flash memory cells, making them consumables with a limited lifespan. When an SSD reaches its maximum write / erase cycle limit, it will fail and stop providing write services, posing a potential risk to the aforementioned acceleration solution.

[0003] In distributed storage systems, data access loads are typically designed to be relatively balanced across disks. This leads to a serious problem: multiple solid-state drives (SSDs, i.e., flash drives) providing acceleration for multiple mechanical hard drives experience highly synchronized data write volumes and wear rates, resulting in similar lifespan degradation. This means that these SSDs, acting as caches, are likely to reach the end of their lifespan around the same time. Each SSD is an independent entity in the system, lacking redundancy protection. In the event of a failure, data recovery relies solely on other nodes in the storage cluster. When multiple SSDs reach near-simultaneous exhaustion and fail, their number may exceed the redundancy limits of the distributed storage system, potentially causing severe incidents such as business interruptions or even data loss—unacceptable for storage systems supporting core business operations. While existing technologies can monitor SSD lifespan by querying disk SMART information, they lack proactive, cluster-level intervention mechanisms to address this risk of synchronized multi-disk degradation. The system passively bears this risk, constituting a significant reliability flaw in existing cache disk acceleration solutions. Summary of the Invention

[0004] In view of this, this specification provides a storage management method, apparatus, device, and readable storage medium to improve the problem of the aforementioned solid-state drive's wear lifespan easily accumulating to an end.

[0005] The specific technical solution is as follows: This specification provides a storage management method for managing a storage management device with multiple solid-state drives (SSDs), wherein the SSDs are non-volatile flash drives with an upper limit to their write / erase life. The method includes: obtaining the wear life of each managed SSD according to a preset plan; in response to an event that an SSD's wear life reaches a preset first threshold, sorting the wear life of each SSD; updating a load balancing strategy based on the sorting result of the wear life of each SSD, wherein the load balancing strategy includes writing more data to SSDs with higher wear life than to SSDs with lower wear life; and distributing a corresponding proportion of business I / O load to each SSD according to the load balancing strategy.

[0006] As a technical solution, the step of obtaining the wear life of each managed solid-state drive according to a preset plan, and sorting the wear life of each solid-state drive in response to an event that the wear life of a solid-state drive has reached a preset first threshold, includes: obtaining the current cluster's used capacity percentage according to a preset plan, and stopping the sorting of the wear life of each solid-state drive and subsequent steps in response to an event that the used capacity percentage is greater than a second threshold.

[0007] As a technical solution, the step of obtaining the wear life of each managed solid-state drive according to a preset plan, and sorting the wear life of each solid-state drive in response to an event that the wear life of a solid-state drive has reached a preset first threshold, includes: periodically sending alarms associated with the solid-state drives whose wear life has reached the preset first threshold in response to an event that the wear life of a solid-state drive has reached the preset first threshold.

[0008] As a technical solution, updating the load balancing strategy based on the ranking results of the wear life of each solid-state drive includes: periodically re-ranking the solid-state drives according to their wear life, and updating the load balancing strategy based on the re-ranking results.

[0009] This specification also provides a storage management device for managing a storage management device with multiple solid-state drives (SSDs). The SSDs are non-volatile flash drives with an upper limit to their write / erase lifespan. The device includes: a first module for acquiring the wear lifespan of each managed SSD according to a preset plan, and sorting the wear lifespans of each SSD in response to an event where an SSD's wear lifespan reaches a preset first threshold; a second module for updating a load balancing strategy based on the sorting result of the wear lifespans of each SSD, wherein the load balancing strategy includes writing more data to SSDs with higher wear lifespans than to SSDs with lower wear lifespans; and a third module for distributing a corresponding proportion of business I / O load to each SSD according to the load balancing strategy.

[0010] As a technical solution, the step of obtaining the wear life of each managed solid-state drive according to a preset plan, and sorting the wear life of each solid-state drive in response to an event that the wear life of a solid-state drive has reached a preset first threshold, includes: obtaining the current cluster's used capacity percentage according to a preset plan, and stopping the sorting of the wear life of each solid-state drive and subsequent steps in response to an event that the used capacity percentage is greater than a second threshold.

[0011] As a technical solution, the step of obtaining the wear life of each managed solid-state drive according to a preset plan, and sorting the wear life of each solid-state drive in response to an event that the wear life of a solid-state drive has reached a preset first threshold, includes: periodically sending alarms associated with the solid-state drives whose wear life has reached the preset first threshold in response to an event that the wear life of a solid-state drive has reached the preset first threshold.

[0012] As a technical solution, updating the load balancing strategy based on the ranking results of the wear life of each solid-state drive includes: periodically re-ranking the solid-state drives according to their wear life, and updating the load balancing strategy based on the re-ranking results.

[0013] This specification also provides an electronic device, including a processor and a readable storage medium storing machine-executable instructions that can be executed by the processor, the processor executing the machine-executable instructions to implement the aforementioned storage management method.

[0014] This specification also provides a readable storage medium storing machine-executable instructions that, when invoked and executed by a processor, cause the processor to implement the aforementioned storage management method.

[0015] The technical solutions provided in this specification offer at least the following beneficial effects: By actively monitoring the wear and tear of each flash drive and dynamically adjusting the write load strategy when a preset threshold is reached, the flash drives with higher wear levels can handle more business writes. This proactively guides the wear and tear of multiple flash drives within the cluster to differentiate, avoiding simultaneous failures. This provides a critical time window for replacing failed drives and rebuilding data, effectively avoiding the risk of data loss due to simultaneous failure of multiple drives, and significantly improving the overall reliability and data security of the storage system. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments of this specification or the prior art, the drawings used in the description of the embodiments of this specification or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings of the embodiments of this specification.

[0017] Figure 1 This is a flowchart of a storage management method according to one embodiment of this specification; Figure 2 This is a flowchart of one embodiment of this specification; Figure 3 This is a structural diagram of a storage management device according to one embodiment of this specification; Figure 4 This is a hardware structure diagram of an electronic device according to one embodiment of this specification.

[0018] Reference numerals: Module 1 21, Module 22, Module 3 23. Detailed Implementation

[0019] The terminology used in the embodiments described herein is for the purpose of describing particular embodiments only and is not intended to limit the scope of this specification. The singular forms “a,” “described,” and “the” as used in this specification and claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to any and all possible combinations comprising one or more of the associated listed items.

[0020] It should be understood that although the terms first, second, third, etc., may be used to describe various information in embodiments of this specification, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this specification, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" may also be interpreted as "when," "when," or "in response to a determination."

[0021] In view of the above, this specification provides a storage management method, apparatus, device, and readable storage medium to at least improve one of the above-mentioned technical problems.

[0022] The specific technical solution is described below.

[0023] In one embodiment, this specification provides a storage management method applied to a storage management device that manages multiple solid-state drives (SSDs), wherein the SSDs are non-volatile flash drives with an upper limit to their write / erase life. The method includes: obtaining the wear life of each managed SSD according to a preset plan; in response to an event that an SSD's wear life reaches a preset first threshold, sorting the wear life of each SSD; updating a load balancing strategy based on the sorting result of the wear life of each SSD, wherein the load balancing strategy includes writing more data to SSDs with higher wear life than to SSDs with lower wear life; and distributing a corresponding proportion of business I / O load to each SSD according to the load balancing strategy.

[0024] This approach involves proactive and intelligent lifespan management and write load control for a storage resource pool composed of multiple non-volatile flash drives (such as SSDs) with limited write and erase lifetimes. The aim is to fundamentally mitigate the risk of concentrated failures caused by synchronized wear and tear across multiple drives. Instead of passively responding after a flash drive failure, this method proactively intervenes before the risk of failure manifests through continuous monitoring, evaluation, and dynamic load redistribution, thereby elevating the reliability of the entire resource pool to a new level.

[0025] The management device can be a standalone storage management server, a management process running on a node in a storage cluster, or part of a distributed storage system management module. It manages a resource pool consisting of multiple flash drives. These flash drives may play various roles in the system; for example, in a typical hybrid storage architecture, flash drives act as cache drives to accelerate larger but slower hard disk drives (HDDs) in the backend. Each flash drive has an upper limit on the number of program / erase cycles determined by the characteristics of the flash memory medium, usually measured as "endurance" or "percentage of life." For example, a solid-state drive (SSD) with a nominal lifespan of 1000 full drive writes is expected to write 1000 times its capacity of data within its lifespan, and its remaining percentage of lifespan gradually decreases as the write volume increases. The management device needs to establish management communication with these flash drives, typically through standard interface protocols (such as SATA, SAS, NVMe) and their accompanying command sets (such as ATA / SMART commands and NVMe Log Page commands) to obtain internal information reflecting their health status.

[0026] Specifically, such as Figure 1 This includes the following steps, the order of which can be changed depending on the needs of the actual application scenario: Step S11: Obtain the wear life of each managed solid-state drive according to the preset plan, and sort the wear life of each solid-state drive in response to an event that the wear life of a solid-state drive has reached a preset first threshold.

[0027] Every hour, the monitoring agent in the management device automatically sends a query request to each flash drive under its jurisdiction to obtain its current health status data (this interval can be adjusted according to business sensitivity and system scale). The specific method for obtaining wear-level lifetime data is typically by querying the flash drive's SMART (Self-Monitoring, Analysis, and Reporting Technology) attribute or the corresponding item in the NVMe Log Page. Key lifetime indicators may be the reciprocal of the "WearLeveling Count" or "Available Spare Percentage," or can be directly obtained through parameters such as "Percentage of Remaining Lifetime" or "Percentage of Used Lifetime." For example, a brand-new flash drive has a "Percentage of Used Lifetime" of 0%, while a drive that has been written with data equivalent to half of its nominal lifetime may display a value of 50%. The management device continuously records the wear-level lifetime values ​​of each flash drive collected each time, forming a view of the lifetime consumption trajectory over time. In addition to periodic polling, this preset schedule can also be triggered by specific events, such as when the system detects an abnormal increase in write IO volume over a period of time, the sampling frequency can be temporarily increased, but this is usually used as a supplement to periodic sampling.

[0028] The preset first threshold here avoids unnecessarily activating the core strategy of this implementation method prematurely, namely the counterproductive load balancing strategy. Its setting requires a balance between security and the frequency of strategy intervention. This threshold cannot be set too low; suitable values ​​include 80% or 70%, because intervention when wear is still minor is not very meaningful and may cause unnecessary performance disturbances. Nor can it be set too high (e.g., 99%), because by then the flash drive is already on the verge of failure, and adjusting the load will be too late.

[0029] A typical and reasonable threshold range is 80% to 90%. For example, the first threshold can be set to 85%. During a routine hourly check, if the monitoring agent finds that the percentage of used lifespan of any flash drive in the resource pool has reached or exceeded 85%, a wear threshold trigger event is generated, causing the system to switch from normal monitoring mode to proactive lifespan management intervention mode.

[0030] The management device will not only process the disk that has reached the threshold, but will perform a unified wear and tear ranking of all managed flash drives in the resource pool to obtain a global view of the lifespan consumption of the entire resource pool at the current moment.

[0031] The sorting is typically done from highest to lowest wear and tear (i.e., from largest to smallest percentage of used life). For example, suppose there are four SSD cache disks in the resource pool, numbered SSD_A, SSD_B, SSD_C, and SSD_D. In this check, their wear and tear values ​​are: SSD_A: 85%, SSD_B: 84%, SSD_C: 83%, and SSD_D: 82%. An event is triggered because SSD_A has reached the 85% threshold. The management device then sorts these four disks, and the result (from highest to lowest) is: SSD_A (85%) > SSD_B (84%) > SSD_C (83%) > SSD_D (82%).

[0032] Step S12: Update the load balancing strategy according to the ranking of the wear life of each solid-state drive. The load balancing strategy includes writing more data to the solid-state drives with more wear life than to the solid-state drives with less wear life.

[0033] The load balancing strategy in this implementation is not intended to balance the wear and tear of each SSD, but rather to be an anti-wear balancing strategy based on the wear and tear status and oriented towards long-term reliability. Specifically, more data is written to the flash drives with higher wear and tear than to the flash drives with lower wear and tear, so as to further increase the wear and tear of the flash drives with higher wear and tear.

[0034] Step S13: Distribute the corresponding proportion of business IO load to each solid-state drive according to the load balancing strategy.

[0035] In the specific implementation of a distributed storage system, the management device adjusts and determines the mapping relationship of the data write path. Taking Ceph as an example, the distribution of data is determined by the mapping (i.e., Cluster Map) from Placement Group (PG) to Object Storage Device (OSD). A PG contains a series of objects, and the objects are ultimately stored in specific OSDs. Each HDD accelerated by SSD can correspond to one OSD.

[0036] After management devices (such as Ceph's Monitor nodes) update their load balancing strategies, future write requests will increasingly fall on disks with higher weights and greater wear, while the proportion of new write requests falling on low-wear disks will decrease. Similar strategies can be implemented at the lower-level caching software (such as Flashcache, OpenCAS) or device driver levels. For example, a unified cache management layer can receive this write ratio strategy and, within its internal routing logic, distribute write requests from upper-layer applications to multiple backend SSD cache disks according to calculated probabilities, giving higher probabilities to disks with greater wear and lower probabilities to disks with less wear.

[0037] In one implementation, the step of obtaining the wear life of each managed solid-state drive according to a preset plan, and sorting the wear life of each solid-state drive in response to an event that there is a solid-state drive whose wear life has reached a preset first threshold, includes: obtaining the current cluster's used capacity percentage according to a preset plan, and stopping the sorting of the wear life of each solid-state drive and subsequent steps in response to an event that the used capacity percentage is greater than a second threshold.

[0038] In one implementation, the step of acquiring the wear life of each managed solid-state drive according to a preset plan, and sorting the wear life of each solid-state drive in response to an event that there is a solid-state drive whose wear life has reached a preset first threshold, includes: periodically sending alarms associated with solid-state drives whose wear life has reached the preset first threshold in response to an event that there is a solid-state drive whose wear life has reached the preset first threshold.

[0039] In one implementation, updating the load balancing strategy based on the ranking of the wear life of each solid-state drive includes: periodically re-ranking the solid-state drives according to their wear life, and updating the load balancing strategy based on the re-ranking results.

[0040] In one implementation, such as Figure 2 The system monitors the lifecycle of each individual SSD and performs anti-wear control on the cache SSDs of the storage cluster. This combines cache disk lifecycle monitoring with anti-wear leveling of data disk IO ratios to manage cache SSDs that reach pre-set lifespan thresholds. This addresses the issue of multiple SSDs reaching their lifespan simultaneously, preventing business interruptions or data loss. Specific steps include: 1. Initialize the storage cluster and read the disk inspection cycle from the configuration file; 2. The storage cluster configures the periodic check cycle for the SSD cache disks according to the configuration file; 3. Set thresholds for SSD lifespan and implement different solutions based on different SSD lifespan degradation levels.

[0041] The device management module periodically queries the SMART information of each SSD cache disk. The OSD registers cache disk wear events that reach a threshold. If a cache disk with wear exceeding 80% is detected, the OSD reports the cache disk wear event to the monitor. After exceeding the threshold, the OSD reports once every hour.

[0042] After receiving information that the cache disk has more than 80% wear, the cluster monitoring module (monitor) sorts all reported cache disks according to their wear level and compares them with the previous sorting information. If there is no change, the load balancing strategy is not updated; if there is a change, the IO increase ratio of each disk is recalculated.

[0043] The IO interface module receives the new anti-wear leveling disk IO ratio and selects it according to this ratio when issuing the PG selection for service IO, in order to control the proportion of service IO on the cache disk.

[0044] When the cluster data disk capacity exceeds 85% (the highest OSD capacity in the storage pool), the anti-pattern mechanism will no longer be effective, but this threshold can be adjusted as needed.

[0045] The goal of this implementation is to manage SSD lifespan thresholds in a tiered manner, employing different strategies based on pre-set thresholds. When an SSD's lifespan has not reached the wear threshold, a data balancing strategy is used, meaning each cache disk bears the same workload. When an SSD's lifespan reaches the wear threshold, data writing is periodically adjusted based on the cache disk's wear level to achieve phased cache disk failures. Simultaneously, considering high-capacity disk replacement scenarios in the storage cluster, when the data disk's capacity reaches the threshold, no anti-wear adjustment of the cache disk is performed to prevent the data disk from becoming full and impacting business operations.

[0046] In one implementation, such as Figure 3 This specification also provides a storage management device for managing a storage management device with multiple solid-state drives (SSDs). The SSDs are non-volatile flash drives with an upper limit to their write / erase lifespan. The device includes: a first module for acquiring the wear lifespan of each managed SSD according to a preset plan, and sorting the wear lifespans of each SSD in response to an event where the wear lifespan of an SSD reaches a preset first threshold; a second module for updating a load balancing strategy based on the sorting result of the wear lifespans of the SSDs, wherein the load balancing strategy includes writing more data to SSDs with higher wear lifespans than to SSDs with lower wear lifespans; and a third module for distributing a corresponding proportion of business I / O load to each SSD according to the load balancing strategy.

[0047] In one implementation, the step of obtaining the wear life of each managed solid-state drive according to a preset plan, and sorting the wear life of each solid-state drive in response to an event that there is a solid-state drive whose wear life has reached a preset first threshold, includes: obtaining the current cluster's used capacity percentage according to a preset plan, and stopping the sorting of the wear life of each solid-state drive and subsequent steps in response to an event that the used capacity percentage is greater than a second threshold.

[0048] In one implementation, the step of acquiring the wear life of each managed solid-state drive according to a preset plan, and sorting the wear life of each solid-state drive in response to an event that there is a solid-state drive whose wear life has reached a preset first threshold, includes: periodically sending alarms associated with solid-state drives whose wear life has reached the preset first threshold in response to an event that there is a solid-state drive whose wear life has reached the preset first threshold.

[0049] In one implementation, updating the load balancing strategy based on the ranking of the wear life of each solid-state drive includes: periodically re-ranking the solid-state drives according to their wear life, and updating the load balancing strategy based on the re-ranking results.

[0050] The implementation methods of the apparatus are the same as or similar to the corresponding implementation methods, and will not be described again here.

[0051] In one embodiment, this specification provides an electronic device including a processor and a readable storage medium storing machine-executable instructions executable by the processor. The processor executes the machine-executable instructions to implement the aforementioned storage management method. From a hardware perspective, a hardware architecture diagram can be found... Figure 3 As shown.

[0052] In one embodiment, this specification provides a readable storage medium storing machine-executable instructions that, when invoked and executed by a processor, cause the processor to implement the aforementioned storage management method.

[0053] Here, a readable storage medium can be any electronic, magnetic, optical, or other physical storage device that can contain or store information, such as executable instructions, data, etc. For example, a readable storage medium can be: RAM (Random Access Memory), volatile memory, non-volatile memory, flash memory, storage drives (such as hard disk drives), solid-state drives, any type of storage disk (such as optical discs, DVDs, etc.), or similar storage media, or combinations thereof.

[0054] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which can take the form of a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email sending and receiving device, game console, tablet computer, wearable device, or any combination of these devices.

[0055] For ease of description, the above devices are described in terms of function, divided into various units. Of course, in implementing this specification, the functions of each unit can be implemented in one or more software and / or hardware components.

[0056] Those skilled in the art will understand that embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, this specification can take the form of a completely hardware implementation, a completely software implementation, or an implementation combining software and hardware aspects. Furthermore, embodiments of this specification can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0057] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments thereof. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0058] Furthermore, these computer program instructions can also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in the process. Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0059] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0060] Those skilled in the art will understand that embodiments of this specification can be provided as methods, systems, or computer program products. Therefore, this specification can take the form of a completely hardware implementation, a completely software implementation, or an implementation combining software and hardware aspects. Furthermore, this specification can take the form of a computer program product implemented on one or more computer-usable storage media (which may include, but are not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0061] The above description is merely an embodiment of this specification and is not intended to limit this specification. Various modifications and variations can be made to this specification by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of the claims of this specification.

Claims

1. A storage management method, characterized in that, A method for managing a storage management device with multiple solid-state drives (SSDs), wherein the SSDs are non-volatile flash drives with an upper limit on their write / erase cycles, the method comprising: According to a preset plan, the wear life of each managed solid-state drive is obtained, and in response to an event that there is a solid-state drive whose wear life has reached a preset first threshold, the wear life of each solid-state drive is sorted. Based on the ranking of the wear life of each solid-state drive, the load balancing strategy is updated. The load balancing strategy includes writing more data to the solid-state drives with higher wear life than to the solid-state drives with lower wear life. Based on the load balancing strategy, the corresponding proportion of business I / O load is distributed to each solid-state drive.

2. The method according to claim 1, characterized in that, The process of acquiring the wear life of each managed solid-state drive according to a preset plan, and in response to an event that a solid-state drive's wear life has reached a preset first threshold, sorting the wear life of each solid-state drive, includes: According to the preset plan, the current cluster's used capacity percentage is obtained. In response to an event that the used capacity percentage is greater than the second threshold, the process of sorting the wear life of each solid-state drive and subsequent steps is stopped.

3. The method according to claim 1, characterized in that, The process of acquiring the wear life of each managed solid-state drive according to a preset plan, and in response to an event that a solid-state drive's wear life has reached a preset first threshold, sorting the wear life of each solid-state drive, includes: In response to an event that a solid-state drive (SSD) has reached a preset first threshold of wear life, periodically send an alarm associated with the SSD that has reached the preset first threshold of wear life.

4. The method according to claim 1, characterized in that, The process of updating the load balancing strategy based on the ranking of the wear and tear of each solid-state drive includes: The load balancing strategy is periodically reordered based on the wear and tear of each solid-state drive and updated accordingly.

5. A storage management device, characterized in that, A storage management device for managing multiple solid-state drives (SSDs), wherein the SSDs are non-volatile flash drives with an upper limit on their write / erase cycles, the device comprising: The first module is used to obtain the wear life of each managed solid-state drive according to a preset plan, and in response to an event that there is a solid-state drive whose wear life has reached a preset first threshold, sort the wear life of each solid-state drive. The second module is used to update the load balancing strategy based on the ranking of the wear life of each solid-state drive. The load balancing strategy includes writing more data to the solid-state drives with more wear life than to the solid-state drives with less wear life. The third module is used to distribute the corresponding proportion of business I / O load to each solid-state drive according to the load balancing strategy.

6. The apparatus according to claim 5, characterized in that, The process of acquiring the wear life of each managed solid-state drive according to a preset plan, and in response to an event that a solid-state drive's wear life has reached a preset first threshold, sorting the wear life of each solid-state drive, includes: According to the preset plan, the current cluster's used capacity percentage is obtained. In response to an event that the used capacity percentage is greater than the second threshold, the process of sorting the wear life of each solid-state drive and subsequent steps is stopped.

7. The apparatus according to claim 5, characterized in that, The process of acquiring the wear life of each managed solid-state drive according to a preset plan, and in response to an event that a solid-state drive's wear life has reached a preset first threshold, sorting the wear life of each solid-state drive, includes: In response to an event that a solid-state drive (SSD) has reached a preset first threshold of wear life, periodically send an alarm associated with the SSD that has reached the preset first threshold of wear life.

8. The apparatus according to claim 5, characterized in that, The process of updating the load balancing strategy based on the ranking of the wear and tear of each solid-state drive includes: The load balancing strategy is periodically reordered based on the wear and tear of each solid-state drive and updated accordingly.

9. An electronic device, characterized in that, include: A processor and a readable storage medium storing machine-executable instructions that can be executed by the processor to implement the method of any one of claims 1-4.

10. A readable storage medium, characterized in that, The readable storage medium stores machine-executable instructions that, when invoked and executed by a processor, cause the processor to implement the method of any one of claims 1-4.

Images