CN114500575A - Path loss management method, device and storage medium in multipath object map - Google Patents
Path loss management method, device and storage medium in multipath object map Download PDFInfo
- Publication number
- CN114500575A CN114500575A CN202111614724.1A CN202111614724A CN114500575A CN 114500575 A CN114500575 A CN 114500575A CN 202111614724 A CN202111614724 A CN 202111614724A CN 114500575 A CN114500575 A CN 114500575A
- Authority
- CN
- China
- Prior art keywords
- path
- loss
- map
- paths
- lost
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000007726 management method Methods 0.000 title description 24
- 238000000034 method Methods 0.000 claims abstract description 58
- 238000011084 recovery Methods 0.000 claims abstract description 15
- 238000004590 computer program Methods 0.000 claims description 20
- 238000012545 processing Methods 0.000 claims description 12
- 230000008569 process Effects 0.000 abstract description 18
- 238000001514 detection method Methods 0.000 description 9
- 230000006870 function Effects 0.000 description 7
- 230000009191 jumping Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 5
- 230000008859 change Effects 0.000 description 4
- 238000012423 maintenance Methods 0.000 description 4
- 230000002093 peripheral effect Effects 0.000 description 4
- 230000001960 triggered effect Effects 0.000 description 4
- 230000002159 abnormal effect Effects 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 238000013473 artificial intelligence Methods 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008570 general process Effects 0.000 description 1
- 238000010801 machine learning Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 239000000725 suspension Substances 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/24—Multipath
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Retry When Errors Occur (AREA)
Abstract
The application provides a method, a device and a storage medium for managing path loss in a multi-path object map, wherein the method comprises the following steps: after receiving a preset trigger command, acquiring a member variable total _ paths in a target multi-path object map, and traversing and determining the number n of sub-paths currently contained in the map; if n is less than total _ paths, if the determined state is that the path is lost currently, acquiring the times of automatically retrieving the lost path, and judging whether the times reach a set threshold value; if so, recording a first fault log, and sending the first fault log to the client; if not, starting the automatic finding process of the lost path. According to the scheme, the lost sub-paths in the multi-path object map can be found in time, the upper limit value of the automatic recovery times is set when the lost sub-paths are automatically recovered, the lost paths can be found in time and the lost paths can be effectively recovered, and the high efficiency and stability of the system are effectively ensured.
Description
Technical Field
The application relates to a method and a device for managing path loss in a multi-path object map and a storage medium, and belongs to the technical field of cloud computing storage multi-path management.
Background
In the field of storage in cloud computing, multipath is used to exclusively manage IO paths, and is widely used particularly in FC-SAN and IP-SAN environments. The main function of the multipath is to cooperate with the storage device to implement the following functions: switching and recovering of faults, load balancing of IO flow, virtualization of a disk and transient jitter of an IO suspension filter data link. Due to the existence of multiple paths, the storage subsystem is more robust and stable, and the IO bandwidth of the system is greatly improved, so that the method is widely applied to the field of cloud computing.
Currently, the most widely applied open-source multipath software in the field of cloud computing storage is multipath-tools derived from reddat. However, the current multipath software does not pay special attention and manage the number of paths, when the system runs, if abnormal change of back-end storage occurs, due to the fact that a storage device manufacturer adapts to a kernel, the kernel drives a bug or the multipath software restarts to take effect of new configuration and other factors in the changing process, the multipath cannot synchronize the change, and the changed partial paths in the multipath object map are lost, because the client services of the available paths work normally temporarily, the client does not sense, but when the rest paths are failed, the storage cannot be accessed at all, and the client services are interrupted. The lost path may be good, and if the path is not lost, the path can be automatically switched, so that the client service can be prevented from being interrupted.
Therefore, how to find and repair the missing sub-paths in the multi-path object map in time becomes a big problem at present.
Disclosure of Invention
The application provides a method and a device for calling a rule engine SDK (software development kit) and a storage medium, which are used for solving the technical problem that a sub-path lost in a multi-path object map cannot be found and repaired in time.
In a first aspect, a method for managing path loss in a multipath object map is provided according to an embodiment of the present application, including:
after receiving a preset trigger command, acquiring member variables in a target multi-path object map, and traversing sub-paths of the target multi-path object map to determine the number n of sub-paths currently contained in the target multi-path object map; the member variables comprise the total number of starting sub-paths total _ paths contained in the target multi-path object map;
if the number n of sub paths currently contained in the target multi-path object map is smaller than the total number total _ paths of initial sub paths contained in the target multi-path object map, and the determined state is that the path is lost currently, acquiring the times map, FIND _ LOSS _ RETRY of automatically retrieving the lost path, and judging whether the times map, FIND _ LOSS _ RETRY of automatically retrieving the lost path reaches a set threshold value MAX _ LOSS _ FIND _ RETRY;
and if the number of times of automatically retrieving the lost path, map, FIND _ LOSS _ RETRY reaches a set threshold value, MAX _ LOSS _ FIND _ RETRY, recording a first fault log, and sending the first fault log to the client.
In one embodiment, the member variables further include a path loss flag map in the target multipath object map, path _ loss, and the method further includes:
if the number of times of automatically retrieving the lost path, map, FIND _ LOSS _ RETRY, does not reach the set threshold value, MAX _ LOSS _ FIND _ RETRY:
setting the value of a path loss mark map, path _ loss, in a target multi-path object map as true, and adding 1 to the times of automatically retrieving the lost path map, find _ loss _ retry;
controlling to execute a udevadm trigger command, and determining whether the lost path is found back according to the execution result of the udevadm trigger command;
if the execution result is determined to be 'successful recovery' according to the udevadm trigger command, recording a 'successful recovery' log, setting the value of a path loss mark map, path _ loss to be false, and setting the times of automatically recovering the lost path map, find _ loss _ retry to be zero;
if the execution result is determined to be 'the lost path is not found back' according to the udevadm trigger command, controlling to execute a rescan command to scan the storage node corresponding to the sub-path contained in the target multi-path object map;
if the storage block devices which are lost previously and correspond to the sub paths contained in the target multi-path object map are scanned by executing the rescan command, recording a log of successful retrieval, setting the value of a path loss mark map, path _ loss to be false, and setting the times of automatically retrieving the lost paths map, find _ loss _ retry to be zero;
and if the storage block devices which are lost previously and correspond to the sub paths contained in the target multi-path object map are not scanned by executing the rescan command, recording a second fault log and sending the second fault log to the client.
In one embodiment, the method further comprises:
adding a path LOSS mark map in the target multi-path object map, a set threshold MAX _ LOSS _ FIND _ RETRY aiming at the times of automatically retrieving the lost path, and the number N of sub-paths contained in the target multi-path object map into the target multi-path object map;
the initial value of the path LOSS flag map in the target multi-path object map is false, the set threshold MAX _ LOSS _ FIND _ RETRY for automatically retrieving the lost path number is 5, the variable N representing the number of sub-paths included in the target multi-path object map is initially 0, and the updating is performed automatically once every time an effective sub-path is traversed.
In one embodiment, the method further comprises:
if the current number n is equal to the total number of initial sub-paths, total _ paths, contained in the target multi-path object map, continuously judging whether a path loss flag, map _ loss, in the target multi-path object map is true;
if the path loss flag map, path _ loss, in the target multi-path object map is true, determining that the target multi-path object map has path loss but the current lost path has been successfully retrieved, recording a log of successful retrieval, setting the value of the path loss flag map, path _ loss to false, and setting the times of automatically retrieving the lost path map, find _ loss _ retry to zero.
In one embodiment, the method further comprises:
if the current number n is greater than the total number of the initial sub-paths total _ paths contained in the target multi-path object map, determining that a new path is found currently, adding 1 to the total number of the initial sub-paths total _ paths contained in the target multi-path object map, setting the value of a path loss flag map.
In one embodiment, the preset trigger command is a check _ path thread start command, a uevent event receive command, or a path add operation command.
In one embodiment, the method further comprises:
aiming at a target multipath object map, acquiring a unique identifier of the target multipath object map;
determining the number of sub paths with the same identification as the unique identification of the target multi-path object map;
the number of sub-paths identical to the unique identifier of the target multi-path object map is determined as the total number of start sub-paths total _ paths contained in the target multi-path object map.
In a second aspect, an apparatus for managing path loss in a multipath object according to an embodiment of the present application includes:
the acquiring module is used for acquiring member variables in the target multi-path object map after receiving a preset trigger command, and traversing sub-paths of the target multi-path object map to determine the number n of the sub-paths currently contained in the target multi-path object map; the member variables comprise the total number of starting sub-paths total _ paths contained in the target multi-path object map;
the judging module is used for acquiring the times map, FIND _ LOSS _ RETRY of automatically retrieving the lost path if the current number n is smaller than the total number total _ paths of the initial sub-paths contained in the target multi-path object map and the determined state is that the path is lost currently, and judging whether the times map, FIND _ LOSS _ RETRY of automatically retrieving the lost path reaches the set threshold MAX _ LOSS _ FIND _ RETRY;
the processing module is used for recording a first fault log and sending the first fault log to the client if the number of times of automatically retrieving the lost path, map, FIND _ LOSS _ RETRY, reaches a set threshold value MAX _ LOSS _ FIND _ RETRY; and if the times of automatically retrieving the lost path, map, find _ loss _ retry, do not reach the set threshold, starting the automatic lost path retrieving process.
In a third aspect, an apparatus for managing a path loss in a multipath object is provided according to an embodiment of the present application, the apparatus includes a processor, a memory, and a computer program stored in the memory and executable on the processor, where the computer program is loaded and executed by the processor to implement any one of the above methods for managing a path loss in a multipath object.
In a fourth aspect, according to an embodiment of the present application, there is provided a computer-readable storage medium storing a computer program, where the computer program is used to implement any one of the above path loss management methods in a multipath object when being executed by a processor.
The beneficial effect of this application lies in:
according to the scheme, after a preset trigger command is received, whether path loss occurs or not is determined according to the number n of sub paths currently contained in the target multi-path object map and the total number total _ paths of initial sub paths contained in the target multi-path object map.
The foregoing description is only an overview of the technical solutions of the present application, and in order to make the technical solutions of the present application more clear and clear, and to implement the technical solutions according to the content of the description, the following detailed description is made with reference to the preferred embodiments of the present application and the accompanying drawings.
Drawings
Fig. 1 to 5 are flowcharts of a method for managing path loss in a multi-path object map according to an embodiment of the present application, respectively;
fig. 6 and fig. 7 are algorithm diagrams of a path loss management method in a multi-path object map in an embodiment, respectively;
fig. 8 is a schematic diagram of a path loss management apparatus in a multi-path object map according to an embodiment of the present application;
fig. 9 is a block diagram of a path loss management apparatus in a multipath object map according to an embodiment of the present application.
Detailed Description
The following examples are intended to illustrate the present application but are not intended to limit the scope of the present application.
The current multi-tools involve the following four general process flows for paths:
1) restarting/reconfiguring the multipath service command to configure the multipath flow;
2) the method comprises the steps that an add event generated after storage block equipment is scanned by a system triggers an automatic adding process of a path;
3) the method comprises the following steps of deleting a path triggered by add/remove ue or change ue generated by the change of a rear-end storage block device;
4) and manually deleting the path flow.
In the above several processing flows for the path, a scenario that the path is abnormally lost may be caused:
(1) the automatic deletion after the equipment failure specifically comprises the following steps: when the failure is recovered, part of the sub-path devices of the block device do not generate an add path event (for reasons of storing a bottom-layer drive version or kernel version compatibility, etc.), that is, an automatic addition flow cannot be triggered, so that the path is lost; (2) after the device recovers from the failure, an add path uevent is generated, but at the moment, the user just restarts the multipath service or validates the new multipath configuration by using a reconfigure command, and at the moment, the multipath cannot handle the event, so that the recovered path cannot be added again to cause the path loss. (3) Path loss caused by accidental manual deletion and non-manual recovery (temporary failed paths may be deleted when the operation and maintenance switches the standby paths to avoid unnecessary logs for path check failure and multi-path state abnormity, and the paths are forgotten to be added again after the standby paths are recovered); (4) after a program which is left in the device is removed (after part of the storage devices are abnormal, the program can be left in the kernel and cannot be automatically recovered, and the device needs to be removed first and then scanned again), the deleted path may be not scanned out in time at a low probability after rescanning, so that the path is lost.
When a path in a multi-path object loses part of paths due to the four scenes, a client cannot sense the path currently, if the path cannot be found back in time, the effect of load balancing is weakened, and in the worst case, service interruption caused by the fact that the path cannot be switched in a failure mode can be possibly caused along with the gradual loss of sub-paths in the multi-path object.
Based on the above problems, the present application provides a technical solution for managing path loss in a multipath object map, which can add a mechanism and a method for managing multipath paths based on the most widely used open-source multipath software multipath-tools at present.
Referring to fig. 1, an embodiment of the present application provides a method for managing a path loss in a multipath object map, where the method includes:
step S12, after receiving a preset trigger command, acquiring member variables in the target multi-path object map, and traversing sub-paths of the target multi-path object map to determine the number n of sub-paths currently contained in the target multi-path object map; the member variables comprise the total number of starting sub-paths total _ paths contained in the target multi-path object map;
in the embodiment of the application, after receiving the preset trigger command, the preset trigger command is a check _ path thread start command, a uevent event receive command, or a path addition operation command. Specifically, the method comprises the following steps:
1) when a starting command of a check _ path round-robin checking path state of the checker module is detected, triggering to start executing member variables in the target multi-path object map, and traversing sub-paths of the target multi-path object map to determine the number n of sub-paths currently contained in the target multi-path object map.
2) When a uevent event receiving command is detected, it is indicated that the back-end equipment is updated, a path corresponding to the uevent is triggered to acquire member variables in a target multi-path object map, and sub-paths of the target multi-path object map are traversed to determine the number n of the sub-paths currently contained in the target multi-path object map.
3) When receiving the path adding operation, the path adding operation may be an operation of manually adding a path using an add path command, and at this time, the acquisition of the member variable in the target multipath object map is also triggered, and the number n of sub-paths currently included in the target multipath object map is determined by traversing the sub-paths of the target multipath object map.
Step S14, if the number n of sub paths currently contained in the target multi-path object map is smaller than the total number total _ paths of the initial sub paths contained in the target multi-path object map, and the determined state is that the path is lost currently, acquiring the times map, FIND _ LOSS _ RETRY of automatically retrieving the lost path, and judging whether the times map, FIND _ LOSS _ RETRY of automatically retrieving the lost path reaches the set threshold MAX _ LOSS _ FIND _ RETRY;
in the embodiment of the present application, whether a path LOSS occurs is determined according to a magnitude relationship between a number n of sub paths currently included in a target multi-path object map and a total number of start sub paths total _ paths included in the target multi-path object map, and if the current number n is smaller than the total number of start sub paths total _ paths included in the target multi-path object map, the determined state is that the path LOSS occurs currently, and a number of times of automatically retrieving a lost path, which is map, FIND, LOSS, return, is continuously obtained, and it is determined whether the number of times of automatically retrieving the lost path, which is map, FIND, LOSS, return, reaches a set threshold value, which is load, FIND, return.
It is pointed out that if the number of times map, FIND _ LOSS _ RETRY of automatic recovery of the lost path has reached the set threshold MAX _ LOSS _ FIND _ RETRY, it indicates that the set threshold number of times has been reached but the lost path has not been successfully recovered, and at this time, in order to save system overhead, the scheme terminates the automatic recovery process; and if the number of times of automatically retrieving the lost path map, FIND _ LOSS _ RETRY does not reach the set threshold value MAX _ LOSS _ FIND _ RETRY, starting the automatic retrieving process of the lost path, and continuing to automatically retrieve the lost path.
And step S16, if the number of times of automatically retrieving the lost path, map, FIND _ LOSS _ RETRY, reaches a set threshold value MAX _ LOSS _ FIND _ RETRY, recording a first fault log, and sending the first fault log to the client.
In the embodiment of the application, the first fault log is that after the MAX _ LOSS _ FIND _ RETRY is automatically retrieved for several times, the path is not retrieved yet, and the storage link and the configuration need to be checked, and when the MAX _ LOSS _ FIND _ RETRY is automatically retrieved for several times and the path is not retrieved successfully, the first fault log information is sent to the client, so that the client is subjected to manual detection by operation and maintenance personnel according to the fault log, and after the operation and maintenance personnel send the detection result manually, the system receives the manual detection result and stores the manual detection result.
In an embodiment of the present application, the method further comprises performing an automatic recovery process; referring to fig. 2, the member variables further include a path loss flag map, path _ loss, in the target multipath object map, and the automatic recovery process included in the method includes:
step S15, if the number of times of automatically retrieving the lost path, map, FIND _ LOSS _ RETRY, does not reach the set threshold MAX _ LOSS _ FIND _ RETRY, then:
setting the value of a path loss mark map, path _ loss, in a target multi-path object map as true, and adding 1 to the times of automatically retrieving the lost path map, find _ loss _ retry;
controlling to execute a udevadm trigger command, and determining whether the lost path is found back according to the execution result of the udevadm trigger command;
if the execution result is determined to be 'successful recovery' according to the udevadm trigger command, recording a 'successful recovery' log, setting the value of a path loss mark map, path _ loss to be false, and setting the times of automatically recovering the lost path map, find _ loss _ retry to be zero;
if the execution result is determined to be 'the lost path is not found back' according to the udevadm trigger command, controlling to execute a rescan command to scan the storage node corresponding to the sub-path contained in the target multi-path object map;
if the storage block devices which are lost previously and correspond to the sub paths contained in the target multi-path object map are scanned by executing a rescan command, recording a log of successful recovery, setting the value of a path loss mark map, path _ loss as false, and resetting the times of automatically recovering the lost paths, map, find _ loss _ retry;
and if the storage block devices which are lost previously and correspond to the sub paths contained in the target multi-path object map are not scanned by executing the rescan command, recording a second fault log and sending the second fault log to the client.
In the embodiment of the present application, referring to fig. 3, the method further includes:
step S11, adding a path LOSS flag map in the target multipath object map, path _ LOSS, a set threshold MAX _ LOSS _ FIND _ RETRY for automatically retrieving the number of lost paths, and the number N of sub paths included in the target multipath object map to the target multipath object map;
the initial value of the path LOSS flag map, path _ LOSS, in the target multipath object map is false, the set threshold value MAX _ LOSS _ FIND _ RETRY for automatically retrieving the number of times of lost paths is 5, the number N of sub-paths included in the target multipath object map is initially 0, and the value of the number N of sub-paths included in the target multipath object map is automatically updated once every time one sub-path is traversed, that is, every time one effective sub-path is queried through traversal, the value of N is added by 1.
In the embodiment of the present application, referring to fig. 4, the method further includes:
step 117, if the number n of sub paths currently included in the target multi-path object map is equal to the total number of start sub paths total _ paths included in the target multi-path object map, continuously determining whether a path loss flag map _ path _ loss in the target multi-path object map is true; if the path loss flag map, path _ loss, in the target multi-path object map is true, determining that the target multi-path object map has path loss but the current lost path has been successfully retrieved, recording a log of successful retrieval, setting the value of the path loss flag map, path _ loss to false, and setting the times of automatically retrieving the lost path map, find _ loss _ retry to zero.
In this embodiment, if the number n of sub paths currently included in the target multi-path object map is equal to the total number of start sub paths total _ paths included in the target multi-path object map, it indicates that a path loss of the multi-path object has occurred, and now, due to the recovery of the storage link, the lost path is added back again, at this time, it is necessary to record the log of the recovered number of multi-path paths and reset the map _ path _ loss flag to 0 and the map _ find _ loss _ retry to 0 count, so as to restart the counting during the next round of detection, and end the round of path detection.
In an embodiment of the present application, the method further includes:
if the number n of sub-paths currently included in the target multi-path object map is greater than the total number of start sub-paths total _ paths included in the target multi-path object map, it is determined that "a new path is found currently", the total number of start sub-paths total _ paths included in the target multi-path object map is added by 1, the value of a path loss flag map _ path _ loss is set to be false, and the number of times of automatically finding back a lost path, map _ find _ loss _ retry, is set to be zero.
In an embodiment of the present application, referring to fig. 5, the method further includes:
step S101, aiming at a target multipath object map, acquiring a unique identifier of the target multipath object map;
step S102, determining the number of sub paths with the same identification as the unique identification of the target multi-path object map;
step S103, determining the number of sub paths identical to the unique identifier of the target multi-path object map as the total number of start sub paths total _ paths included in the target multi-path object map.
In this embodiment of the present application, when creating a multipath, a user mode process (multipath) first checks a path state, excludes a path with an abnormal state and a path that is masked, then generates a multipath object for path aggregation (all paths with the same NAA are attributed to a multipath object as a sub-path of the multipath object, and the NAA is an identifier uniquely identifying a storage block device), configures the multipath, reports the multipath object to a kernel DM, and the DM notifies a user mode after creating a multipath device in the kernel, and then adds logic: and counting the number of all sub paths of the multi-path object and storing the number of all sub paths to a total _ paths member variable of the multi-path object.
Two specific examples are set forth below:
detailed description of the preferred embodiment
When the preset trigger command is a check _ path thread start command, that is, a command for checking the path state in a check _ path round trip of the checker module is received, as shown in fig. 6, the following flow of counting and checking the number of multipath paths is executed:
s001, starting check _ loop;
s002, the check _ path thread checks the state of all paths on the host, namely the link state of all sub-paths contained in the target multi-path object;
s003, counting the number of all sub paths in the multi-path object map to which the current path belongs;
s004, judging the relationship between the path number of the current map and the total _ paths in the map; if the path number of the current map is larger than the total _ paths in the map, executing S005; if the path number of the current map is equal to total _ paths in the map, executing S006; if the path number of the current map is less than the total _ paths in the map, executing S008;
s005, updating the total _ path of the map; resetting path _ loss and find _ loss _ retry of the map, and jumping to S001;
s006, judging whether the path _ loss of the map is true; if path _ loss of map is true, then S007 is executed;
s007, recording the log of 'path number recovered', setting path _ loss as false and find _ loss _ retry as 0, and not skipping to S001;
s008, judging whether the path retrieval times FIND _ LOSS _ RETRY of the map is smaller than MAX _ LOSS _ FIND _ RETRY; if yes, executing the step S009, otherwise, executing the step S010;
s009, if the FIND _ LOSS _ RETRY is smaller than MAX _ LOSS _ FIND _ RETRY, continuously judging whether the path _ LOSS is true; if true, executing step S011, and if not true, executing step S010;
s010, recording a log, namely after the path is found back for the appointed times, the path is still not found back, and a physical link needs to be manually detected and stored, and jumping to S001;
s011, recording a path loss log, setting a path loss mark path _ loss corresponding to the map as true, and continuing to execute the step S011;
s012, starting the lost path retrieving process; increasing the find _ loss _ retry count of the map, and continuing to execute S013;
s013, executing a udevadm trigger command;
s014, judging whether the path is retrieved; if yes, executing S017, if not, executing S15;
s15, performing rescan scanning and storing at the back end;
s016, judging whether the path is found back; if the mobile terminal is found back, executing S017, otherwise, skipping to S001;
s017, the log recording path is retrieved through a retrieving process, the path _ loss of the map is reset to false, the find _ loss _ retry is 0, and the process jumps to S001.
Detailed description of the invention
When the preset trigger command is a uevent event receiving command, it indicates that the backend device has an update, and therefore, triggers a counting and checking process of the number of multipath paths, specifically referring to fig. 7, the executed counting and checking process of the number of multipath paths is as follows:
s101, uev _ trigger is started;
S102、uev_update_path/uev_add_apth；
s103, counting the number of all sub paths in the multi-path object map to which the path belongs;
s104, judging the relationship between the path number of the current map and the total _ paths in the map; if the path number of the current map is equal to total _ paths in the map, executing S105; if the path number of the current map is less than the total _ paths in the map, executing S107; if the path number of the current map is larger than the total _ paths in the map, executing S116;
s105, judging whether the path _ loss of the map is true, if so, continuing to execute S106, otherwise, skipping to the ending step;
s106, recording a log of 'path quantity recovered', setting path _ loss as false and find _ loss _ retry as 0, and skipping to the end step;
s107, judging whether the path _ loss of the map is true or not; if the path _ loss of the map is true, executing S108; otherwise, executing S108 after executing S109;
s108, judging whether the path retrieval times FIND _ LOSS _ RETRY of the map is less than MAX _ LOSS _ FIND _ RETRY; if yes, executing step S110, otherwise, executing step S117;
s109, recording a path loss log, setting a path loss mark path _ loss corresponding to the map as true, and continuously executing the step S108;
s110, starting a lost path retrieving process; increasing find _ loss _ retry count of map;
s111, executing a udevadm trigger command;
s112, judging whether the path is retrieved or not; if yes, jumping to the ending step after executing S115; if not, executing S113;
s113, performing rescan scanning and storing at the rear end;
s114, judging whether the path is retrieved or not; if the information is retrieved, executing S115 and then jumping to the end detection step; otherwise, jumping to the step of ending detection;
s115, recording a log, wherein the path is retrieved through a retrieving process, the path _ loss of the map is reset to be false, and the find _ loss _ retry is 0;
s116, updating total _ paths of the map, and resetting path _ loss and find _ loss _ retry of the map;
and S117, recording a log, namely after the path is found back for the appointed times of trial, the path is still not found back, and the physical link needs to be manually detected and stored, and jumping to the step of ending detection.
To sum up, in the method for managing path loss in a multi-path object map provided in the embodiment of the present application, first, after receiving a preset trigger command, a member variable in a target multi-path object map is obtained, and a number n of sub-paths currently included in the target multi-path object map is determined by traversing sub-paths of the target multi-path object map; if the number n of sub paths currently contained in the target multi-path object map is smaller than the total number total _ paths of initial sub paths contained in the target multi-path object map, and the determined state is that the path is lost currently, acquiring the times map, FIND _ LOSS _ RETRY of automatically retrieving the lost path, and judging whether the times map, FIND _ LOSS _ RETRY of automatically retrieving the lost path reaches a set threshold value MAX _ LOSS _ FIND _ RETRY; and if the number of times of automatically retrieving the lost path, map, FIND _ LOSS _ RETRY reaches a set threshold value, MAX _ LOSS _ FIND _ RETRY, recording a first fault log, and sending the first fault log to the client. According to the scheme, after a preset trigger command is received, whether path loss occurs or not is determined according to the number n of sub paths currently contained in a target multi-path object map and the total number total _ paths of initial sub paths contained in the target multi-path object map; when the times of automatically retrieving the lost path map, FIND _ LOSS _ RETRY does not reach the set threshold MAX _ LOSS _ FIND _ RETRY, starting to execute the automatic retrieving process of the lost path; according to the scheme, the lost sub-paths in the multi-path object map can be effectively found in time, when the target multi-path object map is automatically found back after the path loss phenomenon occurs, the upper limit value of the automatic finding back times is set, and when the upper limit value of the automatic finding back times is reached and the finding back is still not carried out, a first fault log is sent to inform operation and maintenance personnel as soon as possible, so that the effective finding back is carried out.
Fig. 6 is a block diagram of an apparatus for managing path loss in a multipath object map according to an embodiment of the present application, where the apparatus includes at least the following modules:
the obtaining module 61 is configured to obtain a member variable in the target multi-path object map after receiving a preset trigger command, and traverse sub-paths of the target multi-path object map to determine the number n of sub-paths currently included in the target multi-path object map; the member variables comprise the total number of starting sub-paths total _ paths contained in the target multi-path object map;
a determining module 62, configured to, if the current number n is less than a total number of start sub paths total _ paths included in the target multi-path object map, and the determined state is that a path LOSS occurs currently, obtain a time map, FIND _ LOSS _ RETRY of automatically retrieving the lost path, and determine whether the time map, FIND _ LOSS _ RETRY of automatically retrieving the lost path reaches a set threshold MAX _ LOSS _ FIND _ RETRY;
a processing module 63, configured to record a first fault log and send the first fault log to a client if the number of times map, FIND _ LOSS _ RETRY of automatically retrieving a lost path reaches a set threshold MAX _ LOSS _ FIND _ RETRY; and is further configured to perform: and if the times of automatically recovering the lost path map, FIND _ LOSS _ RETRY does not reach the set threshold MAX _ LOSS _ FIND _ RETRY, starting the automatic recovering process of the lost path.
The path loss management device in the multipath object provided in the embodiment of the present application may be used in the path loss management method in the multipath object performed in the above embodiments, and the relevant details refer to the above method embodiments, which have similar implementation principles and technical effects, and are not described herein again.
It should be noted that: the path loss management method in the multipath object provided in the above embodiments and the path loss management apparatus in the multipath object provided in the embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments in detail and are not described herein again.
Fig. 7 is a block diagram of a path loss management apparatus in a multipath object according to an embodiment of the present disclosure, where the path loss management apparatus in the multipath object may be a computing device such as a desktop computer, a notebook computer, a palm top computer, and a cloud server, and the apparatus may include, but is not limited to, a processor and a memory. The apparatus for managing a path loss in a multipath object in this embodiment at least includes a processor and a memory, where the memory stores a computer program, the computer program is executable on the processor, and when the processor executes the computer program, the processor implements the steps in the embodiment of the method for managing a path loss in a multipath object, for example, the steps of the method for managing a path loss in a multipath object shown in any one of fig. 1 to fig. 5. Alternatively, the processor may implement the functions of the respective modules in the path loss management apparatus embodiment in the multipath object when executing the computer program.
Illustratively, the computer program may be partitioned into one or more modules that are stored in the memory and executed by the processor to implement the invention. The one or more modules may be a series of computer program instruction segments capable of performing specific functions, the instruction segments describing the execution process of the computer program in the path loss management apparatus in the multipath object. For example, the computer program may be divided into an acquisition module, a judgment module and a processing module, and the specific functions of each module are as follows:
the acquiring module is used for acquiring member variables in the target multi-path object map after receiving a preset trigger command, and traversing sub-paths of the target multi-path object map to determine the number n of the sub-paths currently contained in the target multi-path object map; the member variables comprise the total number of starting sub-paths total _ paths contained in the target multi-path object map;
the judging module is used for acquiring the times map, FIND _ LOSS _ RETRY of automatically retrieving the lost path if the current number n is smaller than the total number total _ paths of the initial sub-paths contained in the target multi-path object map and the determined state is that the path is lost currently, and judging whether the times map, FIND _ LOSS _ RETRY of automatically retrieving the lost path reaches the set threshold MAX _ LOSS _ FIND _ RETRY;
the processing module is used for recording a first fault log and sending the first fault log to the client if the number of times of automatically retrieving the lost path, map, FIND _ LOSS _ RETRY, reaches a set threshold value MAX _ LOSS _ FIND _ RETRY; and is further configured to perform: and if the times of automatically recovering the lost path map, FIND _ LOSS _ RETRY does not reach the set threshold MAX _ LOSS _ FIND _ RETRY, starting the automatic recovering process of the lost path.
The processor may include one or more processing cores, such as: 4 core processors, 6 core processors, etc. The processor may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor may also include a main processor and a coprocessor, where the main processor is a processor for Processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor may further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning. The processor is a control center of the path loss management device in the multi-path object, and various interfaces and lines are used for connecting all parts of the path loss management device in the whole multi-path object.
The memory may be used to store the computer programs and/or modules, and the processor may implement the various functions of the path loss management apparatus in the multi-path object by running or executing the computer programs and/or modules stored in the memory and calling the data stored in the memory. The memory may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the cellular phone, and the like. In addition, the memory may include high speed random access memory, and may also include non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), at least one magnetic disk storage device, a memory device, or other volatile solid state storage device.
It can be understood by those skilled in the art that the apparatus described in this embodiment is only an example of a path loss management apparatus in a multipath object, and does not form a limitation on the path loss management apparatus in the multipath object, and in other embodiments, more or fewer components may be included, or some components may be combined, or different components may be included, for example, the path loss management apparatus in the multipath object may further include an input/output device, a network access device, a bus, and the like. The processor, memory and peripheral interface may be connected by bus or signal lines. Each peripheral may be connected to the peripheral interface via a bus, signal line, or circuit board. Illustratively, peripheral devices include, but are not limited to: radio frequency circuit, touch display screen, audio circuit, power supply, etc.
Of course, the path loss management apparatus in the multipath object may also include fewer or more components, which is not limited in this embodiment.
Optionally, the present application further provides a computer-readable storage medium, which stores a computer program, and the computer program is used for implementing the steps of the path loss management method in the multipath object when being executed by a processor.
Optionally, the present application further provides a computer product, which includes a computer-readable storage medium, where a program is stored in the computer-readable storage medium, and the program is loaded and executed by a processor to implement the steps of the embodiment of the path loss management method in a multipath object.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method for managing path loss in a multi-path object map is characterized by comprising the following steps:
after receiving a preset trigger command, acquiring member variables in a target multi-path object map, and traversing sub-paths of the target multi-path object map to determine the number n of sub-paths currently contained in the target multi-path object map; the member variables comprise the total number of starting sub-paths total _ paths contained in the target multi-path object map;
if the number n of sub paths currently contained in the target multi-path object map is smaller than the total number total _ paths of the initial sub paths contained in the target multi-path object map, and the determined state is that the path is lost currently, acquiring the times map, FIND _ LOSS _ RETRY of automatically retrieving the lost path, and judging whether the times map, FIND _ LOSS _ RETRY of automatically retrieving the lost path reaches a set threshold value MAX _ LOSS _ FIND _ RETRY;
and if the number of times of automatically retrieving the lost path, map, FIND _ LOSS _ RETRY reaches a set threshold value, MAX _ LOSS _ FIND _ RETRY, recording a first fault log, and sending the first fault log to the client.
2. The method according to claim 1, wherein the member variables further include a path loss flag in the target multipath object map, path _ loss, and the method further comprises:
if the number of times of automatically retrieving the lost path, map, FIND _ LOSS _ RETRY, does not reach the set threshold value, MAX _ LOSS _ FIND _ RETRY:
setting the value of a path loss mark map, path _ loss, in a target multi-path object map as true, and adding 1 to the times of automatically retrieving the lost path map, find _ loss _ retry;
controlling to execute a udevadm trigger command, and determining whether the lost path is found back according to the execution result of the udevadm trigger command;
if the execution result is determined to be 'successful recovery' according to the udevadm trigger command, recording a 'successful recovery' log, setting the value of a path loss mark map, path _ loss to be false, and setting the times of automatically recovering the lost path map, find _ loss _ retry to be zero;
if the execution result is determined to be 'the lost path is not found back' according to the udevadm trigger command, controlling to execute a rescan command to scan the storage node corresponding to the sub-path contained in the target multi-path object map;
if the storage block devices which are lost previously and correspond to the sub paths contained in the target multi-path object map are scanned by executing a rescan command, recording a log of successful recovery, setting the value of a path loss mark map, path _ loss as false, and resetting the times of automatically recovering the lost paths, map, find _ loss _ retry;
and if the storage block devices which are lost previously and correspond to the sub paths contained in the target multi-path object map are not scanned by executing the rescan command, recording a second fault log and sending the second fault log to the client.
3. The method of claim 2, further comprising:
adding a path LOSS mark map in the target multipath object map, a set threshold value MAX _ LOSS _ FIND _ RETRY aiming at the times of automatically retrieving lost paths, and the number N of included sub-paths of the target multipath object map into the target multipath object map;
the initial value of the path LOSS flag map in the target multi-path object map is false, the set threshold MAX _ LOSS _ FIND _ RETRY for automatically retrieving the lost path number is 5, the variable N representing the number of sub-paths included in the target multi-path object map is initially 0, and the updating is performed automatically once every time an effective sub-path is traversed.
4. The method of claim 1 or 2, further comprising:
if the number n of sub paths currently contained in the target multi-path object map is equal to the total number total _ paths of initial sub paths contained in the target multi-path object map, continuously judging whether a path loss flag map, path _ loss, in the target multi-path object map is true;
if the path loss flag map, path _ loss, in the target multi-path object map is true, determining that the target multi-path object map has path loss but the current lost path is successfully retrieved, recording a log of successful retrieval, setting the value of the path loss flag map, path _ loss and resetting the times of automatically retrieving the lost path map, find _ loss _ retry to zero.
5. The method of claim 1 or 2, further comprising:
if the current number n is greater than the total number of the initial sub-paths total _ paths contained in the target multi-path object map, determining that a new path is found currently, adding 1 to the total number of the initial sub-paths total _ paths contained in the target multi-path object map, setting the value of a path loss flag map.
6. The method of claim 1,
the preset trigger command is a check _ path thread starting command, a ue event receiving command or a path adding operation command.
7. The method of claim 1, further comprising:
aiming at a target multipath object map, acquiring a unique identifier of the target multipath object map;
determining the number of sub paths with the same identification as the unique identification of the target multi-path object map;
the number of sub-paths identical to the unique identifier of the target multi-path object map is determined as the total number of start sub-paths total _ paths contained in the target multi-path object map.
8. An apparatus for managing path loss in a multipath object, comprising:
the acquiring module is used for acquiring member variables in the target multi-path object map after receiving a preset trigger command, and traversing sub-paths of the target multi-path object map to determine the number n of the sub-paths currently contained in the target multi-path object map; the member variables comprise the total number of starting sub-paths total _ paths contained in the target multi-path object map;
the judging module is used for acquiring the times map, FIND _ LOSS _ RETRY of automatically retrieving the lost path if the current number n is smaller than the total number total _ paths of the initial sub-paths contained in the target multi-path object map and the determined state is that the path is lost currently, and judging whether the times map, FIND _ LOSS _ RETRY of automatically retrieving the lost path reaches the set threshold MAX _ LOSS _ FIND _ RETRY;
and the processing module is used for recording a first fault log and sending the first fault log to the client if the number of times of automatically retrieving the lost path, map, FIND _ LOSS _ RETRY, reaches a set threshold value, MAX _ LOSS _ FIND _ RETRY.
9. An apparatus for managing path loss in a multi-path object, the apparatus comprising a processor, a memory and a computer program stored in and executable on the memory, wherein the computer program is loaded and executed by the processor to implement a method for managing path loss in a multi-path object as claimed in any one of claims 1 to 7.
10. A computer-readable storage medium storing a computer program for implementing a method for path loss management in a multi-path object as claimed in any one of claims 1 to 7 when the computer program is executed by a processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111614724.1A CN114500575B (en) | 2021-12-27 | 2021-12-27 | Method, device and storage medium for managing path loss in multi-path object map |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111614724.1A CN114500575B (en) | 2021-12-27 | 2021-12-27 | Method, device and storage medium for managing path loss in multi-path object map |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114500575A true CN114500575A (en) | 2022-05-13 |
| CN114500575B CN114500575B (en) | 2024-07-30 |
Family
ID=81496799
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111614724.1A Active CN114500575B (en) | 2021-12-27 | 2021-12-27 | Method, device and storage medium for managing path loss in multi-path object map |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114500575B (en) |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2008158666A (en) * | 2006-12-21 | 2008-07-10 | Nec Corp | Multipath system for storage device, its failure identification method, and program |
| US20150242351A1 (en) * | 2014-02-21 | 2015-08-27 | Fujitsu Limited | Storage system, control apparatus, and computer-readable recording medium having stored therein control program |
| US20150331731A1 (en) * | 2014-05-19 | 2015-11-19 | International Business Machines Corporation | Tracking and factoring application near misses/timeouts into path selection and multipathing status |
| CN105900068A (en) * | 2014-11-24 | 2016-08-24 | 华为技术有限公司 | Path management system, device and method |
| CN106464582A (en) * | 2014-06-27 | 2017-02-22 | 思科技术公司 | Multipath Data Stream Optimization |
| US20180234290A1 (en) * | 2017-02-16 | 2018-08-16 | International Business Machines Corporation | Multipath driver cognitive coordination |
| US20190238446A1 (en) * | 2018-01-31 | 2019-08-01 | International Business Machines Corporation | Distributed storage path configuration |
| CN111901399A (en) * | 2020-07-08 | 2020-11-06 | 苏州浪潮智能科技有限公司 | Cloud platform block equipment exception auditing method, device, equipment and storage medium |
| CN111988169A (en) * | 2020-07-29 | 2020-11-24 | 苏州浪潮智能科技有限公司 | Method, system, equipment and medium for cleaning and repairing abnormal disk of cloud platform |
| US20210099521A1 (en) * | 2019-09-30 | 2021-04-01 | EMC IP Holding Company LLC | Host device with multi-path layer configured for detecting target failure status and updating path availability |
| US20210119930A1 (en) * | 2019-10-31 | 2021-04-22 | Intel Corporation | Reliable transport architecture |
| CN113300953A (en) * | 2021-07-27 | 2021-08-24 | 苏州浪潮智能科技有限公司 | Management method, system and related device for multipath failover group |
| US20210377174A1 (en) * | 2020-06-02 | 2021-12-02 | Cisco Technology, Inc. | Path count management |
-
2021
- 2021-12-27 CN CN202111614724.1A patent/CN114500575B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2008158666A (en) * | 2006-12-21 | 2008-07-10 | Nec Corp | Multipath system for storage device, its failure identification method, and program |
| US20150242351A1 (en) * | 2014-02-21 | 2015-08-27 | Fujitsu Limited | Storage system, control apparatus, and computer-readable recording medium having stored therein control program |
| US20150331731A1 (en) * | 2014-05-19 | 2015-11-19 | International Business Machines Corporation | Tracking and factoring application near misses/timeouts into path selection and multipathing status |
| CN106464582A (en) * | 2014-06-27 | 2017-02-22 | 思科技术公司 | Multipath Data Stream Optimization |
| CN105900068A (en) * | 2014-11-24 | 2016-08-24 | 华为技术有限公司 | Path management system, device and method |
| US20180234290A1 (en) * | 2017-02-16 | 2018-08-16 | International Business Machines Corporation | Multipath driver cognitive coordination |
| US20190238446A1 (en) * | 2018-01-31 | 2019-08-01 | International Business Machines Corporation | Distributed storage path configuration |
| US20210099521A1 (en) * | 2019-09-30 | 2021-04-01 | EMC IP Holding Company LLC | Host device with multi-path layer configured for detecting target failure status and updating path availability |
| US20210119930A1 (en) * | 2019-10-31 | 2021-04-22 | Intel Corporation | Reliable transport architecture |
| US20210377174A1 (en) * | 2020-06-02 | 2021-12-02 | Cisco Technology, Inc. | Path count management |
| CN111901399A (en) * | 2020-07-08 | 2020-11-06 | 苏州浪潮智能科技有限公司 | Cloud platform block equipment exception auditing method, device, equipment and storage medium |
| CN111988169A (en) * | 2020-07-29 | 2020-11-24 | 苏州浪潮智能科技有限公司 | Method, system, equipment and medium for cleaning and repairing abnormal disk of cloud platform |
| CN113300953A (en) * | 2021-07-27 | 2021-08-24 | 苏州浪潮智能科技有限公司 | Management method, system and related device for multipath failover group |
Non-Patent Citations (4)
| Title |
|---|
| 余丹丹: "多径TCP路径管理机制研究及优化", 《中国优秀硕士学位论文全文数据库(电子期刊) 信息科技辑》, 15 November 2020 (2020-11-15) * |
| 周竞文: "面向用户请求路径的分布式系统监控关键技术研究", 《中国博士学位论文全文数据库(电子期刊) 信息科技辑》, 15 December 2017 (2017-12-15) * |
| 范长军;胡志成;杨佳东;: "基于ALUA的多路径存储系统", 计算机系统应用, no. 10, 15 October 2017 (2017-10-15) * |
| 陈适;白骏烈;: "存储虚拟化在教育信息化中的应用", 中国信息技术教育, no. 06, 23 March 2014 (2014-03-23) * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114500575B (en) | 2024-07-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20170091013A1 (en) | Pcie error reporting and throttling | |
| CN107783829B (en) | Task processing method and device, storage medium and computer equipment | |
| CN111885005B (en) | Container cloud platform service communication method, device, equipment and medium | |
| CN106775981B (en) | Process processing method and device and computer readable medium | |
| CN113656168A (en) | Method, system, medium and equipment for automatic disaster recovery and scheduling of traffic | |
| CN113625945A (en) | Distributed storage slow disk processing method, system, terminal and storage medium | |
| CN111988169B (en) | Method, system, equipment and medium for cleaning and repairing abnormal disk of cloud platform | |
| US10136279B2 (en) | Terminal peripheral management method and M2M gateway | |
| CN111342986B (en) | Distributed node management method and device, distributed system and storage medium | |
| CN115878052A (en) | RAID array inspection method, inspection device and electronic equipment | |
| US11226857B1 (en) | Device, method and computer program product for fault elimination of a multilayer system | |
| CN116909494B (en) | Storage switching method and device of server and server system | |
| CN110011854A (en) | MDS fault handling method, device, storage system and computer readable storage medium | |
| US20230359514A1 (en) | Operation-based event suppression | |
| WO2024113534A1 (en) | Method and apparatus for controlling storage resources in storage node, and storage node | |
| CN114500575B (en) | Method, device and storage medium for managing path loss in multi-path object map | |
| CN107526690B (en) | Method and device for clearing cache | |
| EP4354297A1 (en) | Data integrity processing method and apparatus, and electronic device | |
| CN107885575B (en) | Virtual machine migration method and device | |
| CN110968456A (en) | Method and device for processing fault disk in distributed storage system | |
| CN109101253B (en) | Management method and device for host in cloud computing system | |
| CN113656378A (en) | Server management method, device and medium | |
| CN110837431A (en) | Service control method, service control device, computer equipment and computer-readable storage medium | |
| CN117032881B (en) | Method, device and storage medium for detecting and recovering abnormality of virtual machine | |
| US20230015941A1 (en) | Data migration method and apparatus for database |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |