CN111552637A - Database state detection method and device, electronic equipment and storage medium thereof - Google Patents
Database state detection method and device, electronic equipment and storage medium thereof Download PDFInfo
- Publication number
- CN111552637A CN111552637A CN202010310910.5A CN202010310910A CN111552637A CN 111552637 A CN111552637 A CN 111552637A CN 202010310910 A CN202010310910 A CN 202010310910A CN 111552637 A CN111552637 A CN 111552637A
- Authority
- CN
- China
- Prior art keywords
- state
- check
- database
- verification
- states
- 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3604—Software analysis for verifying properties of programs
- G06F11/3608—Software analysis for verifying properties of programs using formal methods, e.g. model checking, abstract interpretation
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application provides a method and a device for detecting database states, electronic equipment and a storage medium thereof, wherein the method is applied to an application server, the application server is correspondingly connected with a master database and at least one slave database, and the method comprises the following steps: acquiring the running state of the middleware in the application server; when the operating state of the middleware is the starting state, a plurality of verification routines of a checking database are created in the middleware; and determining the state of the main database according to the plurality of check routines. According to the method and the device, the states of the databases are detected by establishing a plurality of check coroutines through the middleware, whether the main database breaks down or not is judged, the states of the main database are comprehensively judged through the states of the check coroutines, the database is not judged to be abnormal because a single check coroutine is abnormal, the main database is prevented from being misjudged to be a fault database, the fault database is prevented from being mistakenly switched, and the fault detection precision is improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for detecting a database state, an electronic device, and a storage medium thereof.
Background
Currently, with the rapid development of IOE (IBM, ORACLE, EMC) movement, more and more internet enterprises use the MySQL database as a background database. The construction of a high-availability server based on MySQL (MySQL is a relational database management System) and NFS (network File System) is very mature, a high-availability scheme requires that a database is reliable and the database is available, the database is reliable, the data cannot be lost and the like, the database is available, and the service is available, the server cannot be down and the like.
Existing High availability schemes are generally implemented by High availability tools, such as MHA (master High availability) and the editor software, which consists of two parts, MHA Manager and MHA Node. The MHA Manager can be deployed on an independent machine to manage a plurality of master library-slave library clusters, or can be deployed on a slave library node. The MHA nodes operate on each MySQL server, the MHA Manager can detect the master library nodes in the cluster at regular time, when the master library fails, the fault switching is automatically executed, namely the slave library of the latest data is promoted to a new master library, and then all other slave libraries are redirected to the new master library. And the Orchester is that the nodes are periodically connected or disconnected with the MySQL master library, if the master library is not connected, the slave library is connected, the read-write thread between the master library and the slave library is checked in the slave library, and if the read-write thread of the slave library also shows abnormity, the fault of the master library is judged.
The two high-availability schemes have the problem of low precision caused by single-point detection, and the MHA only performs single-point detection on one node of the main library node, so that misjudgment is easily caused, and the timeliness is low; the detection mechanism of the Orchester may cause that when the Orchester main library node detects a problem and simultaneously tamps from the library, the Orchester can not acquire the state of the read-write thread and can misjudge the database fault. At present, the two high-availability schemes both cause the problem that the detection result is not accurate enough, and possibly cause the master database to be mistakenly cut into the slave database as a fault database.
Disclosure of Invention
In view of the foregoing, it is desirable to provide a method and an apparatus for detecting a database status, an electronic device, and a storage medium thereof, which can improve accuracy of database failure detection.
In one aspect, the present application provides a method for detecting a database status, which is applied to an application server, where the application server is correspondingly connected with a master database and at least one slave database, and the method includes:
acquiring the running state of the middleware in the application server;
when the operating state of the middleware is the starting state, a plurality of verification routines of a checking database are created in the middleware;
and determining the state of the main database according to the plurality of check routines.
In some embodiments, the plurality of check protocols includes a first check protocol;
the step of determining the status of the master database according to the plurality of check routines comprises:
performing database verification according to the plurality of verification coroutines to obtain a plurality of verification states, wherein the plurality of verification states are obtained by performing database verification on the plurality of verification coroutines except for the first verification coroutine;
when any one of the plurality of check states is an abnormal state, acquiring the plurality of check states according to the first check coroutine;
and determining the state of the master database according to the plurality of check states.
In some embodiments, the plurality of check protocols includes a second check protocol, the plurality of check states includes a first check state, and the first check state is a state obtained by checking the database by the second check protocol;
the step of determining the state of the master database from the plurality of check states includes:
acquiring a first value, a second value and a third value according to the second check protocol, wherein the first value is the number of times that the second check protocol sends the data write request to a master database node of a database, the second value is the number of times that the data write request received by the second check protocol returns to the master database node, and the third value is the third value obtained according to the first value and the second value;
comparing the third value with a first preset threshold value to obtain a comparison result;
and obtaining a first checking state according to the comparison result.
In some embodiments, the plurality of check protocols includes a third check protocol, the plurality of check states includes a second check state, and the second check state is a state obtained by the third check protocol checking the database;
the step of determining the state of the master database from the plurality of check states includes:
sending a request for inserting the inspection data into the master database to the master database node according to the third verification corotation to obtain a first result and a second result, wherein the first result is the result of whether the data is successfully inserted into the master database, and the second result is the result of whether the request is successfully sent;
and obtaining the second check state according to the first result and the second result.
In some embodiments, the plurality of check routines includes a fourth check routine, the plurality of check states includes a fourth check state, and the fourth check state is a state obtained by checking the database by the third check routine;
the step of determining the state of the master database from the plurality of check states includes:
acquiring the state of a read-write thread of a slave database according to the fourth check coroutine, wherein the state of the read-write thread is the connection state of the slave database and the master database through the read-write thread;
and obtaining a third verification state according to the state of the read-write thread.
In some embodiments, the step of determining the state of the master database from the plurality of check states comprises:
when the first check state, the second check state and the third check state are all abnormal states, determining that the state of the database is an abnormal state;
and when any one of the first check state, the second check state and the third check state is a normal state, determining that the state of the database is a normal state.
In some embodiments, after the step of determining that the state of the database is an abnormal state, the method further includes:
and when the state of the database is determined to be an abnormal state, selecting a target database from the at least one slave database, and adjusting the target database to be a master database.
In another aspect, the present application further provides an apparatus for detecting a status of a database, the apparatus including:
the detection unit is used for acquiring the running state of the middleware in the application server;
the creating unit is used for creating a plurality of verification routines of the inspection database in the middleware when the operating state of the middleware is the starting state;
and the processing unit is used for determining the state of the main database according to the plurality of check coroutines.
In some embodiments, the plurality of check protocols includes a first check protocol; the processing unit is configured to:
performing database verification according to the plurality of verification coroutines to obtain a plurality of verification states, wherein the plurality of verification states are obtained by performing database verification on the plurality of verification coroutines except for the first verification coroutine;
when any one of the plurality of check states is an abnormal state, acquiring the plurality of check states according to the first check coroutine;
and determining the state of the master database according to the plurality of check states.
In some embodiments, the plurality of check protocols includes a second check protocol, the plurality of check states includes a first check state, and the first check state is a state obtained by checking the database by the second check protocol; the processing unit is configured to:
acquiring a first value, a second value and a third value according to the second check protocol, wherein the first value is the number of times that the second check protocol sends the data write request to a master database node of a database, the second value is the number of times that the data write request received by the second check protocol returns to the master database node, and the third value is the third value obtained according to the first value and the second value;
comparing the third value with a first preset threshold value to obtain a comparison result;
and obtaining a first checking state according to the comparison result.
In some embodiments, the plurality of check protocols includes a third check protocol, the plurality of check states includes a second check state, and the second check state is a state obtained by the third check protocol checking the database; the processing unit is configured to:
sending a request for inserting the inspection data into the master database to the master database node according to the third verification corotation to obtain a first result and a second result, wherein the first result is the result of whether the data is successfully inserted into the master database, and the second result is the result of whether the request is successfully sent;
and obtaining the second check state according to the first result and the second result.
In some embodiments, the plurality of check routines includes a fourth check routine, the plurality of check states includes a fourth check state, and the fourth check state is a state obtained by checking the database by the third check routine; the processing unit is configured to:
acquiring the state of a read-write thread of a slave database according to the fourth check coroutine, wherein the state of the read-write thread is the connection state of the slave database and the master database through the read-write thread;
and obtaining a third verification state according to the state of the read-write thread.
In some embodiments, the processing unit is to:
when the first check state, the second check state and the third check state are all abnormal states, determining that the state of the database is an abnormal state;
and when any one of the first check state, the second check state and the third check state is a normal state, determining that the state of the database is a normal state.
In some embodiments, the processing unit is further to:
and when the state of the database is determined to be an abnormal state, selecting a target database from the at least one slave database, and adjusting the target database to be a master database.
In another aspect, the present application further provides an electronic device, including:
one or more processors;
a memory for storing one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors implement the database state detection method.
In another aspect, the present application further provides a computer-readable storage medium, on which a computer program is stored, which when executed by a processor, performs the method for detecting the state of a database.
According to the method and the device, the states of the databases are detected by establishing a plurality of check coroutines through the middleware, whether the main database breaks down or not is judged, the states of the main database are comprehensively judged through the states of the check coroutines, the database is not judged to be abnormal because a single check coroutine is abnormal, the main database is prevented from being misjudged to be a fault database, the fault database is prevented from being mistakenly switched, and the fault detection precision is improved.
Drawings
The technical solution and other advantages of the present application will become apparent from the detailed description of the embodiments of the present application with reference to the accompanying drawings.
Fig. 1 is a schematic system architecture diagram of a database state detection method according to an embodiment of the present disclosure.
Fig. 2 is a schematic flowchart of a database state detection method according to an embodiment of the present disclosure.
Fig. 3 is a schematic flowchart of a method for detecting a database state according to another embodiment of the present disclosure.
Fig. 4 is a schematic flowchart of an embodiment of step 103 in the embodiment of the present application.
Fig. 5 is a schematic flow chart of another embodiment of step 103 in the embodiment of the present application.
Fig. 6 is a schematic flow chart of another embodiment of step 103 in the embodiment of the present application.
Fig. 7 is a schematic diagram of a database status detection apparatus according to an embodiment of the present application.
Fig. 8 is a schematic structural diagram of an electronic device for detecting a database state according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. It is to be understood that the embodiments described are only a few embodiments of the present application and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
In the description of the present application, it is to be understood that the terms "center," "longitudinal," "lateral," "length," "width," "thickness," "upper," "lower," "front," "rear," "left," "right," "vertical," "horizontal," "top," "bottom," "inner," "outer," "clockwise," "counterclockwise," and the like are used in the orientations and positional relationships indicated in the drawings for convenience in describing the present application and for simplicity in description, and are not intended to indicate or imply that the referenced devices or elements must have a particular orientation, be constructed in a particular orientation, and be operated in a particular manner, and are not to be construed as limiting the present application. Furthermore, the terms "first", "second" and "first" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, features defined as "first", "second", may explicitly or implicitly include one or more of the described features. In the description of the present application, "a plurality" means two or more unless specifically limited otherwise.
In the description of the present application, it is to be noted that, unless otherwise explicitly specified or limited, the terms "mounted," "connected," and "connected" are to be construed broadly, e.g., as meaning either a fixed connection, a removable connection, or an integral connection; may be mechanically connected, may be electrically connected or may be in communication with each other; either directly or indirectly through intervening media, either internally or in any other relationship. The specific meaning of the above terms in the present application can be understood by those of ordinary skill in the art as appropriate.
In this application, unless expressly stated or limited otherwise, the first feature "on" or "under" the second feature may comprise direct contact of the first and second features, or may comprise contact of the first and second features not directly but through another feature in between. Also, the first feature being "on," "above" and "over" the second feature includes the first feature being directly on and obliquely above the second feature, or merely indicating that the first feature is at a higher level than the second feature. A first feature being "under," "below," and "beneath" a second feature includes the first feature being directly under and obliquely below the second feature, or simply meaning that the first feature is at a lesser elevation than the second feature.
The following disclosure provides many different embodiments or examples for implementing different features of the application. In order to simplify the disclosure of the present application, specific example components and arrangements are described below. Of course, they are merely examples and are not intended to limit the present application. Moreover, the present application may repeat reference numerals and/or letters in the various examples, such repetition is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed. In addition, examples of various specific processes and materials are provided herein, but one of ordinary skill in the art may recognize applications of other processes and/or use of other materials.
Referring to fig. 1, the database status detection method provided in the present application may be applied to an application environment as shown in fig. 1, that is, may be applied to an application environment including an application server 10, a client device 20, and a storage 30, where the client device 20 and the storage 30 are in network connection with the application server 10, where the client device 20 is loaded with a client, the application server 10 is loaded with a middleware 40, the data storage 30 is used for storing data, and for example, a database 50 is provided, the middleware 40 is used for analyzing according to a data access request received from a client in the client device 10 and establishing a connection with the database 50, and the middleware 40 further receives a returned result from the data access request of the database 50 and returns the result to the client.
Wherein the data access request may include a data write request and a data read request. The database 50 may include a master database and at least one slave database, the master database 50 is configured to receive a data write request of a data access request, write data carried in the data write request into the master database, and synchronously update the write data into the slave database, and the target slave database receives a data read request through the middleware 40.
The data access request may be specifically in the form of SQL language, for example, after receiving the data access request in the form of SQL language, the middleware 40 may analyze a target database that the client needs to access according to the content of SQL language, and establish an access connection with the target database, and further directly forward the access request to the target database, so as to directly initiate access to the target database through the SQL language; the data access request may also be generated according to a preset command format, and the middleware 40 extracts target information in the data access request after receiving the data access request, so as to obtain the position of the target database and the target data, which need to be accessed by the user, in the database, further generate a corresponding SQL language according to the data access requirement of the user, and initiate access to the target data to the database through the generated SQL language.
The database 50 may be a relational database cluster, that is, an open database connection driver may be provided to integrate the databases, for example, in the embodiment of the present application, the database 50 may be a MySQL database, or an open database such as maria db and a supercona Server, and the database 30 may include a master database and at least one slave database, which are not limited herein.
In the present embodiment, the middleware 40 is loaded in the application server 10, and the middleware 40 is a separate system software or service program located between the client in the client device 10 and the database 30. Middleware 20 is a type of computer software that interfaces software components and applications, and includes a set of services to facilitate the interaction of multiple pieces of software running on one or more machines over a network, the interoperability provided by this technology driving the evolution of a consistent distributed architecture that is typically used to support and simplify those complex distributed applications, including web servers, transaction monitors, and message queue software. The middleware may be Proxy, Cobar, MyCat, Vitess, Atlas, etc.
In the embodiment of the present application, a plurality of check protocols for checking the database are created in the middleware 40 to detect the state of the master database; and determining the state of the main database according to the plurality of check protocol, judging whether the main database fails, and returning the result of detecting the state of the main database to the client.
In the embodiment of the present application, the communication between the client and the middleware 40 may be implemented by any communication manner, including but not limited to, mobile communication based on the third Generation Partnership Project (3 GPP), Long Term Evolution (LTE), Worldwide Interoperability for microwave Access (WiMAX), or computer network communication based on the TCP/IP Protocol Suite (TCP/IP), User Datagram Protocol (UDP), and the like.
Those skilled in the art will understand that the application environment shown in fig. 1 is only one application scenario related to the present application, and does not constitute a limitation on the application scenario of the present application, and that other application environments may further include more or fewer servers than those shown in fig. 1, for example, only 1 server is shown in fig. 1, and it is understood that the application environment may further include one or more other clients corresponding to the accessible application server, and is not limited herein. The client device 10 may include at least one of a cell phone, a tablet, a laptop, a personal digital assistant, a wearable device, and the like.
Specifically, referring to fig. 2, an embodiment of the present application provides a method for detecting a database state, which specifically includes steps 101 to 103:
The running state of the middleware can be obtained through a preset command statement, and the running state of the middleware comprises the following steps: the present embodiment aims to acquire an operating state of the middleware, for example, when the middleware between the client and the master database is Proxy, the operating state of the Proxy is the starting state.
In this embodiment, the middleware Proxy is connected to a back-end database, and is configured to store data of the MySQL database collected by the middleware Proxy; for example, the back-end database may be an SQLite database, and a corresponding storage table is established in a MySQL database to store real-time data collected by a corresponding client, so as to facilitate unloading and history retrieval; and then, the acquired real-time data is stored in the corresponding MySQL work database space through one-time transfer storage in an SQLite database interaction operation mode, namely, after the Proxy obtains the verification state of the MySQL database through a plurality of verification coroutines, the data such as the verification code, the Proxy IP address, the port and the like obtained by each coroutine are stored in the SQLite database.
And 103, determining the state of the main database according to the plurality of check routines.
Taking the primary database as the MySQL database as an example, the state of the MySQL database may be a normal state or a failure state, the normal state is a state in which the database normally operates, and the failure state database is in a failure state. Common cases of MySQL data failures include: the method comprises the following steps of full connection number failure of MySQL ports, full failure of MySQL disks, downtime of a MySQL main database and the like. For the condition that the MySQL port connection number is full, namely, switching is not required to be executed generally, the corresponding solution is to set an alarm threshold value, for example, when the connection number reaches 80% of the preset port connection number, an alarm is started to perform manual intervention; if the port connection number is full but no alarm is given, the port connection number can be manually increased. For the condition of the capacity full fault of the MySQL disk, a general solution is to set an alarm threshold value, and start alarming when the connection number reaches 80% to perform manual intervention; if the disk capacity is full but no alarm is given, a failover needs to be performed, namely one of the slave databases is switched to the master database, and the failed master database is switched to the slave database. For the situation that the MySQL main database is down or restarted due to other reasons, the automatic fault switching needs to be executed.
According to the method, the state of the main database is detected by establishing the plurality of check protocol programs through the middleware, whether the main database breaks down or not is judged, the state of the main database is comprehensively judged through the states of the plurality of check protocol programs, the main database is judged to be abnormal without the fact that a single check protocol program is abnormal, the main database is prevented from being judged to be a fault database by mistake, therefore, the fault database is prevented from being switched by mistake, and the fault detection precision is improved.
In some embodiments, the plurality of check protocols includes a first check protocol; correspondingly, the step 103 determines the state of the primary database according to the plurality of check routines, referring to fig. 3, specifically includes the following steps 201 and 203:
And the first checking protocol is used for waiting for calling other protocols in the middleware Proxy. Each coroutine obtains a check state after detecting the master database, and in this embodiment, the check state may be represented by a preset check code, and the check code may be a binary code. For example, when the verification state is normal, it can be represented by any of 0, 00, and 010, and correspondingly, when the verification state is abnormal, it can be represented by any of 1, 11, and 101. It should be understood that the above status code is only one expression of the verification status, and besides the above expression, the status code may be modified, or expressed in the form of letters or characters, etc., which are not limited in this application.
If the verification state of one verification coroutine is abnormal, initiating an arbitration task, namely calling a first verification coroutine to verify the states of other verification coroutines, and after the first verification coroutine acquires the verification results of all other verification coroutines, comprehensively judging the state of the main database according to the obtained verification results.
And step 203, determining the state of the master database according to the plurality of verification states.
When a certain checking protocol checking state is abnormal and a first checking protocol is called to check the states of other checking protocols, as long as the first checking protocol detects that the state code of any one checking protocol is not 1, the checking result generated by the first checking protocol is 0, at the moment, the main database is considered to be not failed, and the first checking protocol gives up checking on other checking protocols; and if the first check coroutine detects that the state codes of all other check coroutines are all 1, the check result generated by the first check coroutine is 0, and the main database is judged to be in fault.
In some embodiments, the plurality of check routines includes a second check routine, and the plurality of check states includes a first check state, where the first check state is a state obtained by the second check routine checking the MySQL database.
The second check-up routine is used to count the failure rate of transactions sent to the master database within a preset duration, wherein the preset duration may be, for example, a duration of one second.
The step 203 determines the state of the primary database according to the plurality of verification states, referring to fig. 4, which specifically includes the following steps 301 and 302:
The first value is the number of times that the second check coroutine sends the data write request to a master database node of the MySQL database, namely, the number of total transactions.
And the second value is the number of times that the data write request received by the second check routine is returned to the master database node.
And the third value is obtained according to the first value and the second value, the third value is used for indicating the failure rate of the transaction sent to the master database in every second, the middleware Proxy can identify the read traffic or the write traffic when forwarding the instruction, and if the write traffic is forwarded to the master database node. Because the failure rate statistics is based on the return of the transaction received by the middleware Proxy, the results that the transaction is ended but the transaction is not normally returned are all calculated in failure, and the transaction is not ended or the return of a null value is all calculated in success, the failure rate calculation method can be expressed by the following mathematical formula:
wherein r represents failure rate, m represents the total times of forwarding instructions to the master database by the middleware Proxy, and n represents the total times of receiving the returns from the master database by the middleware Proxy. m, n, r correspond to the first value, the second value and the third value, respectively.
It should be noted that the above mathematical expression is only one expression form of the first value, the second value, and the third value, and parameters may be added to the expression or a computational modification may be performed on the expression, which is not limited in this application.
the second check routine is provided with two counters, a first counter and a second counter, the instruction statement is analyzed in the middleware Proxy, if the operation is sent to the main database, the first counter is recorded as m +1, the return result of the main database is judged at the same time, if the return result reports errors, the second counter is recorded as n +1, and the value of r is compared with a first preset threshold value, wherein the first preset threshold value can be represented by a binary state code; for example, to determine whether the value of r is equal to 1.
And 302, obtaining a first verification state according to the comparison result.
For example, whether the state code of the second check protocol is equal to 1 is judged, if so, the first check protocol is called to check the states of other check protocols, which indicates that the check result of the second check protocol is abnormal.
Meanwhile, the second check Protocol executes once per second to store the value of r and the connection Address of the middleware Proxy in the back-end database, wherein the connection Address is a network Address for connecting the database, and the connection Address may include an Internet Protocol Address (IP Address) and a network port. Backend data may be, for example, an SQLite database; a corresponding storage table is established in the MySQL database to store real-time data collected by corresponding equipment, so that unloading and history retrieval are facilitated; and then, storing the acquired real-time data into the corresponding MySQL working database space through one-time transfer in an SQLite database interaction operation mode.
In some embodiments, the plurality of check protocols includes a third check protocol, the plurality of check states includes a second check state, and the second check state is a state obtained by the third check protocol checking the database.
The step 203 of determining the state of the primary database according to the plurality of verification states includes, as shown in fig. 5, the following steps 401 and 402:
And the third verification protocol establishes new connection with the main database according to a preset frequency, for example, the connection with the main database is established once every 1 second, the preset monitoring data is inserted into the main data, the return result is judged, the connection with the database is disconnected after the return result is obtained, and the connection with the main data is established again in the next second.
The purpose of inserting the monitoring data is to detect whether the port connection number is full and whether the disk is full, wherein whether the disk is full is judged by whether the monitoring data can be inserted into the disk, and the returned result is a detection result, for example, the first result corresponds to the result of whether the connection is successful, the second result corresponds to the result of whether the monitoring data can be inserted into the disk, if the third protocol is successfully connected with the main database and the monitoring database is successfully inserted into the disk, the verification state of the third verification protocol is marked as success, the verification state is represented by a state code 0, and meanwhile, the Proxy IP address and the port are written into a back-end storage database SQLite; and if the third protocol is not connected with the main database or the monitoring data cannot be inserted into the disk, marking the checking state of the third checking protocol as failure, representing the failure by using a state code 1, writing the IP address and the port of the Proxy into a back-end storage database SQLite, and calling the first checking protocol for arbitration.
By continuously performing the operations of connection, disconnection and insertion, whether the port connection number of the main library is full or not or whether the main library is full or not is judged.
In some embodiments, the plurality of check routines includes a fourth check routine, the plurality of check states includes a fourth check state, and the fourth check state is a state obtained by checking the database by the third check routine;
the step 203 of determining the state of the primary database according to the plurality of verification states includes, as shown in fig. 6, the following steps 501 and 502:
and 502, obtaining a third verification state according to the state of the read-write thread.
And establishing connection between the slave database and the master database through a fourth check protocol according to a preset frequency, for example, acquiring monitoring states of the master database and the slave database once every 1 second, namely judging whether a read-write thread of the slave database can be connected with the master database, marking the check state of the third check protocol as successful if the connection is successful, and simultaneously writing the IP address and the port of the Proxy into the back-end storage database by using a state code 0, otherwise, marking the check state of the third check protocol as failed, and marking the check state of the third check protocol as failed by using a state code 1, writing the IP address and the port of the Proxy into the SQLite of the back-end storage database, and simultaneously calling the first check protocol for arbitration. And the state monitoring of the master database node is realized by judging the read-write state in the slave database node.
In some embodiments, the step 203 of determining the state of the primary database according to the plurality of verification states specifically includes the following steps 601 and 602:
601, if the first check state, the second check state and the third check state are all abnormal states, determining that the state of the master database is an abnormal state;
the first check state, the second check state, and the third check state may be represented by a state code, for example, the state code is 0 or 1, 0 represents that the check state is normal, and 1 represents that the check state is abnormal.
After the middleware Proxy is started, acquiring information of a master database node and a slave database node of MySQL from a configuration file, simultaneously starting four protocols of a first verification protocol, a second verification protocol and a fourth verification protocol, after business flow reaches the Proxy, the Proxy analyzes the SQL, reading flow is forwarded to a corresponding slave node according to a certain rule, writing flow is forwarded to a corresponding master node, and if the first verification protocol verifies a first verification state, a second verification state and a third verification state, namely state codes obtained by the second verification protocol, the third verification protocol and the fourth verification protocol are all 1, the first verification protocol verification result is recorded as 1, and the master database fault is judged.
Step 602, if any one of the first check state, the second check state and the third check state is a normal state, determining that the state of the master database is a normal state.
For example, when the second check protocol completes the check of the master database to obtain the first check state, if the state code of the first check state is 1, the second check protocol actively calls the first check protocol to check the states of the third check protocol and the fourth check protocol, as long as the check state of one protocol in the third check protocol or the fourth check protocol is not 1, the check result of the first check protocol is marked as 0, and if the state of the master database at this time is judged to be a normal state, that is, the database is normal, the fault switching is abandoned and the state check of the third check protocol and the fourth check protocol is continued.
In some embodiments, if the first check protocol check result is recorded as 1, the first check protocol then repeatedly checks two rounds of states of the second check protocol, the third check protocol and the fourth check protocol, if the three rounds of checks that the state codes obtained by the first check protocol are all 1, the state of the database is judged to be abnormal, otherwise, the state of the database is judged to be normal, and no operation is executed.
In some embodiments, after determining 603 that the state of the master database is an abnormal state, the method further includes:
step 603, when the state of the master database is determined to be an abnormal state, selecting a target database from the at least one slave database, and adjusting the target database to be the master database.
And when the state of the master database is determined to be abnormal, namely the master database fails, performing fault switching, promoting the slave database of the latest data to be a new master database, and then redirecting all other slave databases to the new master database, thereby ensuring the normal operation of the server.
And checking the states of the second check protocol, the second check protocol and the third check protocol by calling the first check protocol, performing comprehensive judgment according to a check result, considering that the result is credible, and executing fault switching operation if the state of the main database is determined to be an abnormal state.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and parts that are not described in detail in a certain embodiment may refer to the above detailed descriptions of other embodiments, and are not described herein again.
In a specific implementation, each unit or structure may be implemented as an independent entity, or may be combined arbitrarily to be implemented as one or several entities, and the specific implementation of each unit or structure may refer to the foregoing method embodiment, which is not described herein again.
In order to better implement the database state detection method in the embodiment of the present application, on the basis of the database state detection method, the embodiment of the present application further provides a database state detection device. The state detection device of the database is integrated in equipment, and the equipment can be a server or a client, such as a mobile phone, a tablet computer, a desktop computer and the like.
Fig. 7 is a schematic block diagram of a state detection apparatus of a database provided in an embodiment of the present application, where the apparatus for identifying a concrete state includes a detection unit 701, a creation unit 702, and a processing unit 703, as shown in fig. 7, where:
an obtaining unit 701, configured to obtain an operating state of middleware in an application server;
a creating unit 702, configured to create, in the middleware, multiple check routines for checking a database when the acquired running state of the middleware is a starting state;
the processing unit 703 is configured to determine a state of the primary database according to the plurality of check routines.
In some embodiments, the plurality of check protocols includes a first check protocol; the processing unit 703 is configured to:
performing database verification according to the plurality of verification coroutines to obtain a plurality of verification states, wherein the plurality of verification states are obtained by performing database verification on the plurality of verification coroutines except for the first verification coroutine;
when any one of the plurality of check states is an abnormal state, acquiring the plurality of check states according to the first check coroutine;
and determining the state of the master database according to the plurality of check states.
In some embodiments, the plurality of check protocols includes a second check protocol, the plurality of check states includes a first check state, and the first check state is a state obtained by checking the database by the second check protocol; the processing unit 703 is configured to:
acquiring a first value, a second value and a third value according to the second check protocol, wherein the first value is the number of times that the second check protocol sends the data write request to a master database node of a database, the second value is the number of times that the data write request received by the second check protocol returns to the master database node, and the third value is the third value obtained according to the first value and the second value;
comparing the third value with a first preset threshold value to obtain a comparison result;
and obtaining a first checking state according to the comparison result.
In some embodiments, the plurality of check protocols includes a third check protocol, the plurality of check states includes a second check state, and the second check state is a state obtained by the third check protocol checking the database; the processing unit 703 is configured to:
sending a request for inserting the inspection data into the master database to the master database node according to the third verification corotation to obtain a first result and a second result, wherein the first result is the result of whether the data is successfully inserted into the master database, and the second result is the result of whether the request is successfully sent;
and obtaining the second check state according to the first result and the second result.
In some embodiments, the plurality of check routines includes a fourth check routine, the plurality of check states includes a fourth check state, and the fourth check state is a state obtained by checking the database by the third check routine; the processing unit 703 is configured to:
acquiring the state of a read-write thread of a slave database according to the fourth check coroutine, wherein the state of the read-write thread is the connection state of the slave database and the master database through the read-write thread;
and obtaining a third verification state according to the state of the read-write thread.
In some embodiments, the processing unit 703 is configured to:
when the first check state, the second check state and the third check state are all abnormal states, determining that the state of the main database is an abnormal state;
and when any one of the first check state, the second check state and the third check state is a normal state, determining that the state of the master database is a normal state.
In some embodiments, the processing unit 703 is further configured to:
and when the state of the master database is determined to be an abnormal state, selecting a target database from the at least one slave database, and adjusting the target database to be the master database.
The device of this application embodiment obtains the starting condition of middleware through obtaining unit 701, and a plurality of check coroutines are established at the middleware that is in starting condition to establishment unit 702, and processing unit 702 passes through a plurality of check coroutines detect the database state, judge whether the main database breaks down, state in order to carry out the comprehensive judgement main database through a plurality of check coroutines, it is unusual not just to judge the database because a single a certain check coroutine appears unusually, avoid the main database to be misjudged as the trouble database, thereby avoid causing trouble database miscover, improve the fault detection precision.
An embodiment of the present application further provides an electronic device, which integrates any one of the state detection devices of the database provided in the embodiments of the present application, please refer to fig. 8, and fig. 8 shows a schematic structural diagram of the electronic device according to the embodiments of the present application, specifically:
the electronic device may include components such as a processor 801 of one or more processing cores, memory 802 of one or more computer-readable storage media, a power supply 803, and an input unit 804. Those skilled in the art will appreciate that the electronic device configuration shown in fig. 8 does not constitute a limitation of the electronic device and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components. Wherein:
the processor 801 is a control center of the electronic device, connects various parts of the entire electronic device using various interfaces and lines, and performs various functions of the electronic device and processes data by operating or executing software programs and/or modules stored in the memory 802 and calling data stored in the memory 802, thereby performing overall monitoring of the electronic device. Alternatively, processor 801 may include one or more processing cores; preferably, the processor 801 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 801.
The memory 802 may be used to store software programs and modules, and the processor 801 executes various functional applications and data processing by operating the software programs and modules stored in the memory 802. The memory 802 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data created according to use of the electronic device, and the like. Further, the memory 802 may include high speed random access memory and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, the memory 802 may also include a memory controller to provide the processor 801 access to the memory 802.
The electronic device further comprises a power supply 803 for supplying power to each component, and preferably, the power supply 803 can be logically connected with the processor 801 through a power management system, so that functions of charging, discharging, power consumption management and the like can be managed through the power management system. The power supply 803 may also include one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and any like components.
The electronic device may further include an input unit 804, and the input unit 804 may be used to receive input numeric or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.
Although not shown, the electronic device may further include a display unit and the like, which are not described in detail herein. Specifically, in this embodiment, the processor 801 in the electronic device loads an executable file corresponding to a process of one or more application programs into the memory 802 according to the following instructions, and the processor 801 runs the application programs stored in the memory 802, so as to implement various functions as follows:
acquiring the running state of the middleware in the application server; when the operating state of the middleware is the starting state, a plurality of verification routines of a checking database are created in the middleware; and determining the state of the main database according to the plurality of check routines.
According to the method, the database state is detected by establishing the plurality of check coroutines through the middleware, whether the main database fails or not is judged, the state of the main database is comprehensively judged through the states of the plurality of check coroutines, the database is judged to be abnormal without the fact that a single check coroutine is abnormal, the main database is prevented from being judged to be a fault database by mistake, therefore, the fault database is prevented from being switched by mistake, and the fault detection precision is improved.
It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions or by associated hardware controlled by the instructions, which may be stored in a computer readable storage medium and loaded and executed by a processor.
To this end, an embodiment of the present application provides a computer-readable storage medium, which may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like. Stored thereon, is a computer program, which is loaded by a processor to execute the steps of any of the logistics hub and distribution point addressing methods provided by the embodiments of the present application. For example, the computer program may be loaded by a processor to perform the steps of:
acquiring the running state of the middleware in the application server; when the operating state of the middleware is the starting state, a plurality of verification routines of a checking database are created in the middleware; and determining the state of the main database according to the plurality of check routines.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and parts that are not described in detail in a certain embodiment may refer to the above detailed descriptions of other embodiments, and are not described herein again.
In a specific implementation, each unit or structure may be implemented as an independent entity, or may be combined arbitrarily to be implemented as one or several entities, and the specific implementation of each unit or structure may refer to the foregoing method embodiment, which is not described herein again.
The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.
The logistics distribution point addressing method, the logistics distribution point addressing device, the electronic device and the storage medium provided by the embodiment of the application are introduced in detail, a specific example is applied in the embodiment of the application to explain the principle and the implementation mode of the embodiment of the application, and the description of the embodiment is only used for helping to understand the method and the core idea of the embodiment of the application; meanwhile, for those skilled in the art, according to the idea of the embodiment of the present application, the specific implementation manner and the application range may be changed, and in summary, the content of the present specification should not be construed as a limitation to the embodiment of the present application.
Claims (10)
1. A method for detecting database state is characterized in that the method is applied to an application server, the application server is correspondingly connected with a master database and at least one slave database, and the method comprises the following steps:
acquiring the running state of the middleware in the application server;
when the operating state of the middleware is the starting state, a plurality of verification routines of a checking database are created in the middleware;
and determining the state of the main database according to the plurality of check routines.
2. The method of claim 1, wherein the plurality of check protocols comprises a first check protocol;
the step of determining the status of the master database according to the plurality of check routines comprises:
performing database verification according to the plurality of verification coroutines to obtain a plurality of verification states, wherein the plurality of verification states are obtained by performing database verification on the plurality of verification coroutines except for the first verification coroutine;
when any one of the plurality of check states is an abnormal state, acquiring the plurality of check states according to the first check coroutine;
and determining the state of the master database according to the plurality of check states.
3. The method of claim 2, wherein the plurality of check-up routines comprises a second check-up routine, the plurality of check-up states comprises a first check-up state, and the first check-up state is a state obtained by the second check-up routine checking up the database;
the step of determining the state of the master database from the plurality of check states includes:
acquiring a first value, a second value and a third value according to the second check protocol, wherein the first value is the number of times that the second check protocol sends the data write request to a master database node of a database, the second value is the number of times that the data write request received by the second check protocol returns to the master database node, and the third value is the third value obtained according to the first value and the second value;
comparing the third value with a first preset threshold value to obtain a comparison result;
and obtaining the first verification state according to the comparison result.
4. The method of claim 2, wherein the plurality of check-up routines comprises a third check-up routine, the plurality of check-up states comprises a second check-up state, and the second check-up state is a state obtained by the third check-up routine checking up the database;
the step of determining the state of the master database from the plurality of check states includes:
sending a request for inserting the inspection data into the master database to the master database node according to the third verification corotation to obtain a first result and a second result, wherein the first result is the result of whether the data is successfully inserted into the master database, and the second result is the result of whether the request is successfully sent;
and obtaining the second check state according to the first result and the second result.
5. The method of any of claims 2-4, wherein the plurality of check protocols includes a fourth check protocol, the plurality of check states includes a fourth check state, and the fourth check state is a state obtained by a third check protocol checking the database;
the step of determining the state of the master database from the plurality of check states includes:
acquiring the state of a read-write thread of a slave database according to the fourth check coroutine, wherein the state of the read-write thread is the connection state of the slave database and the master database through the read-write thread;
and obtaining a third verification state according to the state of the read-write thread.
6. The method of claim 5, wherein the step of determining the state of the master database from the plurality of check states comprises:
when the first check state, the second check state and the third check state are all abnormal states, determining that the state of the database is an abnormal state;
and when any one of the first check state, the second check state and the third check state is a normal state, determining that the state of the database is a normal state.
7. The method of claim 6, wherein the step of determining the status of the database as an abnormal status is followed by:
and when the state of the database is determined to be an abnormal state, selecting a target database from the at least one slave database, and adjusting the target database to be a master database.
8. An apparatus for detecting a status of a database, comprising:
the acquisition unit is used for acquiring the running state of the middleware in the application server;
the creating unit is used for creating a plurality of verification routines of the inspection database in the middleware when the operating state of the middleware is the starting state;
and the processing unit is used for determining the state of the main database according to the plurality of check coroutines.
9. An electronic device, characterized in that the electronic device comprises:
one or more processors;
a memory for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement a method of detecting a database state as recited in any of claims 1-7.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out a method for detecting a database state according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010310910.5A CN111552637B (en) | 2020-04-20 | 2020-04-20 | Database state detection method and device, electronic equipment and storage medium thereof |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010310910.5A CN111552637B (en) | 2020-04-20 | 2020-04-20 | Database state detection method and device, electronic equipment and storage medium thereof |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111552637A true CN111552637A (en) | 2020-08-18 |
| CN111552637B CN111552637B (en) | 2023-05-19 |
Family
ID=72002466
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010310910.5A Active CN111552637B (en) | 2020-04-20 | 2020-04-20 | Database state detection method and device, electronic equipment and storage medium thereof |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111552637B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113312351A (en) * | 2021-06-01 | 2021-08-27 | 北京沃东天骏信息技术有限公司 | Data processing method and device |
| CN113779118A (en) * | 2020-10-28 | 2021-12-10 | 北京沃东天骏信息技术有限公司 | Business processing method, device and system based on Vitess architecture |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2000181753A (en) * | 1998-12-16 | 2000-06-30 | Fujitsu Ltd | Fault recovery method, fault recovery system for the same and computer readable program recording medium |
| CN101183377A (en) * | 2007-12-10 | 2008-05-21 | 华中科技大学 | High availability data-base cluster based on message middleware |
| JP2014137798A (en) * | 2013-01-18 | 2014-07-28 | Oki Electric Ind Co Ltd | Database system and control method for database system |
| US20140298112A1 (en) * | 2013-03-29 | 2014-10-02 | Fujitsu Limited | Detection method, storage medium, and detection device |
| CN104503965A (en) * | 2014-10-16 | 2015-04-08 | 杭州斯凯网络科技有限公司 | High-elasticity high availability and load balancing realization method of PostgreSQL (Structured Query Language) |
| CN105404581A (en) * | 2015-12-25 | 2016-03-16 | 北京奇虎科技有限公司 | Database evaluation method and device |
| CN105577799A (en) * | 2015-12-25 | 2016-05-11 | 北京奇虎科技有限公司 | Method and device for detecting fault of database cluster |
| CN109344061A (en) * | 2018-09-25 | 2019-02-15 | 阿里巴巴集团控股有限公司 | A kind of method for detecting abnormality of interface, device, equipment and system |
| CN110162428A (en) * | 2019-05-17 | 2019-08-23 | 中国铁道科学研究院集团有限公司 | Method of data synchronization and device, electronic equipment and computer readable storage medium |
| CN110362625A (en) * | 2019-05-30 | 2019-10-22 | 杭州数梦工场科技有限公司 | Data base read-write separation method, device, electronic equipment and storage medium |
| CN110673994A (en) * | 2019-09-20 | 2020-01-10 | 北京百度网讯科技有限公司 | Database testing method and device |
-
2020
- 2020-04-20 CN CN202010310910.5A patent/CN111552637B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2000181753A (en) * | 1998-12-16 | 2000-06-30 | Fujitsu Ltd | Fault recovery method, fault recovery system for the same and computer readable program recording medium |
| CN101183377A (en) * | 2007-12-10 | 2008-05-21 | 华中科技大学 | High availability data-base cluster based on message middleware |
| JP2014137798A (en) * | 2013-01-18 | 2014-07-28 | Oki Electric Ind Co Ltd | Database system and control method for database system |
| US20140298112A1 (en) * | 2013-03-29 | 2014-10-02 | Fujitsu Limited | Detection method, storage medium, and detection device |
| CN104503965A (en) * | 2014-10-16 | 2015-04-08 | 杭州斯凯网络科技有限公司 | High-elasticity high availability and load balancing realization method of PostgreSQL (Structured Query Language) |
| CN105404581A (en) * | 2015-12-25 | 2016-03-16 | 北京奇虎科技有限公司 | Database evaluation method and device |
| CN105577799A (en) * | 2015-12-25 | 2016-05-11 | 北京奇虎科技有限公司 | Method and device for detecting fault of database cluster |
| CN109344061A (en) * | 2018-09-25 | 2019-02-15 | 阿里巴巴集团控股有限公司 | A kind of method for detecting abnormality of interface, device, equipment and system |
| CN110162428A (en) * | 2019-05-17 | 2019-08-23 | 中国铁道科学研究院集团有限公司 | Method of data synchronization and device, electronic equipment and computer readable storage medium |
| CN110362625A (en) * | 2019-05-30 | 2019-10-22 | 杭州数梦工场科技有限公司 | Data base read-write separation method, device, electronic equipment and storage medium |
| CN110673994A (en) * | 2019-09-20 | 2020-01-10 | 北京百度网讯科技有限公司 | Database testing method and device |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113779118A (en) * | 2020-10-28 | 2021-12-10 | 北京沃东天骏信息技术有限公司 | Business processing method, device and system based on Vitess architecture |
| CN113312351A (en) * | 2021-06-01 | 2021-08-27 | 北京沃东天骏信息技术有限公司 | Data processing method and device |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111552637B (en) | 2023-05-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9785521B2 (en) | Fault tolerant architecture for distributed computing systems | |
| US9606880B2 (en) | Information processing apparatus, information processing system, and control method therefor | |
| CN108287769B (en) | Information processing method and device | |
| EP2723017A1 (en) | Method, apparatus and system for implementing distributed auto-incrementing counting | |
| US11438987B2 (en) | Lighting control method, system and device for NVME backboard, and medium | |
| CN112199356B (en) | Fault processing method, device, server and storage medium | |
| CN111552637A (en) | Database state detection method and device, electronic equipment and storage medium thereof | |
| CN112506915A (en) | Application data management system, processing method and device and server | |
| CN109586989B (en) | State checking method, device and cluster system | |
| CN110717130B (en) | Dotting method, dotting device, dotting terminal and storage medium | |
| US11086738B2 (en) | System and method to automate solution level contextual support | |
| CN112650629B (en) | Block chain index data recovery method, device, equipment and computer storage medium | |
| CN112751782B (en) | Flow switching method, device, equipment and medium based on multi-activity data center | |
| US9031969B2 (en) | Guaranteed in-flight SQL insert operation support during an RAC database failover | |
| CN111124724B (en) | Node fault testing method and device of distributed block storage system | |
| CN110928945B (en) | Data processing method and device for database and data processing system | |
| CN115190044B (en) | Device connection state checking method, device and storage medium | |
| CN109254880B (en) | Method and device for processing database downtime | |
| CN114816914A (en) | Data processing method, equipment and medium based on Kubernetes | |
| CN115237641A (en) | Fault detection method and device, electronic equipment and readable medium | |
| CN112988442A (en) | Method and equipment for transmitting fault information in server operation stage | |
| CN111737079A (en) | Method and device for monitoring cluster network | |
| CN115914016A (en) | Cluster fault diagnosis method, device, equipment and storage medium | |
| CN117407282A (en) | Application program warning method, device, equipment, storage medium and program product | |
| CN118656307A (en) | Fault detection method, server, medium and product of baseboard management controller |
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 |