CN112671590A - Data transmission method and device, electronic equipment and computer storage medium - Google Patents
Data transmission method and device, electronic equipment and computer storage medium Download PDFInfo
- Publication number
- CN112671590A CN112671590A CN202011635298.5A CN202011635298A CN112671590A CN 112671590 A CN112671590 A CN 112671590A CN 202011635298 A CN202011635298 A CN 202011635298A CN 112671590 A CN112671590 A CN 112671590A
- Authority
- CN
- China
- Prior art keywords
- data
- success rate
- historical
- default
- sending
- 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
Landscapes
- Computer And Data Communications (AREA)
Abstract
The embodiment of the application provides a data transmission method and device, electronic equipment and a computer storage medium, and relates to the technical field of cloud computing. The method comprises the following steps: when the data production end needs to transmit service data, whether cluster switching conditions are met or not is judged based on data transmission condition information of a default client instance used by the data production end currently in a historical transmission period, and the default client instance is used for transmitting data to a default message cluster. If the cluster switching condition is met, the target standby client instance is used for sending service data to the standby message cluster corresponding to the target standby client instance; and if the cluster switching condition is not met, using a default client instance to send the service data to the default message cluster. By adopting the method, the problem of service data loss caused by the fault of the machine room where the default message cluster is positioned can be avoided.
Description
Technical Field
The present application relates to the field of cloud computing technologies, and in particular, to a data transmission method and apparatus, an electronic device, and a computer storage medium.
Background
In the existing data transmission system, a data production end can write generated service data into a message cluster, and then a data consumption end can access the message cluster to acquire the service data from the message cluster.
However, when a network failure occurs in the machine room where the message cluster is located, the data production end cannot write the service data into the message cluster, and the data consumption end cannot access the consumption cluster to obtain the service data, so that the data transmitted in the data transmission system is lost, and the service is affected.
Disclosure of Invention
An object of the embodiments of the present application is to provide a data transmission method, an apparatus, an electronic device, and a computer storage medium, so as to avoid data loss during data transmission, thereby improving the security of a data transmission system. The specific technical scheme is as follows:
in a first aspect, an embodiment of the present application provides a data transmission method, where the method is applied to a data production end in a data transmission system, where the data transmission system further includes a default message cluster and at least one standby message cluster corresponding to the data production end, the data production end includes a default client instance for transmitting data to the default message cluster and a standby client instance for transmitting data to the standby message cluster, and the standby client instances are in one-to-one correspondence with the standby message clusters; the method comprises the following steps:
when the data production end needs to transmit service data, judging whether a cluster switching condition is met or not based on data transmission condition information of a default client instance currently used by the data production end in a historical transmission period, wherein the default client instance is used for transmitting data to the default message cluster;
if the cluster switching condition is met, a target standby client instance is used for sending the service data to a standby message cluster corresponding to the target standby client instance;
and if the cluster switching condition is not met, the service data is sent to the default message cluster by using the default client instance.
In a possible implementation manner, the determining whether the cluster switching condition is satisfied based on data transmission condition information of a default client instance currently used by the data production end in a historical transmission period includes:
acquiring the sending success rate of the historical service data of the default client instance in the historical transmission period;
acquiring historical test data sending success rates of the default client instance and each standby client instance in the historical transmission period;
determining a target standby client example with the highest sending success rate of historical test data in the data production end;
if the sending success rate of the historical service data is smaller than a first preset threshold value, and the sending success rate of the historical test data of the default client example is smaller than the sending success rate of the historical test data of the target standby client example, determining that the cluster switching condition is met;
and if the sending success rate of the historical service data is greater than or equal to the first preset threshold value, or the sending success rate of the historical test data of the default client example is greater than or equal to the sending success rate of the historical test data of the target standby client example, determining that the cluster switching condition is not met.
In a possible implementation manner, the determining whether the cluster switching condition is satisfied based on data transmission condition information of a default client instance currently used by the data production end in a historical transmission period includes:
acquiring the sending success rate of the historical service data of the default client instance in the historical transmission period;
if the sending success rate of the historical service data is smaller than a first preset threshold value, determining that the cluster switching condition is met;
and if the sending success rate of the historical service data is greater than or equal to the first preset threshold, determining that the cluster switching condition is not met.
In a possible implementation manner, the obtaining a sending success rate of the historical service data of the default client instance in a historical transmission period includes:
acquiring a service success rate list of the default client instance recorded by the data production end in the historical transmission period, wherein the service success rate list comprises the success rate of sending service data to the default message cluster by the default client instance in each preset time unit which is arranged from morning to evening according to the time sequence;
calculating the average value of the success rates recorded in the service success rate list as the sending success rate of the historical service data; alternatively, the first and second electrodes may be,
calculating the average value of the success rates of the specified number of the reciprocals recorded in the service success rate list as the sending success rate of the historical service data; alternatively, the first and second electrodes may be,
and if the service success rate list is empty, determining that the historical service data sending success rate is a preset value, wherein the preset value is greater than the first preset threshold value.
In one possible implementation, the method further includes:
using the default client instance to send test data to the default message cluster in each preset time unit, and using each standby client instance to send test data to each standby message cluster respectively;
recording the success rate of sending the test data by the default client example in each preset time unit in a first test success rate list, and recording the success rate of sending the test data by the standby client example in each time unit in a second test success rate list corresponding to the standby client example aiming at each standby client example;
acquiring the sending success rate of the historical test data of the default client instance and each standby client instance in the historical transmission period, wherein the sending success rate includes:
acquiring a first test success rate list recorded by the data production end in the historical transmission period and a second test success rate list corresponding to each standby client instance;
calculating the average value of the success rates recorded in the first test success rate list in the historical transmission period, and taking the average value as the sending success rate of the historical test data of the default client example; calculating the average value of the success rates recorded in the second test success rate list aiming at the second test success rate list corresponding to each standby client example in the historical transmission period, and taking the average value as the test data sending success rate corresponding to the standby client example; alternatively, the first and second electrodes may be,
calculating the average value of the success rates of the specified number of reciprocals recorded in the first test success rate list in the historical transmission period, and taking the average value as the sending success rate of the historical test data of the default client example; and calculating the average value of the success rates of the specified number of the reciprocals recorded in the second test success rate list as the test data sending success rate corresponding to each standby client example in the historical transmission period.
In a second aspect, an embodiment of the present application provides a data transmission device, where the device is applied to a data production end in a data transmission system, where the data transmission system further includes a default message cluster and at least one standby message cluster corresponding to the data production end, the data production end includes a default client instance for transmitting data to the default message cluster and a standby client instance for transmitting data to the standby message cluster, and the standby client instances correspond to the standby message clusters one to one; the device comprises:
a judging module, configured to judge whether a cluster switching condition is met based on data transmission condition information of a default client instance currently used by the data production end in a historical transmission period when the data production end needs to transmit service data, where the default client instance is used to transmit data to the default message cluster;
a sending module, configured to send the service data to a backup message cluster corresponding to the target backup client instance by using the target backup client instance if the cluster switching condition is met; and if the cluster switching condition is not met, the service data is sent to the default message cluster by using the default client instance.
In a possible implementation manner, the determining module includes:
the obtaining submodule is used for obtaining the sending success rate of the historical service data of the default client instance in the historical transmission period; acquiring historical test data sending success rates of the default client instance and each standby client instance in the historical transmission period;
the determining submodule is used for determining a target standby client example with the highest sending success rate of the historical test data in the data production end;
the judging submodule is used for determining that the cluster switching condition is met if the sending success rate of the historical service data is smaller than a first preset threshold value and the sending success rate of the historical test data of the default client example is smaller than the sending success rate of the historical test data of the target standby client example; and if the sending success rate of the historical service data is greater than or equal to the first preset threshold value, or the sending success rate of the historical test data of the default client example is greater than or equal to the sending success rate of the historical test data of the target standby client example, determining that the cluster switching condition is not met.
In a possible implementation manner, the obtaining sub-module is specifically configured to:
acquiring a service success rate list of the default client instance recorded by the data production end in the historical transmission period, wherein the service success rate list comprises the success rate of sending service data to the default message cluster by the default client instance in each preset time unit which is arranged from morning to evening according to the time sequence;
calculating the average value of the success rates recorded in the service success rate list as the sending success rate of the historical service data; alternatively, the first and second electrodes may be,
calculating the average value of the success rates of the specified number of the reciprocals recorded in the service success rate list as the sending success rate of the historical service data; alternatively, the first and second electrodes may be,
and if the service success rate list is empty, determining that the historical service data sending success rate is a preset value, wherein the preset value is greater than the first preset threshold value.
In a third aspect, an electronic device is provided, which includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete communication with each other through the communication bus;
a memory for storing a computer program;
a processor adapted to perform the method steps of any of the above first aspects when executing a program stored in the memory.
In a fourth aspect, a storage medium is provided, in which a computer program is stored which, when being executed by a processor, carries out the method steps of any one of the above-mentioned first aspects. Wherein the storage medium is a computer-readable storage medium.
In a fifth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method steps of any of the first aspects described above.
By adopting the technical scheme, when the data production end needs to transmit the service data, whether the cluster switching condition is met or not can be judged based on the data transmission condition information of the default client instance in the historical transmission period, and if the cluster switching condition is not met, the default client instance is continuously used for sending the service data to the default message cluster; if the cluster switching condition is met, the communication between the default client instance and the default message cluster is proved to be in a problem, the message cluster is switched in time, the data production end uses the target standby client instance to send the service data to the standby message cluster instead, and the service data loss caused by the fact that the service data is continuously sent to the default message cluster when the machine room where the default message cluster is located is in a fault can be avoided.
Of course, not all advantages described above need to be achieved at the same time in the practice of any one product or method of the present application.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below.
Fig. 1 is a system framework diagram of a data transmission system provided in an embodiment of the present application;
fig. 2 is an exemplary schematic diagram of a data transmission system provided in an embodiment of the present application;
fig. 3 is a flowchart of another data transmission method provided in the embodiment of the present application;
fig. 4 is a flowchart of a method for determining whether a cluster switching condition is satisfied in a data transmission method provided in an embodiment of the present application;
fig. 5 is a schematic structural diagram of a data transmission device provided in an embodiment of the present application;
fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application.
In the prior art, when a network fault occurs in a machine room where a consumption cluster corresponding to a data production end is located, the data production end cannot send service data to the consumption cluster, which results in data loss, and then the data consumption end cannot acquire the service data from the message cluster, which will affect the service.
In order to solve the above problem, embodiments of the present application provide a data transmission method, an apparatus, an electronic device, and a storage medium.
For convenience of understanding, a data transmission system applied to an embodiment of the present application is first described, and as shown in fig. 1, the data transmission system includes: the system comprises a data production end 101, a default message cluster 102 corresponding to the data production end 101, at least one standby message cluster 103 corresponding to the data production end 101, and a data consumption end 104.
The data production end 101 includes a default client instance and at least one standby client instance, where the default client instance is used to transmit data to the default message cluster 102, and the standby client instance is used to transmit data to the standby message cluster 103. The standby client instances have a one-to-one correspondence relationship with the standby message clusters 103, for example, if there are 3 standby message clusters corresponding to the data production end 101, the data production end 101 includes 3 standby client instances, and each standby client instance is used to transmit data to one of the standby message clusters.
Similar to the data producing side 101, the data consuming side 104 also has a default client instance and at least one standby client instance, the default client instance in the data consuming side 104 is used for reading data from the default message cluster 102, and the standby client instance in the data consuming side 104 is used for reading data from the standby message cluster 103. And, each client instance in the data consumer 104 may read data to the respective corresponding message cluster at the same time.
In this embodiment of the present application, the standby message cluster 103 may also be used as a default message cluster of other data production terminals, that is, each data production terminal sends data to its corresponding default message cluster by default, and meanwhile, the default message cluster corresponding to other data production terminals may be used as its own standby message cluster.
As an example, as shown in fig. 2, the data transmission system may include: the data consumption method comprises a data production end A, a default message cluster corresponding to the data production end A, namely a kafka cluster A, a data consumption end A, a data production end B, a default message cluster corresponding to the data production end B, namely a kafka cluster B, and a data consumption end B.
The kafka cluster B may be used as a standby message cluster of the data producing end a, and similarly, the kafka cluster a may also be used as a standby message cluster of the data producing end B.
The data consuming side a may read data in the kafka cluster a and the kafka cluster B, and the data consuming side B may read data in the kafka cluster a and the kafka cluster B.
In the embodiment of the present application, different message clusters may be deployed in different computer rooms.
In combination with the data transmission system, an embodiment of the present application provides a data transmission method, where the method is applied to a data production end in the data transmission system, the data transmission system further includes a default message cluster and at least one standby message cluster corresponding to the data production end, the data production end includes a default client instance for transmitting data to the default message cluster and a standby client instance for transmitting data to the standby message cluster, and the standby client instances are in one-to-one correspondence with the standby message clusters, as shown in fig. 3, the method includes:
s301, when the data production end needs to transmit service data, whether cluster switching conditions are met is judged based on data transmission condition information of a default client instance currently used by the data production end in a historical transmission period.
Wherein the default client instance is to transmit data to the default message cluster.
If yes, i.e. if the cluster switching condition is satisfied, executing S302; if not, that is, if the cluster switching condition is not satisfied, S303 is executed.
S302, the target standby client instance is used for sending the service data to the standby message cluster corresponding to the target standby client instance.
And S303, sending the service data to the default message cluster by using the default client instance.
By adopting the technical scheme, when the data production end needs to transmit the service data, whether the cluster switching condition is met or not can be judged based on the data transmission condition information of the default client instance in the historical transmission period, and if the cluster switching condition is not met, the default client instance is continuously used for sending the service data to the default message cluster; if the cluster switching condition is met, the communication between the default client instance and the default message cluster is proved to be in a problem, the message cluster is switched in time, the data production end uses the target standby client instance to send the service data to the standby message cluster instead, and the service data loss caused by the fact that the service data is continuously sent to the default message cluster when the machine room where the default message cluster is located is in a fault can be avoided.
The data production end can record the success rate of sending the service data to the default message cluster after using the default client instance to send the service data to the default message cluster each time, and can record the success rate of sending the service data to the standby message cluster after using the standby client instance to send the service data to the standby message cluster each time.
After the data production end uses the target standby client instance to send the service data to the standby message cluster corresponding to the target standby client instance, when the service data needs to be sent next time, whether cluster switching needs to be carried out or not can be judged according to the method. If the cluster switching condition is determined to be met based on the data transmission condition information of the target standby client instance currently used by the data production end in the historical transmission period, the cluster switching condition can be switched to the default client instance to be used for sending the service data to the default message cluster.
In an implementation manner of the embodiment of the present application, for the above S301, the data transmission condition information may include a historical service data sending success rate and a historical test data sending success rate of the default client instance, and on this basis, as shown in fig. 4, in the above S301, based on the data transmission condition information of the default client instance currently used by the data production end in the historical transmission period, determining whether the cluster switching condition is satisfied, may include the following steps:
s3011, obtaining a sending success rate of historical service data of a default client instance in a historical transmission period.
The historical transmission period may be set based on actual conditions, for example, may be set to 10 seconds or 1 minute before the current time, or may be set to other values, which is not limited in this embodiment of the present application.
The sending success rate of the historical service data refers to the success rate of sending the service data to the default message cluster by the default client in the historical transmission period.
S3012, obtaining the sending success rate of the historical test data of the default client instance and each standby client instance in the historical transmission period.
The sending success rate of the historical test data of the default client instance refers to the success rate of sending the test data to the default message cluster by the default client instance in the historical transmission period. The sending success rate of the historical test data of the standby client instance in the historical transmission period refers to the success rate of sending the test data to the corresponding standby message cluster of the standby client instance in the historical transmission period.
S3013, determining the target standby client example with the highest historical test data sending success rate in the data production end.
In the case where two or more backup client instances are included in the data production side, the backup client having the highest success rate of sending the historical test data may be used as the target backup client instance.
Where the data producer includes one standby client instance, the standby client instance may be the target standby client instance.
In this embodiment of the present application, the execution sequence between S3011 and S3012-S3012 is not limited, and S3011 may be executed before or after S3012, or may be executed in parallel with S3012.
S3014, if the sending success rate of the historical service data is smaller than a first preset threshold value, and the sending success rate of the historical test data of the default client instance is smaller than the sending success rate of the historical test data of the target standby client instance, it is determined that the cluster switching condition is met.
In other words, there are two cluster switching conditions, one being: the sending success rate of the historical service data of the default client instance is smaller than a first preset threshold, and the second condition is that: and the sending success rate of the historical test data of the default client example is less than that of the target standby client example.
When the two conditions are met, cluster switching can be performed, that is, the data sending end can be switched to use the target standby client instance to send service data to the standby message cluster corresponding to the target standby client instance.
The first preset threshold may be set based on actual requirements, and may specifically be set according to an empirical value. For example, the first preset threshold may be related to the importance degree of the service to which the service data belongs, and the more important the service to which the service data belongs, the larger the value of the first preset threshold. As an example, the first preset threshold may be 0.98.
S3015, if the sending success rate of the historical service data is greater than or equal to a first preset threshold value, or the sending success rate of the historical test data of the default client instance is greater than or equal to the sending success rate of the historical test data of the target standby client instance, it is determined that the cluster switching condition is not met.
That is, when either one of the first condition and the second condition is not satisfied, the cluster switching is not performed.
By adopting the method, if the sending success rate of the historical service data of the default client example is smaller than the first threshold value, the health state of the default message cluster is proved to have problems, namely the success rate of sending the service data to the default message cluster is lower. In addition, if the sending success rate of the historical test data of the default client example is greater than or equal to the sending success rate of the historical test data of the target standby client example, it is indicated that the success rate of sending the test data to the standby message cluster corresponding to the target standby client example by the data production end is higher than the success rate of sending the test data to the default message cluster. That is to say, the health state of the standby message cluster corresponding to the target standby client instance is superior to the health state of the default message cluster, and in this case, the standby message cluster corresponding to the target standby client instance is switched to be used for sending the service data, so that the possibility that the service data is lost can be reduced, and the influence on the service is avoided.
In addition, when the data production end does not continuously send data to the default message cluster, there may be a phenomenon that the data production end only sends service data once in a historical transmission period, and the success rate of sending historical services is temporarily reduced due to network jitter and the like, and actually the health of the default message cluster is good. And the data production end can continuously send the test data to the default message cluster and the standby message cluster in the historical transmission period, so the test data sending success rate is less influenced by network jitter. Whether cluster switching is carried out or not is judged by combining the two conditions, so that the phenomenon of frequent cluster switching caused by network jitter can be avoided.
In this embodiment of the application, in S3011, the obtaining of the historical service data sending success rate of the default client instance in the historical transmission period may specifically be implemented as:
and acquiring a service success rate list of the default client instance recorded by the data production end in the historical transmission period, wherein the service success rate list comprises the success rate of sending the service data to the default message cluster by the default client instance in each preset time unit which is arranged from morning to evening according to the time sequence.
Taking the historical transmission period as 10 seconds and the preset time unit as seconds as an example, the service success rate list in 10 seconds before the current time includes [ -, -,1,0.99,0.97,0.99, -, 0.96, -, - ], where "-" indicates that no service data is sent in a preset time unit, and therefore the success rate in the time unit is null.
After the service success rate list is obtained, the embodiment of the application provides the following three ways of determining the sending success rate of the historical service data based on the service success rate list.
And in the first mode, calculating the average value of the success rates recorded in the service success rate list as the sending success rate of the historical service data.
For example, for the service success rate list [ -, -,1,0.99,0.97,0.99, -, 0.96, -, - ], the service data sending success rate obtained by calculation is: (1+0.99+0.97+0.99+ 0.96)/5-0.982.
And secondly, calculating the average value of the success rates of the specified number of the reciprocals recorded in the service success rate list as the sending success rate of the historical service data.
For example, the specified number may be 3, i.e., an average of success rates of the last 3 seconds is calculated, and the last 3 seconds is only the 3 seconds of the presence service data transmission closest to the current time. For example, for the service success rate list [ -, -,1,0.99,0.97,0.99, -, 0.96, - ], the last 3 success rates 0.97,0.99, and 0.96 may be taken, and the calculated average value is taken as the historical service data transmission success rate.
In the embodiment of the application, the success rate of the specified number of the recorded reciprocals in the service success rate list is taken to calculate the average value, so that the sending success rate of the historical service data can reflect the latest health state of the default cluster.
In the case that the service success rate list in the historical transmission period is not empty, the historical service data sending success rate can be calculated by adopting any one of the first mode and the second mode. And under the condition that the service success rate list in the historical transmission period is empty, determining the sending success rate of the historical service data in a third mode.
And in the third mode, if the service success rate list is empty, determining that the sending success rate of the historical service data is a preset value.
Wherein the preset value is larger than a first preset threshold value. For example, in the case where the first preset threshold is 0.98, the preset value is 0.98.
In the embodiment of the present application, the data production end may temporarily send the service data to the standby message cluster under the condition that the health status of the default message cluster is poor, and the data production end is still more biased to send the service data to the default message cluster under the condition that the default message cluster is available. Therefore, under the condition that the service success rate list is empty, it is indicated that the data production end does not send service data to the default message cluster in the historical transmission period, but the health state of the default message cluster is not good, at this time, the default service sending success rate is a preset threshold, and the service sending success rate threshold does not meet the cluster switching condition, so that the data can be sent to the default message cluster, the purpose that the data production end is biased to send the service data to the default message cluster is achieved, and the condition that cluster switching is performed through frequency switching is avoided.
Optionally, before the data production end sends the service data each time, it needs to determine whether the cluster switching condition is satisfied, and if the cluster switching is frequently performed, a phenomenon that the data produced by the data production end arrives at each message cluster out of the time sequence is likely to occur. For example, the data production end sends service data 1 to the default message cluster in the 1 st second, sends service data 2 to the standby message cluster in the 2 nd second, and sends service data 3 to the default message cluster in the 3 rd second. A situation may occur in which the service data 2 arrives at the standby message cluster first and the service data 1 arrives at the default message cluster later, so that the sequence in which the service data arrives at the message cluster is asynchronous with the time sequence in which the service data is generated. By the cluster switching condition provided by the embodiment of the application, the problem of asynchronous service data time sequence caused by frequent switching can be avoided.
In another embodiment of the present application, in order to obtain a success rate of sending test data, the data production end may send test data to the default message cluster and the standby message cluster, and record the success rate of sending test data, which may specifically be implemented as:
and sending test data to the default message cluster by using the default client instance in each preset time unit, and sending the test data to each standby message cluster by using each standby client instance. The success rate of sending the test data by the default client instance in each preset time unit is recorded in the first test success rate list, and the success rate of sending the test data by the standby client instance in each time unit is recorded in the second test success rate list corresponding to the standby client instance aiming at each standby client instance.
The preset time unit may be second, that is, the data production end may send the test data to the default message cluster using the default client instance every second, and send the test data to the standby client instance using the standby client instance every second.
In an embodiment of the present application, the default message cluster and the standby message cluster may both be kafka clusters, a topic (topic) of the kafka cluster may include a plurality of partitions, and the data production end sends test data covering the plurality of partitions to the default message cluster and the standby message cluster every second.
For example, if the subject of the default message cluster includes 6 partitions, the data producer sends test data covering 6 partitions to the default message cluster every second using the default client instance.
The data production end also records the sending success rate of the test data by taking seconds as a unit. For example, after the data production end uses the default client instance to send the test data to the default message cluster at 10:00:01, the success rate of sending the test data to the default message cluster at 10:00:01 may be recorded in the first test success rate list, and if the test data of one second covers 6 partitions of the default message cluster, the success rate corresponding to 10:00:01 is the success rate of sending the test data to the 6 partitions. For example, if the test data is successfully transmitted to the 6 partitions, the success rate corresponding to 10:00:01 is 1.
The data production end can use the standby client example to send the test data to the standby message cluster by adopting the same method, and the success rate of sending the test data per second is recorded in a second test success rate list corresponding to the standby client example.
It will be appreciated that each alternate client instance corresponds to a second list of test success rates. For example, backup client instance a corresponds to backup message cluster a and backup client instance B corresponds to backup message cluster B.
The data production end uses the standby client instance a to send test data to the standby message cluster a every second, and records in a second test success rate list corresponding to the standby client instance a: and the standby client A sends the success rate of the test data to the standby message cluster A every second.
Similarly, the data production end uses the standby client instance B to send test data to the standby message cluster B every second, and records in a second test success rate list corresponding to the standby client instance B: and the standby client example B sends the success rate of the test data to the standby message cluster B every second.
On the basis, the step S3012 of obtaining the sending success rate of the historical test data of the default client instance and each standby client instance in the historical transmission period includes:
and acquiring a first test success rate list recorded by the data production end in a historical transmission period and a second test success rate list corresponding to each standby client instance.
The historical transmission period may be preset according to actual conditions, for example, the historical transmission period may be 10 seconds before the current time. Then, the data production end may obtain a first test success rate list recorded within 10 seconds before the current time of the recording, and a second test success rate list corresponding to each backup client instance recorded within 10 seconds before the current time.
After the first test success rate list and the second test success rate list in the historical transmission period are obtained, the historical test data sending success rate of the default client example and the historical test data sending success rate of each standby client example can be determined in the following one or two ways.
Calculating the average value of the success rates recorded in a first test success rate list in a historical transmission period, and taking the average value as the sending success rate of the historical test data of the default client example; and aiming at a second test success rate list corresponding to each standby client example in the historical transmission period, calculating the average value of the success rates recorded in the second test success rate list, and taking the average value as the test data sending success rate corresponding to the standby client example.
For example, if the historical transmission period is 10 seconds before the current time, the list of the service success rates recorded within 10 seconds before the current time is [ -, -,1,0.99,0.97,0.99, -, 0.96, -, - ], and the first test success rate list recorded within 10 seconds before the current time is [0.98,1,1,0.99,0.97,0.99,1, 0.96, 1, 1], the comparison shows that the success rate at some time in the service success rate list is null, while the success rate recorded in the first test success rate list is more comprehensive, therefore, the first test success rate list can more comprehensively reflect the health state of the default message cluster in the historical transmission period, and the historical service data sending success rate and the historical test data sending success rate are integrated to judge whether the cluster switching condition is met, so that the cluster switching can be more accurately carried out.
Calculating the average value of the success rates of the specified number of reciprocals recorded in the first test success rate list in the historical transmission period, and taking the average value as the sending success rate of the historical test data of the default client example; and aiming at a second test success rate list corresponding to each standby client example in the historical transmission period, calculating the average value of the success rates of the specified number of reciprocals recorded in the second test success rate list, and taking the average value as the test data sending success rate corresponding to the standby client example.
For example, if the historical transmission period is 10 seconds before the current time, the list of service success rates recorded 10 seconds before the current time is [ -, -,1,0.99, -, 0.97,0.99,0.96, -, - ], and the first list of test success rates recorded 10 seconds before the current time is [0.98,1,1,0.99,0.97,0.99,1, 0.96, 1,1 ]. If the specified number of the last data is 3, calculating the sending success rate of the historical service data according to the success rate from the last 3 seconds to the last 5 seconds in the service success rate list, and if network jitter occurs in the 3 seconds, the calculated sending success rate of the historical service data cannot accurately reflect the real health state of the default message cluster. At this time, the sending success rate of the historical test data of the default client example is calculated according to the last 3 seconds of success rate in the first test success rate list, and the sending success rate of the historical test data can relatively accurately reflect the health state of the default message cluster. Therefore, the sending success rate of the historical service data and the sending success rate of the historical test data are integrated to judge whether the cluster switching condition is met, the cluster switching can be accurately carried out, the influence caused by network jitter is reduced, and the cluster can be prevented from being frequently switched.
If the service data sending success rate of the default client instance is determined in the above embodiment by the first method, the test data sending success rate of the default client instance and the test data sending success rate of the standby client instance are also determined in the first method.
If the service data sending success rate of the default client instance is determined in the above embodiment by the second method, the test data sending success rate of the default client instance and the test data sending success rate of the standby client instance are also determined in the second method.
If the service data sending success rate of the default client instance is determined in the third manner in the above embodiment, the test data sending success rate of the default client instance and the test data sending success rate of the standby client instance may be determined in the first manner or the second manner.
In an implementation manner of the embodiment of the present application, for the above S301, the data transmission condition information may include a historical service data sending success rate of the default client instance, and on this basis, in the above S301, based on the data transmission condition information of the default client instance currently used by the data production end in the historical transmission period, it is determined whether the cluster switching condition is satisfied, and the determination may be implemented as:
acquiring the sending success rate of historical service data of a default client instance in a historical transmission period;
if the sending success rate of the historical service data is smaller than a first preset threshold value, determining that the cluster switching condition is met;
and if the sending success rate of the historical service data is greater than or equal to the first preset threshold, determining that the cluster switching condition is not met.
By adopting the embodiment of the application, under the condition that the network environment of the data transmission system is stable, the method for judging whether the cluster switching condition is met is simpler and more efficient.
In the embodiment of the application, the data production end may send the service data to different message clusters at different times, and the data consumption end may read the service data from a plurality of message clusters at the same time.
Based on the same inventive concept, the embodiment of the application also provides a data transmission device, which is applied to a data production end in a data transmission system, wherein the data transmission system further comprises a default message cluster and at least one standby message cluster corresponding to the data production end, the data production end comprises a default client instance for transmitting data to the default message cluster and a standby client instance for transmitting data to the standby message cluster, and the standby client instances are in one-to-one correspondence with the standby message clusters; as shown in fig. 5, the apparatus includes:
a determining module 501, configured to determine whether a cluster switching condition is met based on data transmission condition information of a default client instance currently used by a data production end in a historical transmission period when the data production end needs to transmit service data, where the default client instance is used to transmit data to a default message cluster;
a sending module 502, configured to send service data to a backup message cluster corresponding to a target backup client instance by using the target backup client instance if a cluster switching condition is met; and if the cluster switching condition is not met, using a default client instance to send the service data to the default message cluster.
Optionally, the determining module 501 includes:
the acquisition submodule is used for acquiring the sending success rate of the historical service data of the default client instance in the historical transmission period; acquiring historical test data sending success rates of a default client instance and each standby client instance in a historical transmission period;
the determining submodule is used for determining a target standby client example with the highest sending success rate of the historical test data in the data production end;
the judging submodule is used for determining that cluster switching conditions are met if the sending success rate of the historical service data is smaller than a first preset threshold value and the sending success rate of the historical test data of the default client example is smaller than the sending success rate of the historical test data of the target standby client example; and if the sending success rate of the historical service data is greater than or equal to a first preset threshold value, or the sending success rate of the historical test data of the default client example is greater than or equal to the sending success rate of the historical test data of the target standby client example, determining that the cluster switching condition is not met.
Optionally, the determining module 501 includes:
the acquisition submodule is used for acquiring the sending success rate of the historical service data of the default client instance in the historical transmission period;
the judging submodule is used for determining that cluster switching conditions are met if the sending success rate of the historical service data is smaller than a first preset threshold; and if the sending success rate of the historical service data is greater than or equal to a first preset threshold value, determining that the cluster switching condition is not met.
Optionally, the obtaining sub-module is specifically configured to:
acquiring a service success rate list of a default client instance recorded by a data production end in a historical transmission period, wherein the service success rate list comprises the success rate of sending service data to a default message cluster by the default client instance in each preset time unit which is arranged from morning to evening according to time sequence;
calculating the average value of the success rates recorded in the service success rate list as the sending success rate of the historical service data; alternatively, the first and second electrodes may be,
calculating the average value of the success rates of the specified number of the reciprocals recorded in the service success rate list as the sending success rate of the historical service data; alternatively, the first and second electrodes may be,
and if the service success rate list is empty, determining that the historical service data sending success rate is a preset value, wherein the preset value is greater than a first preset threshold value.
Optionally, the apparatus further comprises: and a recording module.
A sending module 502, configured to send test data to the default message cluster using the default client instance in each preset time unit, and send test data to each backup message cluster using each backup client instance respectively;
the recording module is used for recording the success rate of sending the test data by the default client example in each preset time unit in the first test success rate list, and recording the success rate of sending the test data by the standby client example in each time unit in a second test success rate list corresponding to the standby client example aiming at each standby client example;
an acquisition submodule, specifically configured to:
acquiring a first test success rate list recorded by a data production end in a historical transmission period and a second test success rate list corresponding to each standby client example;
calculating the average value of the success rates recorded in the first test success rate list in the historical transmission period, and taking the average value as the sending success rate of the historical test data of the default client example; aiming at a second test success rate list corresponding to each standby client example in a historical transmission period, calculating the average value of the success rates recorded in the second test success rate list, and taking the average value as the test data sending success rate corresponding to the standby client example; alternatively, the first and second electrodes may be,
calculating the average value of the success rates of the specified number of reciprocals recorded in the first test success rate list in the historical transmission period, and taking the average value as the sending success rate of the historical test data of the default client example; and aiming at a second test success rate list corresponding to each standby client example in the historical transmission period, calculating the average value of the success rates of the specified number of reciprocals recorded in the second test success rate list, and taking the average value as the test data sending success rate corresponding to the standby client example.
The embodiment of the present application further provides an electronic device, as shown in fig. 6, which includes a processor 601, a communication interface 602, a memory 603, and a communication bus 604, where the processor 601, the communication interface 602, and the memory 603 complete mutual communication through the communication bus 604,
a memory 603 for storing a computer program;
the processor 601 is configured to implement any one of the above-described embodiments of the data transmission method applied to the data producing side and the data transmission method applied to the data consuming side when executing the program stored in the memory 603.
The communication bus mentioned in the above terminal may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The communication bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.
The communication interface is used for communication between the terminal and other equipment.
The Memory may include a Random Access Memory (RAM) or a non-volatile Memory (non-volatile Memory), such as at least one disk Memory. Optionally, the memory may also be at least one memory device located remotely from the processor.
The Processor may be a general-purpose Processor, and includes a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, a discrete Gate or transistor logic device, or a discrete hardware component.
In yet another embodiment provided by the present application, there is also provided a computer-readable storage medium having stored therein instructions, which, when run on a computer, cause the computer to perform any of the method steps of the above-described data transmission method embodiments.
In a further embodiment provided by the present application, there is also provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform any of the method steps of the above-described data transmission method embodiments.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It is noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
All the embodiments in the present specification are described in a related manner, and the same and similar parts among the embodiments may be referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the embodiments of the apparatus and the electronic device, since they are substantially similar to the embodiments of the method, the description is simple, and the relevant points can be referred to only in the partial description of the embodiments of the method.
The above description is only for the preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application are included in the protection scope of the present application.
Claims (10)
1. A data transmission method is characterized in that the method is applied to a data production end in a data transmission system, the data transmission system further comprises a default message cluster and at least one standby message cluster corresponding to the data production end, the data production end comprises a default client instance used for transmitting data to the default message cluster and a standby client instance used for transmitting data to the standby message cluster, and the standby client instances are in one-to-one correspondence with the standby message clusters; the method comprises the following steps:
when the data production end needs to transmit service data, judging whether a cluster switching condition is met or not based on data transmission condition information of a default client instance currently used by the data production end in a historical transmission period, wherein the default client instance is used for transmitting data to the default message cluster;
if the cluster switching condition is met, a target standby client instance is used for sending the service data to a standby message cluster corresponding to the target standby client instance;
and if the cluster switching condition is not met, the service data is sent to the default message cluster by using the default client instance.
2. The method of claim 1, wherein determining whether a cluster switching condition is satisfied based on data transmission condition information of a default client instance currently used by the data production side in a historical transmission period comprises:
acquiring the sending success rate of the historical service data of the default client instance in the historical transmission period;
acquiring historical test data sending success rates of the default client instance and each standby client instance in the historical transmission period;
determining a target standby client example with the highest sending success rate of historical test data in the data production end;
if the sending success rate of the historical service data is smaller than a first preset threshold value, and the sending success rate of the historical test data of the default client example is smaller than the sending success rate of the historical test data of the target standby client example, determining that the cluster switching condition is met;
and if the sending success rate of the historical service data is greater than or equal to the first preset threshold value, or the sending success rate of the historical test data of the default client example is greater than or equal to the sending success rate of the historical test data of the target standby client example, determining that the cluster switching condition is not met.
3. The method of claim 1, wherein determining whether a cluster switching condition is satisfied based on data transmission condition information of a default client instance currently used by the data production side in a historical transmission period comprises:
acquiring the sending success rate of the historical service data of the default client instance in the historical transmission period;
if the sending success rate of the historical service data is smaller than a first preset threshold value, determining that the cluster switching condition is met;
and if the sending success rate of the historical service data is greater than or equal to the first preset threshold, determining that the cluster switching condition is not met.
4. The method according to claim 2 or 3, wherein obtaining the sending success rate of the historical service data of the default client instance in the historical transmission period comprises:
acquiring a service success rate list of the default client instance recorded by the data production end in the historical transmission period, wherein the service success rate list comprises the success rate of sending service data to the default message cluster by the default client instance in each preset time unit which is arranged from morning to evening according to the time sequence;
calculating the average value of the success rates recorded in the service success rate list as the sending success rate of the historical service data; alternatively, the first and second electrodes may be,
calculating the average value of the success rates of the specified number of the reciprocals recorded in the service success rate list as the sending success rate of the historical service data; alternatively, the first and second electrodes may be,
and if the service success rate list is empty, determining that the historical service data sending success rate is a preset value, wherein the preset value is greater than the first preset threshold value.
5. The method of claim 2, further comprising:
using the default client instance to send test data to the default message cluster in each preset time unit, and using each standby client instance to send test data to each standby message cluster respectively;
recording the success rate of sending the test data by the default client example in each preset time unit in a first test success rate list, and recording the success rate of sending the test data by the standby client example in each time unit in a second test success rate list corresponding to the standby client example aiming at each standby client example;
acquiring the sending success rate of the historical test data of the default client instance and each standby client instance in the historical transmission period, wherein the sending success rate includes:
acquiring a first test success rate list recorded by the data production end in the historical transmission period and a second test success rate list corresponding to each standby client instance;
calculating the average value of the success rates recorded in the first test success rate list in the historical transmission period, and taking the average value as the sending success rate of the historical test data of the default client example; calculating the average value of the success rates recorded in the second test success rate list aiming at the second test success rate list corresponding to each standby client example in the historical transmission period, and taking the average value as the test data sending success rate corresponding to the standby client example; alternatively, the first and second electrodes may be,
calculating the average value of the success rates of the specified number of reciprocals recorded in the first test success rate list in the historical transmission period, and taking the average value as the sending success rate of the historical test data of the default client example; and calculating the average value of the success rates of the specified number of the reciprocals recorded in the second test success rate list as the test data sending success rate corresponding to each standby client example in the historical transmission period.
6. A data transmission device is characterized in that the device is applied to a data production end in a data transmission system, the data transmission system further comprises a default message cluster and at least one standby message cluster corresponding to the data production end, the data production end comprises a default client instance used for transmitting data to the default message cluster and a standby client instance used for transmitting data to the standby message cluster, and the standby client instances are in one-to-one correspondence with the standby message clusters; the device comprises:
a judging module, configured to judge whether a cluster switching condition is met based on data transmission condition information of a default client instance currently used by the data production end in a historical transmission period when the data production end needs to transmit service data, where the default client instance is used to transmit data to the default message cluster;
a sending module, configured to send the service data to a backup message cluster corresponding to the target backup client instance by using the target backup client instance if the cluster switching condition is met; and if the cluster switching condition is not met, the service data is sent to the default message cluster by using the default client instance.
7. The apparatus of claim 6, wherein the determining module comprises:
the obtaining submodule is used for obtaining the sending success rate of the historical service data of the default client instance in the historical transmission period; acquiring historical test data sending success rates of the default client instance and each standby client instance in the historical transmission period;
the determining submodule is used for determining a target standby client example with the highest sending success rate of the historical test data in the data production end;
the judging submodule is used for determining that the cluster switching condition is met if the sending success rate of the historical service data is smaller than a first preset threshold value and the sending success rate of the historical test data of the default client example is smaller than the sending success rate of the historical test data of the target standby client example; and if the sending success rate of the historical service data is greater than or equal to the first preset threshold value, or the sending success rate of the historical test data of the default client example is greater than or equal to the sending success rate of the historical test data of the target standby client example, determining that the cluster switching condition is not met.
8. The apparatus according to claim 7, wherein the obtaining sub-module is specifically configured to:
acquiring a service success rate list of the default client instance recorded by the data production end in the historical transmission period, wherein the service success rate list comprises the success rate of sending service data to the default message cluster by the default client instance in each preset time unit which is arranged from morning to evening according to the time sequence;
calculating the average value of the success rates recorded in the service success rate list as the sending success rate of the historical service data; alternatively, the first and second electrodes may be,
calculating the average value of the success rates of the specified number of the reciprocals recorded in the service success rate list as the sending success rate of the historical service data; alternatively, the first and second electrodes may be,
and if the service success rate list is empty, determining that the historical service data sending success rate is a preset value, wherein the preset value is greater than the first preset threshold value.
9. An electronic device is characterized by comprising a processor, a communication interface, a memory and a communication bus, wherein the processor and the communication interface are used for realizing mutual communication by the memory through the communication bus;
a memory for storing a computer program;
a processor for implementing the method steps of any one of claims 1 to 5 when executing a program stored in the memory.
10. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the method steps of any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011635298.5A CN112671590B (en) | 2020-12-31 | 2020-12-31 | Data transmission method and device, electronic equipment and computer storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011635298.5A CN112671590B (en) | 2020-12-31 | 2020-12-31 | Data transmission method and device, electronic equipment and computer storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112671590A true CN112671590A (en) | 2021-04-16 |
| CN112671590B CN112671590B (en) | 2023-01-20 |
Family
ID=75413329
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011635298.5A Active CN112671590B (en) | 2020-12-31 | 2020-12-31 | Data transmission method and device, electronic equipment and computer storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112671590B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115515184A (en) * | 2022-11-04 | 2022-12-23 | 北京众森信和科技有限公司 | Service data sending method |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050160305A1 (en) * | 2004-01-09 | 2005-07-21 | Kenichi Soejima | Information processing system, information processing apparatus, and control method for information processing system |
| CN107451147A (en) * | 2016-05-31 | 2017-12-08 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus of kafka clusters switching at runtime |
| CN108322358A (en) * | 2017-12-15 | 2018-07-24 | 北京奇艺世纪科技有限公司 | Strange land distributed message transmission, processing, consuming method and device mostly living |
| CN111917846A (en) * | 2020-07-19 | 2020-11-10 | 中信银行股份有限公司 | Kafka cluster switching method, device and system, electronic equipment and readable storage medium |
-
2020
- 2020-12-31 CN CN202011635298.5A patent/CN112671590B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050160305A1 (en) * | 2004-01-09 | 2005-07-21 | Kenichi Soejima | Information processing system, information processing apparatus, and control method for information processing system |
| CN107451147A (en) * | 2016-05-31 | 2017-12-08 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus of kafka clusters switching at runtime |
| CN108322358A (en) * | 2017-12-15 | 2018-07-24 | 北京奇艺世纪科技有限公司 | Strange land distributed message transmission, processing, consuming method and device mostly living |
| CN111917846A (en) * | 2020-07-19 | 2020-11-10 | 中信银行股份有限公司 | Kafka cluster switching method, device and system, electronic equipment and readable storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115515184A (en) * | 2022-11-04 | 2022-12-23 | 北京众森信和科技有限公司 | Service data sending method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112671590B (en) | 2023-01-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110213068B (en) | Message middleware monitoring method and related equipment | |
| CN111585867B (en) | Message processing method and device, electronic equipment and readable storage medium | |
| CN108737132B (en) | Alarm information processing method and device | |
| US20200250019A1 (en) | Method, device and computer program product for monitoring access request | |
| CN111046310A (en) | Page processing method, device, server and computer readable storage medium | |
| US20160094392A1 (en) | Evaluating Configuration Changes Based on Aggregate Activity Level | |
| CN113590429A (en) | Server fault diagnosis method and device and electronic equipment | |
| CN113485649A (en) | Data storage method, system, device, medium and electronic equipment | |
| CN111147310A (en) | Log tracking processing method, device, server and medium | |
| CN111562884A (en) | Data storage method and device and electronic equipment | |
| CN112671590B (en) | Data transmission method and device, electronic equipment and computer storage medium | |
| CN110069217B (en) | Data storage method and device | |
| CN117459536A (en) | Resource distribution method, cloud server, device, electronic equipment and storage medium | |
| CN112653736A (en) | Parallel source returning method and device and electronic equipment | |
| CN110955587A (en) | Method and device for determining equipment to be replaced | |
| CN108234658B (en) | Method and device for sensing health condition of server cluster and server | |
| US10096029B1 (en) | System, method, and computer program for proactively identifying and addressing customer needs | |
| CN112769643B (en) | Resource scheduling method and device, electronic equipment and storage medium | |
| US20180123866A1 (en) | Method and apparatus for determining event level of monitoring result | |
| CN113835905A (en) | Message queue load balancing method and device, electronic equipment and medium | |
| CN110113187B (en) | Configuration updating method and device, configuration server and configuration system | |
| CN111400327B (en) | Data synchronization method and device, electronic equipment and storage medium | |
| CN111143526B (en) | Method and device for generating and controlling configuration information of counsel service control | |
| CN113568781A (en) | Database error processing method and device and database cluster access system | |
| CN111291127A (en) | Data synchronization method, device, server and storage medium |
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 |