A method, device, equipment and medium for improving system reliability

Abstract

The present invention relates to the field of communications, and provides a method, device, equipment and medium for improving system reliability. The method includes: obtaining theoretical traffic data corresponding to a backend topology module under different front-end service models; obtaining a current front-end service model and actual traffic data of the backend topology module under the current front-end service model; in response to detecting an abnormal change in the backend topology module and / or a ratio of the theoretical traffic data to the actual traffic data being greater than a preset ratio in a high-reliability mode, adjusting the actual traffic data to be less than the theoretical traffic data. The method disclosed in the present invention can ensure that the backend array can always provide services for the front-end service through multiple strategies in a high-reliability scenario, improving the reliability of the entire machine system.

Description

Technical Field

[0001] The present invention relates to the field of communications, and in particular, to a method, device, equipment and medium for improving system reliability. Background Art

[0002] Currently, array storage, especially high-end array storage, generally uses QoS (Quality of Service) technology for traffic control. For example, there are QoS rules for hosts or host groups at the front-end service level, and QoS rules for volumes or volume groups at the storage level. In the prior art, most QoS rules perform single IOPS (Input / Output Operations Per Second) or bandwidth limitation, and do not perform corresponding policy adjustments for topological changes in the storage backend array. In some scenarios where the topology of a data link is abnormal and traffic surges occur on other data links, if the front-end service pressure increases at this time, it is easy to cause abnormal management information of the backend array or an IO drop to zero at the service level, thereby affecting the reliability of the entire machine system. Summary of the Invention

[0003] In view of this, the present invention provides a method, device, equipment and medium for improving system reliability. Among them, the method for improving system reliability proposed by the present invention monitors the working states of the backend main control module, the backend expansion module, and the disk array module in real time through a backend topology traffic management module (BTT management module), and optimizes the traffic management measures of the entire machine in the case of abnormal backend topology, especially in the high-reliability mode, ensuring that the backend array can always provide services for the front-end service through multiple strategies, thereby improving the reliability of the entire machine system.

[0004] Based on the above purpose, an aspect of an embodiment of the present invention provides a method for improving system reliability, the method comprising the following steps: obtaining theoretical traffic data corresponding to a backend topology module under different front-end service models; obtaining the current front-end service model and the actual traffic data of the backend topology module under the current front-end service model; in response to detecting an abnormal change in the backend topology module and / or a ratio of the theoretical traffic data to the actual traffic data being greater than a preset ratio in the high-reliability mode, adjusting the actual traffic data to be less than the theoretical traffic data.

[0005] In some embodiments, the method further comprises: in response to detecting an abnormal change in the backend topology module in the normal mode, determining the magnitude of the actual traffic data and the theoretical traffic data of a first expected ratio, and the scenario in which the abnormal change occurs, and adjusting the actual traffic data to a corresponding traffic range according to different determination results.

[0006] In some embodiments, the adjusting the actual traffic data to a corresponding traffic range according to different judgment results by judging the magnitude of the actual traffic data and the theoretical traffic data of the first expected ratio and the scenario where the abnormal change occurs in response to detecting an abnormal change in the backend topology module in the normal mode includes: in response to detecting an abnormal change in the backend topology module in the normal mode, when the actual traffic data is not less than the theoretical traffic data of the first expected ratio and the abnormal change occurs in the physical scenario, adjusting the actual traffic data to be less than the theoretical traffic data.

[0007] In some embodiments, the adjusting the actual traffic data to a corresponding traffic range according to different judgment results by judging the magnitude of the actual traffic data and the theoretical traffic data of the first expected ratio and the scenario where the abnormal change occurs in response to detecting an abnormal change in the backend topology module in the normal mode further includes: in response to detecting an abnormal change in the backend topology module in the normal mode, when the actual traffic data is not less than the theoretical traffic data of the first expected ratio and the abnormal change occurs in the service scenario, adjusting the actual traffic data to be less than the expected value corresponding to the theoretical traffic data.

[0008] In some embodiments, the adjusting the actual traffic data to be less than the theoretical traffic data in response to detecting an abnormal change in the backend topology module and / or the ratio of the theoretical traffic data to the actual traffic data being greater than a preset ratio in the high-reliability mode includes: in response to detecting an abnormal change in the backend topology module in the high-reliability mode and the actual traffic data is not less than the theoretical traffic data of the second expected ratio, adjusting the actual traffic data to be less than the theoretical traffic data; in response to the ratio of the theoretical traffic data to the actual traffic data being greater than the preset ratio and the actual traffic data is not less than the theoretical traffic data in the high-reliability mode, adjusting the actual traffic data to be less than the theoretical traffic data.

[0009] In some embodiments, the adjusting the actual traffic data to be less than the theoretical traffic data in response to detecting an abnormal change in the backend topology module and / or the ratio of the theoretical traffic data to the actual traffic data being greater than a preset ratio in the high-reliability mode further includes: in response to the ratio of the theoretical traffic data to the actual traffic data being greater than the preset ratio and the actual traffic data being less than the theoretical traffic data in the high-reliability mode, reporting a warning about the cluster performance.

[0010] In some embodiments, obtaining the theoretical traffic data corresponding to the backend topology modules under different front-end service models includes: establishing a backend topology traffic management module and embedding the theoretical traffic data corresponding to the backend topology modules under different front-end service models into the backend topology traffic management module to obtain the theoretical traffic data corresponding to the backend topology modules under different front-end service models.

[0011] Another aspect of the embodiments of the present invention further provides a device for improving system reliability. The device includes: a first module configured to obtain the theoretical traffic data corresponding to the backend topology modules under different front-end service models; a second module configured to obtain the current front-end service model and the actual traffic data of the backend topology modules under the current front-end service model; and a third module configured to, in response to detecting an abnormal change in the backend topology module and / or the ratio of the theoretical traffic data to the actual traffic data being greater than a preset ratio in the high-reliability mode, adjust the actual traffic data of the backend topology module to be less than the theoretical traffic data.

[0012] Another aspect of the embodiments of the present invention further provides a computer device, including at least one processor; and a memory storing computer instructions that can be run on the processor. When the instructions are executed by the processor, the steps of any of the above methods are implemented.

[0013] Another aspect of the embodiments of the present invention further provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of any of the above methods.

[0014] The present invention has at least the following beneficial effects: The present invention proposes a method, device, equipment, and medium for improving system reliability. The method for improving system reliability proposed by the present invention optimizes the management measures of the overall machine traffic in the abnormal scenario of the backend topology. Especially in the high-reliability scenario, various strategies are used to ensure that the backend array can always provide services for the front-end services, improving the reliability of the overall machine system. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the following drawings are only some embodiments of the present invention. For those of ordinary skill in the art, other embodiments can be obtained based on these drawings without creative efforts.

[0016] Figure 1 Schematic diagram of an embodiment of a method for improving system reliability provided by the present invention;

[0017] Figure 2Schematic diagram of the backend topology of the system provided by the present invention;

[0018] Figure 3 Schematic diagram of an embodiment of a device for improving system reliability provided by the present invention;

[0019] Figure 4 Schematic diagram of an embodiment of a computer device provided by the present invention;

[0020] Figure 5 Schematic diagram of an embodiment of a computer-readable storage medium provided by the present invention. Detailed implementation manners

[0021] The following describes embodiments of the present invention. However, it should be understood that the disclosed embodiments are merely examples, and other embodiments may take various alternative forms.

[0022] In addition, it should be noted that all the expressions using "first" and "second" in the embodiments of the present invention are used to distinguish two entities or parameters with the same name but different, so it can be seen that "first" and "second" are only for the convenience of expression and should not be construed as a limitation on the embodiments of the present invention. This will not be repeated in the subsequent embodiments. The terms "comprising", "including" or any other deformation thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements not only includes those elements, but may also include elements not explicitly listed or inherent to these processes, methods, articles or devices.

[0023] The following will describe one or more embodiments of the present application with reference to the accompanying drawings.

[0024] Based on the above purposes, in the first aspect of the embodiments of the present invention, an embodiment of a method for improving system reliability is proposed. Figure 1 Shown is a schematic diagram of an embodiment of a method for improving system reliability provided by the present invention. As Figure 1 shown, an embodiment of a method for improving system reliability in the embodiments of the present invention includes the following steps:

[0025] S1. Obtain the theoretical traffic data corresponding to the backend topology module under different front-end service models;

[0026] S2. Obtain the current front-end service model and the actual traffic data of the backend topology module under the current front-end service model;

[0027] S3. In response to detecting an abnormal change in the backend topology module and / or the ratio of the theoretical traffic data to the actual traffic data being greater than a preset ratio in the high-reliability mode, adjust the actual traffic data to be less than the theoretical traffic data.

[0028] For the above purposes, in the first aspect of the embodiments of the present invention, another embodiment of a method for improving system reliability is further proposed. An embodiment of a method for improving system reliability according to the embodiments of the present invention includes the following steps: By setting up a backend topology traffic management module (BTT management module) as shown in Figure 2 to monitor in real time the theoretical traffic data corresponding to the backend topology module under different front-end service models. The BTT management module is located on the board and mainly uses programmable logic devices such as ARM. In this embodiment, the backend topology module includes a backend main control module, a backend expansion module, and a disk array module. Among them, the backend main control module is located on the board and is generally a control chip or an external plug-in IO card, etc., according to the different disk array modules; the backend expansion module is located on the board and is generally an expansion chip or an external plug-in IO card, etc., according to the different disk array modules; the disk array module is responsible for the final data storage of the storage system, and is generally a dual-port hard disk or SSD (Solid State Disk or Solid State Drive) with interfaces such as SAS (Serial Attached SCSI) or NVME (Non-Volatile Memory Express). In addition, there is an indication module located on the board, which is directly controlled by the serial port module and externally indicates the real-time state of the current BTT management module; the wireless module can convert the serial port module signal into wireless signals such as WIFI, so that the outside world can interact with the BTT management module without a physical serial cable; the serial port module can perform information interaction between the outside world and the BTT management module, parameter presetting, and enabling of related functions. Specifically, the theoretical traffic data A of the comprehensive topology of the backend main control module, the backend expansion module, and the disk array module under different front-end service models (such as large and small data blocks, random / sequential, read / write, etc., and at the same time including classic data models such as OLAP / OLTP) (for example, the theoretical traffic data of a SAS controller of specification D1 from manufacturer C1, a SAS expander of specification D2 from manufacturer C2, and an SSD of specification D3 from manufacturer C3 under OLTP) is embedded in the backend topology traffic management module, and at the same time, the actual traffic data B corresponding to the comprehensive topology of the backend main control module, the backend expansion module, and the disk array module under different front-end service models is obtained through the backend topology traffic management module. The backend topology traffic management module communicates with the CPU module to obtain the front-end service model, and the backend topology traffic management module monitors in real time abnormal scenario situations such as topology changes of the backend main control module, the backend expansion module, and the disk array module, and distinguishes whether the topology change belongs to a physical operation or a service failure (the backend topology traffic management module generally uses physical information such as the presence signals of these backend modules to make judgments on physical operations, etc. If the BTT cannot make a distinction, all abnormal scenarios will be classified as service failures).

[0029] In normal mode, only when the back-end topology traffic management module detects a change in the back-end topology, the data comparison between A and B is performed at this time. When B >= M * A and the abnormal scenario is a physical operation, the traffic on this link is controlled below A through the back-end topology traffic management module; if B >= M * A and the abnormal scenario is a service failure, the traffic on this link is controlled below M * A through the back-end topology traffic management module. In high-reliability mode, when the back-end topology traffic management module detects a change in the back-end topology, the data comparison between A and B is performed at this time. If B >= N * A, regardless of whether the abnormal scenario is a physical operation or a service failure, the traffic on this link is controlled below A through the back-end topology traffic management module; if the difference between A and B in high-reliability mode is greater than C, the data comparison between A and B will be performed regardless of whether the back-end topology traffic management module detects a change in the back-end topology. If B >= A, the traffic on this link is controlled below A through the back-end topology traffic management module; if B < A, a cluster performance alarm is reported. Among them, A, C, M, and N are all system preset parameters, which can be adjusted through methods such as the system or the serial port module. The BTT management module monitors the working status of the back-end main control module, the back-end expansion module, and the disk array module in real time, optimizes the overall machine traffic management measures in the case of back-end topology anomalies, especially in high-reliability mode, and ensures that the back-end array can always provide services for the front-end services through multiple strategies, thereby ensuring the reliability of the overall machine system.

[0030] For the above purposes, in the first aspect of the embodiments of the present invention, another embodiment of a method for improving system reliability is also proposed. In this embodiment, by setting up a Back-end Topology Traffic Management Module (BTT Management Module) to monitor in real time the theoretical traffic data corresponding to the back-end topology module under different front-end service models. The BTT Management Module is located on the board and mainly uses programmable logic devices such as ARM. In this embodiment, the back-end topology module includes a back-end main control module, a back-end expansion module, and a disk array module. Among them, the back-end main control module is located on the board and generally controls chips or external IO cards according to different disk array modules; the back-end expansion module is located on the board and is generally an expansion chip or an external IO card according to different disk array modules; the disk array module is responsible for the final data storage of the storage system, generally a dual-port hard disk or SSD (Solid State Disk or Solid State Drive) with interfaces such as SAS (Serial Attached SCSI) or NVME (Non-Volatile Memory Express). In addition, there is an indication module located on the board, directly controlled by the serial port module, which externally indicates the real-time state of the current BTT Management Module; the wireless module can convert the serial port module signal into wireless signals such as WIFI, so that the outside world can interact with the BTT Management Module without a physical serial cable; the serial port module can perform information interaction between the outside world and the BTT Management Module, parameter presetting, and enabling of related functions. Specifically, the theoretical traffic data A of the comprehensive topology of the back-end main control module, the back-end expansion module, and the disk array module under different front-end service models (such as large and small data blocks, random / sequential, read / write, etc., and at the same time including classic data models such as OLAP / OLTP) (for example, the theoretical traffic data of a SAS controller of specification D1 from manufacturer C1, a SAS expander of specification D2 from manufacturer C2, and an SSD of specification D3 from manufacturer C3 under OLTP) is embedded in the back-end topology traffic management module. At the same time, the actual traffic data B corresponding to the comprehensive topology of the back-end main control module, the back-end expansion module, and the disk array module under different front-end service models is obtained through the back-end topology traffic management module. The front-end service model is obtained by the back-end topology traffic management module communicating with the CPU module. The back-end topology traffic management module monitors in real time abnormal scenario situations such as topology changes of the back-end main control module, the back-end expansion module, and the disk array module, and distinguishes whether the topology change belongs to a physical operation or a service failure (the back-end topology traffic management module generally uses physical information such as the presence signals of these back-end modules to make judgments on physical operations, etc. If the BTT cannot make a distinction, it will uniformly classify the abnormal scenario as a service failure).

[0031] In the normal mode, only when the back-end topology traffic management module detects a change in the back-end topology, the data of A and B are compared at this time. When B >= 1.25 * A and the abnormal scenario is a physical operation, the traffic under this link is controlled below A through the back-end topology traffic management module; if B >= 1.25 * A and the abnormal scenario is a service failure, the traffic under this link is controlled below 1.25 * A through the back-end topology traffic management module. In the high-reliability mode, when the back-end topology traffic management module detects a change in the back-end topology, the data of A and B are compared at this time. If B >= 1.15 * A, regardless of whether the abnormal scenario is a physical operation or a service failure, the traffic under this link is controlled below A through the back-end topology traffic management module; if the difference between A and B in the high-reliability mode is greater than 20%, the data of A and B are compared regardless of whether the back-end topology traffic management module detects a change in the back-end topology. If B >= A, the traffic under this link is controlled below A through the back-end topology traffic management module; if B < A, a cluster performance warning is reported. The system preset parameters can be adjusted through the system or the serial port module, etc. The BTT management module monitors the working status of the back-end main control module, the back-end expansion module, and the disk array module in real time, and optimizes the whole-machine traffic management measures in the case of back-end topology anomalies. Especially in the high-reliability mode, various strategies are used to ensure that the back-end array can always provide services for the front-end services, thereby ensuring the reliability of the whole-machine system.

[0032] In the second aspect of the embodiments of the present invention, a device for improving system reliability is proposed. Figure 3 The following shows a schematic diagram of an embodiment of a device for improving system reliability provided by the present invention. As Figure 3 shown, a device for improving system reliability provided by the present invention includes: a first module 011 configured to obtain theoretical traffic data corresponding to the back-end topology module under different front-end service models; a second module 012 configured to obtain the current front-end service model and the actual traffic data of the back-end topology module under the current front-end service model; a third module 013 configured to, in response to detecting an abnormal change in the back-end topology module and / or the ratio of the theoretical traffic data to the actual traffic data being greater than a preset ratio in the high-reliability mode, adjust the actual traffic data of the back-end topology module to be less than the theoretical traffic data.

[0033] For the above purpose, in the third aspect of the embodiments of the present invention, a computer device is proposed. Figure 4 The following shows a schematic diagram of an embodiment of a computer device provided by the present invention. As Figure 4As shown in the figure, an embodiment of a computer device provided by the present invention includes the following modules: at least one processor 021; and a memory 022, where the memory 022 stores computer instructions 023 that can run on the processor 021, and when the computer instructions 023 are executed by the processor 021, the steps of the method described above are implemented.

[0034] The present invention also provides a computer-readable storage medium. Figure 5 The figure shows a schematic diagram of an embodiment of a computer-readable storage medium provided by the present invention. As Figure 5 shown, the computer-readable storage medium 031 stores a computer program 032 that, when executed by a processor, executes the above method. The method executed by the computer program 032 includes: obtaining theoretical traffic data corresponding to a backend topology module under different front-end service models; obtaining the current front-end service model and the actual traffic data of the backend topology module under the current front-end service model; and in response to detecting an abnormal change in the backend topology module and / or the ratio of the theoretical traffic data to the actual traffic data being greater than a preset ratio in the high-reliability mode, adjusting the actual traffic data to be less than the theoretical traffic data.

[0035] In some embodiments, the method further includes: in response to detecting an abnormal change in the backend topology module in the normal mode, determining the magnitude of the actual traffic data and the theoretical traffic data of the first expected ratio and the scenario in which the abnormal change occurs, and adjusting the actual traffic data to a corresponding traffic range according to different determination results.

[0036] In some embodiments, the step of in response to detecting an abnormal change in the backend topology module in the normal mode, determining the magnitude of the actual traffic data and the theoretical traffic data of the first expected ratio and the scenario in which the abnormal change occurs, and adjusting the actual traffic data to a corresponding traffic range includes: in response to detecting an abnormal change in the backend topology module in the normal mode, when the actual traffic data is not less than the theoretical traffic data of the first expected ratio and the abnormal change occurs in the physical scenario, adjusting the actual traffic data to be less than the theoretical traffic data.

[0037] In some embodiments, the step of in response to detecting an abnormal change in the backend topology module in the normal mode, determining the magnitude of the actual traffic data and the theoretical traffic data of the first expected ratio and the scenario in which the abnormal change occurs, and adjusting the actual traffic data to a corresponding traffic range further includes: in response to detecting an abnormal change in the backend topology module in the normal mode, when the actual traffic data is not less than the theoretical traffic data of the first expected ratio and the abnormal change occurs in the service scenario, adjusting the actual traffic data to be less than the expected value corresponding to the theoretical traffic data.

[0038] In some embodiments, in response to monitoring an abnormal change in the back-end topology module in the high reliability mode and / or the ratio of the theoretical flow data to the actual flow data is greater than a preset ratio, adjusting the actual flow data to be less than the theoretical flow data includes: in response to monitoring an abnormal change in the back-end topology module in the high reliability mode and the actual flow data is not less than the theoretical flow data of a second expected ratio, adjusting the actual flow data to be less than the theoretical flow data; in response to monitoring in the high reliability mode that the ratio of the theoretical flow data to the actual flow data is greater than a preset ratio and the actual flow data is not less than the theoretical flow data, adjusting the actual flow data to be less than the theoretical flow data.

[0039] In some embodiments, in response to monitoring abnormal changes in the back-end topology module in the high reliability mode and / or the ratio of the theoretical traffic data to the actual traffic data is greater than a preset ratio, adjusting the actual traffic data to be less than the theoretical traffic data also includes: in response to monitoring in the high reliability mode that the ratio of the theoretical traffic data to the actual traffic data is greater than a preset ratio and the actual traffic data is less than the theoretical traffic data, reporting a cluster performance warning.

[0040] In some embodiments, obtaining the theoretical traffic data corresponding to the back-end topology module under different front-end business models includes: establishing a back-end topology traffic management module and embedding the theoretical traffic data corresponding to the back-end topology module under different front-end business models into the back-end topology traffic management module to obtain the theoretical traffic data corresponding to the back-end topology module under different front-end business models.

[0041] Finally, it should be noted that those skilled in the art will understand that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The program for setting the system parameters can be stored in a computer-readable storage medium. When the program is executed, it can include the processes of the embodiments of the above-mentioned methods. The storage medium of the program can be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM). The above-mentioned computer program embodiments can achieve the same or similar effects as any of the corresponding aforementioned method embodiments.

[0042] In addition, the method disclosed in the embodiment of the present invention can also be implemented as a computer program executed by a processor, and the computer program can be stored in a computer-readable storage medium. When the computer program is executed by the processor, the above functions defined in the method disclosed in the embodiment of the present invention are performed.

[0043] In addition, the above method steps and system units can also be implemented by a controller and a computer-readable storage medium for storing a computer program that enables the controller to implement the above steps or unit functions.

[0044] Those skilled in the art will also understand that the various exemplary logic blocks, modules, circuits, and algorithm steps described in connection with the disclosure herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability of hardware and software, a general description of the functions of various illustrative components, blocks, modules, circuits, and steps has been given. Whether this function is implemented as software or hardware depends on the specific application and the design constraints imposed on the overall system. The functions that can be implemented by those skilled in the art in various ways for each specific application, but such implementation decisions should not be construed as causing a departure from the scope of the disclosure of the embodiments of the present invention.

[0045] In one or more exemplary designs, the functions can be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions can be stored on or transmitted through a computer-readable medium as one or more instructions or code. Computer-readable media includes computer storage media and communication media, and the communication media includes any medium that helps to transfer a computer program from one location to another. The storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example and not limitation, the computer-readable medium can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store the required program code in the form of instructions or data structures and can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. In addition, any connection can be properly termed a computer-readable medium. For example, if coaxial cables, fiber optic cables, twisted pairs, digital subscriber lines (DSL), or wireless technologies such as infrared, radio, and microwave are used to send software from a website, server, or other remote source, then the above coaxial cables, fiber optic cables, twisted pairs, DSL, or wireless technologies such as infrared, radio, and microwave are all included in the definition of the medium. As used herein, disk and optical disk include compact disk (CD), laser disk, optical disk, digital versatile disk (DVD), floppy disk, Blu-ray disk, where disks typically reproduce data magnetically, while optical disks reproduce data optically using a laser. Combinations of the above should also be included within the scope of computer-readable media.

[0046] The foregoing are exemplary embodiments disclosed by the present invention. However, it should be noted that various changes and modifications can be made without departing from the scope of the embodiments disclosed by the present invention as defined by the claims. The functions, steps, and / or actions of the method claims according to the disclosed embodiments herein need not be performed in any particular order. In addition, although the elements disclosed by the embodiments of the present invention may be described or claimed in individual form, they can also be understood as plural unless explicitly limited to the singular form.

[0047] It should be understood that, as used herein, unless the context clearly supports an exception, the singular form "a" is also intended to include the plural form. It should also be understood that the "and / or" used herein refers to any and all possible combinations of one or more of the associated listed items.

[0048] The serial numbers of the disclosed embodiments of the present invention above are only for description and do not represent the superiority or inferiority of the embodiments.

[0049] Those of ordinary skill in the art can understand that all or part of the steps to implement the above embodiments can be completed by hardware, or can be completed by instructing relevant hardware through a program. The program can be stored in a computer-readable storage medium. The above-mentioned storage medium can be a read-only memory, a disk, an optical disc, or the like.

[0050] Those of ordinary skill in the art should understand that the discussion of any of the above embodiments is only exemplary and is not intended to imply that the scope of the disclosure of the embodiments of the present invention (including the claims) is limited to these examples; under the concept of the embodiments of the present invention, the technical features between the above embodiments or different embodiments can also be combined, and there are many other variations in different aspects of the embodiments of the present invention as above, which are not provided in detail for the sake of brevity. Therefore, any omission, modification, equivalent replacement, improvement, etc. made within the spirit and principle of the embodiments of the present invention shall be included within the protection scope of the embodiments of the present invention.

Claims

1. A method for improving system reliability, characterized in that, Including: Obtaining theoretical traffic data corresponding to backend topology modules under different front-end business models, which includes: Establishing a backend topology traffic management module and embedding the theoretical traffic data corresponding to the backend topology modules under different front-end business models into the backend topology traffic management module to obtain the theoretical traffic data corresponding to the backend topology modules under different front-end business models; Obtaining the current front-end business model and the actual traffic data of the backend topology module under the current front-end business model; In response to detecting an abnormal change in the backend topology module and / or the ratio of the theoretical traffic data to the actual traffic data being greater than a preset ratio in the high-reliability mode, adjusting the actual traffic data to be less than the theoretical traffic data.

2. The method according to claim 1, characterized in that, The method further includes: In response to detecting an abnormal change in the backend topology module in the normal mode, judging the size of the actual traffic data and the theoretical traffic data at a first expected ratio, and the scenario where the abnormal change occurs, and adjusting the actual traffic data to a corresponding traffic range according to different judgment results.

3. The method according to claim 2, wherein The step of, in response to detecting an abnormal change in the backend topology module in the normal mode, judging the size of the actual traffic data and the theoretical traffic data at a first expected ratio, and the scenario where the abnormal change occurs, and adjusting the actual traffic data to a corresponding traffic range includes: In response to detecting an abnormal change in the backend topology module in the normal mode, if the actual traffic data is not less than the theoretical traffic data at a first expected ratio and the abnormal change occurs in a physical scenario, adjusting the actual traffic data to be less than the theoretical traffic data.

4. The method according to claim 3, wherein The step of, in response to detecting an abnormal change in the backend topology module in the normal mode, judging the size of the actual traffic data and the theoretical traffic data at a first expected ratio, and the scenario where the abnormal change occurs, and adjusting the actual traffic data to a corresponding traffic range further includes: In response to detecting an abnormal change in the backend topology module in the normal mode, if the actual traffic data is not less than the theoretical traffic data at a first expected ratio and the abnormal change occurs in a business scenario, adjusting the actual traffic data to be less than the expected value corresponding to the theoretical traffic data.

5. The method according to claim 1, wherein The step of, in response to detecting an abnormal change in the backend topology module and / or the ratio of the theoretical traffic data to the actual traffic data being greater than a preset ratio in the high-reliability mode, adjusting the actual traffic data to be less than the theoretical traffic data includes: In response to detecting an abnormal change in the backend topology module in the high-reliability mode and the actual traffic data being not less than the theoretical traffic data at a second expected ratio, adjusting the actual traffic data to be less than the theoretical traffic data; In response to detecting that the ratio of the theoretical traffic data to the actual traffic data is greater than a preset ratio and the actual traffic data is not less than the theoretical traffic data in the high-reliability mode, adjusting the actual traffic data to be less than the theoretical traffic data.

6. The method according to claim 5, wherein The step of adjusting the actual traffic data to be less than the theoretical traffic data in response to detecting an abnormal change in the backend topology module and / or a ratio of the theoretical traffic data to the actual traffic data being greater than a preset ratio in the high-reliability mode further includes: In response to detecting that the ratio of the theoretical traffic data to the actual traffic data is greater than the preset ratio and the actual traffic data is less than the theoretical traffic data in the high-reliability mode, reporting a warning about the cluster performance.

7. A device for improving system reliability, characterized in that It includes: A first module configured to obtain theoretical traffic data corresponding to the backend topology module under different front-end service models; A second module configured to obtain the current front-end service model and the actual traffic data of the backend topology module under the current front-end service model; A third module configured to adjust the actual traffic data of the backend topology module to be less than the theoretical traffic data in response to detecting an abnormal change in the backend topology module and / or a ratio of the theoretical traffic data to the actual traffic data being greater than a preset ratio in the high-reliability mode; The first module is used to: establish a backend topology traffic management module and embed the theoretical traffic data corresponding to the backend topology module under different front-end service models into the backend topology traffic management module to obtain the theoretical traffic data corresponding to the backend topology module under different front-end service models.

8. A computer device, characterized in that, It includes: At least one processor; And A memory storing computer instructions executable on the processor, and when the instructions are executed by the processor, the steps of the method according to any one of claims 1-6 are implemented.

9. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, the steps of the method according to any one of claims 1-6 are implemented.

Images