CN112769889B - Method, device, storage medium and electronic device for pushing service data - Google Patents

Abstract

Embodiments of the present invention provide a method, device, storage medium, and electronic device for pushing service data. The method includes: obtaining the operating status of the first node when it is determined that the target service data needs to be pushed to the receiving node, and then When the first node is in the first operating state, the target service data is pushed to the receiving node, and when the first node is in the second operating state, the pushing of the target service data to the first node is terminated. Therefore, related technologies can be solved The push service data existing in the system is easy to cause cascading failures, and it is difficult to efficiently complete the technical problems of the push service, so as to achieve the technical effect of improving the robustness and stability of the data push service and realizing the high availability of the service.

Description

Method, device, storage medium and electronic device for pushing service data

technical field

Embodiments of the present invention relate to the communication field, and in particular, relate to a method, device, storage medium, and electronic device for pushing service data.

Background technique

WebHook is an api (application programming interface, application programming interface) concept, which is also called a reverse api, that is, the terminal does not actively send requests, and the server pushes them completely.

In the traditional service data push process, the client requests data from the server, and then the server provides the data to the client. In the WebHook mode, the server updates the required resources, and then automatically pushes them to the client as service data. The client is not a requester, but a passive receiver. This inversion of control relationship can be used to facilitate many communication requests that would otherwise require more complex requests and constant polling at the remote server.

However, when pushing data and messages in the WebHook mode, when one or more services are unavailable or exhibit high latency, it will cause cascading failures in the entire system. The retry logic of the push service will only make the situation worse and may cause the system to completely crash.

Aiming at the technical problems that the push service data in the related technology is easy to cause cascading faults and it is difficult to efficiently complete the push service, no effective solution has been proposed yet.

Contents of the invention

Embodiments of the present invention provide a service data push method, device, storage medium, and electronic device to at least solve the technical problems in the related art that push service data is likely to cause cascading failures and it is difficult to efficiently complete the push service.

According to an embodiment of the present invention, a method for pushing service data is provided, including: obtaining the running status of the first node when it is determined that the target service data needs to be pushed to the receiving node; In the case of a running state, the target service data is pushed to the receiving node, wherein the first running state is used to indicate that the service data pushed to the receiving node has a continuous abnormal number of times less than or equal to the first Threshold; when the first node is in a second operating state, stop pushing the target service data to the first node, wherein the second operating state is used to represent the service pushed to the receiving node The number of consecutive data abnormalities is greater than the first threshold.

According to another embodiment of the present invention, a device for pushing service data is provided, including: an acquisition module, configured to acquire the operating status of the first node when it is determined that target service data needs to be pushed to the receiving node; the push module , for pushing the target service data to the receiving node when the first node is in a first running state, wherein the first running state is used to represent the service pushed to the receiving node The number of consecutive data abnormalities is less than or equal to the first threshold; the termination module is configured to terminate pushing the target service data to the first node when the first node is in the second operating state, wherein the The second running state is used to indicate that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is greater than the first threshold.

According to yet another embodiment of the present invention, a computer-readable storage medium is also provided, and a computer program is stored in the computer-readable storage medium, wherein, when the computer program is executed by a processor, any one of the above-mentioned methods is implemented Steps in the examples.

According to yet another embodiment of the present invention, an electronic device is also provided, including a memory, a processor, and a computer program stored in the memory and operable on the processor, and the processor executes the computer program The program implements the steps in any one of the above method embodiments.

According to the present invention, when it is determined that the target service data needs to be pushed to the receiving node, the operation state of the first node is obtained, and when the first node is in the first operation state, the target service data is pushed to the receiving node, and the When the first node is in the second running state, the push of the target service data to the first node is terminated. Therefore, it can solve the technical problem that the push service data in the related art is likely to cause cascading failures and it is difficult to efficiently complete the push service. Helps prevent cascading failures across multiple systems, and builds a system with high fault tolerance and resilience. When key services are unavailable or have high latency, the system can still operate normally, so as to improve the robustness and stability of data push services performance and achieve high availability of services.

Description of drawings

The accompanying drawings described here are used to provide a further understanding of the present invention, and constitute a part of the application. The schematic embodiments of the present invention and their descriptions are used to explain the present invention, and do not constitute improper limitations to the present invention. In the attached picture:

Fig. 1 is a hardware structural block diagram of a mobile terminal according to an optional method for pushing service data according to an embodiment of the present invention;

Fig. 2 is a schematic flow diagram of an optional method for pushing service data according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of an optional method for pushing service data according to an embodiment of the present invention;

Fig. 4 is a structural block diagram of an optional device for pushing service data according to an embodiment of the present invention;

Fig. 5 is a schematic structural diagram of an optional electronic device according to an embodiment of the present invention.

detailed description

Embodiments of the present invention will be described in detail below with reference to the drawings and in combination with the embodiments.

It should be noted that the terms "first" and "second" in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific sequence or sequence.

The method embodiments provided in the embodiments of this application can be executed in mobile terminals, computer terminals or similar computing devices. Taking running on a mobile terminal as an example, Fig. 1 is a block diagram of a hardware structure of a mobile terminal according to a method for pushing service data according to an embodiment of the present invention. As shown in FIG. 1, the mobile terminal may include one or more (only one is shown in FIG. 1) processors 102 (processors 102 may include but not limited to processing devices such as microprocessor MCU or programmable logic device FPGA, etc.) and a memory 104 for storing data, wherein the above-mentioned mobile terminal may also include a transmission device 106 and an input and output device 108 for communication functions. Those of ordinary skill in the art can understand that the structure shown in Figure 1 is only for illustration, and it does not limit the structure of the above-mentioned mobile terminal. For example, the mobile terminal may also include more or fewer components than those shown in FIG. 1, or have a different configuration from that shown in FIG.

The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the service data push method in the embodiment of the present invention, and the processor 102 runs the computer program stored in the memory 104, thereby Executing various functional applications and data processing is to realize the above-mentioned method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory that is remotely located relative to the processor 102, and these remote memories may be connected to the mobile terminal through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device 106 is used to receive or transmit data via a network. The specific example of the above-mentioned network may include a wireless network provided by the communication provider of the mobile terminal. In one example, the transmission device 106 includes a Network Interface Controller (NIC for short), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 may be a radio frequency (Radio Frequency, referred to as RF) module, which is used to communicate with the Internet in a wireless manner.

In this embodiment, a method for pushing service data running on a mobile terminal, a computer terminal or a similar computing device is provided. FIG. 2 is a schematic flowchart of an optional method for pushing service data according to an embodiment of the present invention , as shown in Figure 2, the process includes the following steps:

S202, when it is determined that the target service data needs to be pushed to the receiving node, obtain the running status of the first node;

S204. When the first node is in the first operating state, push the target service data to the receiving node, wherein the first operating state is used to indicate that the service data pushed to the receiving node has a continuous abnormal number of times less than or equal to the first threshold;

S206. When the first node is in the second operating state, stop pushing the target service data to the first node, where the second operating state is used to indicate that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is greater than the first threshold .

Wherein, the execution subject of the above steps may be a base station, a terminal, etc., but is not limited thereto.

Optionally, in this embodiment, the above-mentioned receiving nodes may include but not limited to one or more, which may be pre-configured by staff during the process of setting up the above-mentioned service push system.

Optionally, in this embodiment, the above target service data may correspond to one receiving node, or the same target service data may correspond to multiple receiving nodes.

Optionally, in this embodiment, the above-mentioned first node may include, but is not limited to, a circuit breaker controlled in the form of an application program.

Optionally, in this embodiment, the running state of the above-mentioned first node may include but not limited to open (open) state, closed (close) state, half-open (halfopen) state, etc., which can be determined by the staff according to the application scenario or The type of service to be pushed by the server is pre-configured.

Optionally, in this embodiment, the above-mentioned first running state is used to indicate that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is less than or equal to the first threshold, that is, when the service data pushed to the receiving node is detected When the number of consecutive data exceptions is less than or equal to the first threshold, the operating state of the first node is determined as the first operating state, and the first threshold can be pre-configured according to the application scenario or the type of service to be pushed by the server .

Optionally, in this embodiment, the above-mentioned termination of pushing the target service data to the first node may include but not limited to termination of pushing the target service data to the first node, and may also include but not limited to termination of pushing the target service data to the receiving node. Nodes, etc., in the case of terminating the push of the target service data to the receiving node, may include but not limited to discarding the service data to be pushed, so as to avoid cascading failure problems caused by the server’s failure to push the service and improve the system’s reliability. Fault tolerance increases the resilience of the system.

The foregoing is only an example, and this embodiment does not make any specific limitations.

Optionally, in this embodiment, the above-mentioned second running status is used to indicate that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is greater than the first threshold, that is, when it is detected that the service data pushed to the receiving node continues When the number of occurrences of abnormalities is greater than the first threshold, the operating state of the first node is determined as the second operating state.

Through this embodiment, when it is determined that the target service data needs to be pushed to the receiving node, the operating state of the first node is obtained, and when the first node is in the first operating state, the target service data is pushed to the receiving node, When the first node is in the second operating state, the push of the target service data to the first node is terminated. Therefore, it can solve the technical problem that the push service data in the related art is likely to cause cascading failures and it is difficult to efficiently complete the push service. , helps prevent cascading failures across multiple systems, and builds a system with high fault tolerance and resilience. When key services are unavailable or have high latency, the system can still operate normally, improving the robustness and Stability, the technical effect of achieving high availability of services.

As an optional solution, after the target service data is pushed to the receiving node, the method further includes: detecting the number of consecutive abnormal occurrences of the service data pushed to the receiving node; When the number of consecutive abnormal occurrences of the service data pushed to the receiving node is less than or equal to a second threshold, the operating state of the first node is determined as the first operating sub-state, and the second threshold is less than the second threshold A threshold, the first operating state includes the first operating sub-state; when it is detected that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is greater than the second threshold and less than the first In the case of a threshold value, the operating state of the first node is determined as the second operating sub-state, and the first operating state includes the second operating sub-state; when the service pushed to the receiving node is detected In a case where the number of consecutive occurrences of abnormal data is greater than the first threshold, the operating state of the first node is determined as the second operating state.

Optionally, in this embodiment, the status of the above-mentioned first node is determined by whether the service data is abnormal during the process of pushing the service data before.

Optionally, in this embodiment, the above detection of the number of consecutive abnormal occurrences of the service data pushed to the receiving node can be performed by the server or the terminal. Taking the server as the execution subject as an example, during the detection process, by obtaining the last sent service The length of time spent sending the data or whether the sent service data can be used to determine whether the above-mentioned service data has an abnormality. In the case of an abnormality, record the number of abnormalities once. Next, determine that the operating state of the first node is the first operating sub-state, and determine that the operating state of the first node is the second operating sub-state when the number of consecutive abnormal occurrences is greater than the second threshold and less than the first threshold.

For example, the above-mentioned second threshold can be configured as 0, that is, when no abnormality occurs continuously, the state of the first node is configured as the above-mentioned first running sub-state, and when an abnormality occurs once, the state of the first node is configured as It is the above-mentioned second running sub-state.

Through this embodiment, the number of consecutive abnormal occurrences of the service data pushed to the receiving node is detected; when it is detected that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is less than or equal to the second threshold, the first node’s The running state is determined as the first running sub-state, the second threshold is less than the first threshold, and the first running state includes the first running sub-state; when it is detected that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is greater than the second threshold, and In the case of less than the first threshold, the operating state of the first node is determined as the second operating sub-state, and the first operating state includes the second operating sub-state; when it is detected that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is greater than In the case of the first threshold, the operating state of the first node is determined as the second operating state, and different operating states of the first node are determined for different abnormal times, so as to solve the robustness and stability problems of the data push service, and then, It can solve the technical problems that the push service data in the related technology is easy to cause cascading failures and it is difficult to complete the push service efficiently. It helps to prevent cascading failures across multiple systems and build a system with high fault tolerance and flexibility. When critical services are unavailable or have high latency, the system can still operate normally, achieving the technical effect of improving service availability.

As an optional solution, after obtaining the running state of the first node, the method further includes: when the first node is in the second running state, pushing predetermined data to the receiving node ; Detect whether the predetermined data pushed to the receiving node is abnormal; when it is determined that the predetermined data pushed to the receiving node is not abnormal, adjust the state of the first node to the first Running state: when it is determined that the predetermined data pushed to the receiving node is abnormal, maintaining the state of the first node as the second running state.

Optionally, in this embodiment, the aforementioned predetermined data may include but not limited to the above-mentioned service data to be pushed obtained when the aforementioned first node is in the second running state, and may also include but not limited to Test data to detect whether anomalies occur.

For example, it may include but not limited to configuring the above predetermined data as single-byte data to test whether the current service push process is normal, and may also include but not limited to using part or all of the service data to be pushed to test the current Whether the process of service push is normal.

When some or all of the service data to be pushed is used as the predetermined data, once the detection result shows that no abnormality occurs, the state of the first node can be adjusted to the first running state, and the sending of the service data can be completed. It is used in less cases, and can quickly push service data without affecting test efficiency.

When single-byte data is used as the predetermined data, once the detection result shows that no abnormality occurs, the state of the first node can be adjusted to the first running state, and continue to send subsequent service data to be pushed. The above scheme can be used in the service data Used in many cases, it can speed up the test efficiency and avoid cascading failures.

Through this embodiment, when the first node is in the second operating state, push the scheduled data to the receiving node; detect whether the scheduled data pushed to the receiving node is abnormal; In case of abnormality, adjust the state of the first node to the first operating state; when it is determined that the scheduled data pushed to the receiving node is abnormal, maintain the state of the first node as the second operating state, therefore, the related The push service data in the technology is easy to cause cascading failures, and it is difficult to efficiently complete the technical problems of push services, which helps to prevent cascading failures across multiple systems, and builds a system with high fault tolerance and flexibility. When it is unavailable or has high latency, the system can still run normally, achieving the technical effect of improving the robustness and stability of the data push service and realizing the high availability of the service.

As an optional solution, after obtaining the running state of the first node, the method further includes: when the first node is in the second running state, pushing predetermined data to the receiving node ; Detect the number of consecutive abnormal occurrences of the predetermined data pushed to the receiving node; when it is detected that the number of consecutive abnormal occurrences of the predetermined data pushed to the receiving node is less than a third threshold, adjust the first The state of a node is the first running state; when the number of consecutive abnormal occurrences of the predetermined data pushed to the receiving node is greater than or equal to the third threshold, the state of the first node is maintained as the second operating state.

Optionally, in this embodiment, it may also include but is not limited to detecting the abnormal state of the above-mentioned predetermined data multiple times, and the above-mentioned The state of the first node is adjusted to the first running state.

For example, it may be configured such that the number of consecutive abnormal occurrences of the predetermined data is less than one time, that is, when the predetermined data does not occur continuously, the state of the first node is adjusted to the first operating state. In an abnormal situation, the state of the first node is maintained as the second running state.

It may also be configured such that the number of consecutive abnormal occurrences of the predetermined data is less than 3 times, that is, when the number of consecutive abnormal occurrences of the predetermined data is less than 3 times, the state of the first node is adjusted to the first operating state, In the case that the number of consecutive abnormal occurrences of the predetermined data is greater than or equal to 3 times, the state of the first node is maintained as the second operating state, so that the above-mentioned service push system can have a certain fault tolerance rate. , you can also try to continue to push the service. In the case that the service data to be pushed is the key service data, the scope of application of the above service pushing method can be expanded.

Through this embodiment, when the first node is in the second operating state, the scheduled data is pushed to the receiving node; the number of consecutive abnormal occurrences of the scheduled data pushed to the receiving node is detected; when the scheduled data pushed to the receiving node is detected, When the number of consecutive abnormal occurrences of the data is less than or equal to the third threshold, adjust the state of the first node to the first operating state; when the number of consecutive abnormal occurrences of the scheduled data pushed to the receiving node is greater than the third threshold, maintain The state of the first node is the second running state. Therefore, it can solve the technical problem that the push service data in the related technology is easy to cause cascading faults, and it is difficult to complete the push service efficiently, and it helps to prevent cascading across multiple systems. Faults, build a system with high fault tolerance and flexibility. When key services are unavailable or have high latency, the system can still operate normally, achieving the technical effect of improving the robustness and stability of data push services and achieving high availability of services. .

As an optional solution, when the first node is in the first running state, after pushing the target service data to the receiving node, the method further includes: acquiring and pushing the target service data When the sending duration is greater than or equal to a first duration threshold, it is determined that the service data pushed to the receiving node is abnormal.

Optionally, in this embodiment, the above-mentioned sending duration may include but not limited to active feedback from the receiving node to the execution subject of the push service, and may also include but not limited to sending an acquisition message to the above-mentioned receiving node by the execution subject of the push service, In order to make the receiving node return a message recording the sending time to the execution subject of the push service.

Optionally, in this embodiment, the above-mentioned first duration threshold can be preset by the staff according to the actual situation or the application scenario, and can also be dynamically adjusted according to the importance of the current service to be pushed or the number of services to be pushed.

Through this embodiment, the sending duration of the push target service data is obtained; when the sending duration is greater than or equal to the first duration threshold, it is determined that the service data pushed to the receiving node is abnormal. Service data is easy to cause cascading failures, and it is difficult to efficiently complete the technical problems of push services. It helps to prevent cascading failures across multiple systems, and builds a system with high fault tolerance and flexibility. When key services are unavailable or have high When there is a delay, the system can still run normally, achieving the technical effect of improving the robustness and stability of the data push service and realizing the high availability of the service.

As an optional solution, when the first node is in the first running state, after pushing the target service data to the receiving node, the method further includes: acquiring the target service data The running state of the corresponding target service, wherein the running state of the target service includes an available state and an unavailable state; when the target service is in an unavailable state, determine the target service pushed to the receiving node An exception occurred in the data.

Optionally, in this embodiment, the running status of the above-mentioned target service may include, but not limited to, active feedback from the receiving node to the executive body of the push service, and may also include but not limited to sending Obtaining a message, so that the above-mentioned receiving node returns a message recording the running status of the above-mentioned target service to the execution subject of the push service, may also include but is not limited to the server obtaining the running status of the application program associated with the above-mentioned target service to determine the above-mentioned target service Whether the data is abnormal.

Through this embodiment, the running state of the target service corresponding to the target service data is obtained, wherein the running state of the target service includes an available state and an unavailable state; when the target service is in an unavailable state, it is determined to push the Therefore, it can solve the technical problem that the push service data in the related technology is easy to cause cascading faults, and it is difficult to complete the push service efficiently, which helps to prevent cascading faults across multiple systems and build fault tolerance A system with high capability and flexibility, when the key service is unavailable or has high latency, the system can still run normally, achieving the technical effect of improving the robustness and stability of the data push service and realizing the high availability of the service.

Below in conjunction with specific examples, the present invention is further explained:

Fig. 3 is a schematic flow diagram of an optional method for pushing service data according to an embodiment of the present invention. As shown in Fig. 3, the flow includes the following steps:

1. When the data push service (corresponding to the execution subject of the aforementioned service data push method) sends data to the receiving data service A (corresponding to the aforementioned receiving node), it passes through the circuit breaker (corresponding to the aforementioned first node), If the circuit breaker of A is in the open state (corresponding to the aforementioned first running sub-state), the data is sent directly to the receiving data service A, and there is no timeout or abnormal situation when sending data, and the state of the circuit breaker is still open;

2. When the data push service sends data to the receiving data service B (corresponding to the aforementioned receiving node), it passes through the circuit breaker. If the circuit breaker of B is in the open state, the data is directly sent to the receiving data service B. When sending data In the event of a timeout or abnormality, the short circuit of B will be in the HalfOpen state (corresponding to the aforementioned second running sub-state). In the HalfOpen state, the data push to the data service B will not be affected, and only the number of abnormalities will be recorded;

3. When the data push service sends data to the data receiving service B, it passes through the circuit breaker. If the circuit breaker of B is in the HalfOpen state, the data push service sends the data to the receiving data service B. If there is no timeout or abnormal situation when sending data, the circuit breaker The state will change from the HalfOpen state to the open state;

4. When the data push service sends data to the receiving data service B, it passes through the circuit breaker. If the circuit breaker of B is in the HalfOpen state, the data push service sends it to the receiving data service B. When sending data, there is a timeout or an abnormal situation exceeding the unit time threshold, the state of the circuit breaker will change from the HalfOpen state to the Close (corresponding to the aforementioned second operating state) state;

5. When the data push service sends data to the receiving data service C (corresponding to the aforementioned receiving node), after passing through the circuit breaker, if the circuit breaker of C is in the Close state, the data push service will periodically send a piece of data to the receiving data service C ( Corresponding to the aforementioned predetermined data), if there is a timeout or abnormal situation when sending data, stop pushing data to the receiving data service C, and the state of the circuit breaker of C does not change and remains in the Close state;

6. When the data push service sends data to the receiving data service C, it passes through the circuit breaker. If the circuit breaker of C is in the Close state, the data push service will periodically send a piece of data to the receiving data service C. When sending data, there is no timeout or In an abnormal situation, the state of the C circuit breaker changes to the Open state.

Through this embodiment, it is possible to solve the problem of the robustness and stability of the data push service when the receiving data service in the WebHook mode times out or is abnormal due to various reasons, and realizes the high availability of the service.

In addition, due to the simple setting of the judgment mechanism, it can efficiently solve the problem of catastrophic cascading failures in the system in the WebHook mode, improve the fault tolerance of the system (including distributed systems) in the WebHook mode, and increase the system (including distributed systems) in the WebHook mode. Distributed system) resilience.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation. Based on such an understanding, the essence of the technical solution of the present invention or the part that contributes to the prior art can be embodied in the form of software products, and the computer software products are stored in a storage medium (such as ROM/RAM, disk, CD) contains several instructions to enable a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in various embodiments of the present invention.

In this embodiment, a device for pushing service data is also provided, which is used to implement the above embodiments and preferred implementation modes, and what has been described will not be repeated. As used below, the term "module" may be a combination of software and/or hardware that realizes a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementations in hardware, or a combination of software and hardware are also possible and contemplated.

Fig. 4 is a structural block diagram of an optional device for pushing service data according to an embodiment of the present invention. As shown in Fig. 4, the device includes:

Obtaining module 402, is used for obtaining the operating status of the first node under the situation that needs to push target service data to receiving node;

A push module 404, configured to push the target service data to the receiving node when the first node is in a first running state, wherein the first running state is used to indicate that the data is pushed to the receiving node The number of consecutive abnormal occurrences of the service data of the node is less than or equal to the first threshold;

Termination module 406, configured to terminate pushing the target service data to the first node when the first node is in a second running state, wherein the second running state is used to indicate pushing to the The number of consecutive abnormal occurrences of the service data of the receiving node is greater than the first threshold.

As an optional solution, after pushing the target service data to the receiving node, the device is further configured to: detect the number of consecutive abnormal occurrences of the service data pushed to the receiving node; In the case that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is less than or equal to the second threshold, the running state of the first node is determined as the first running sub-state, and the second threshold is less than the A first threshold, the first operating state includes the first operating sub-state; when it is detected that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is greater than the second threshold and less than the second threshold In the case of a threshold value, the operating state of the first node is determined as the second operating sub-state, and the first operating state includes the second operating sub-state; when the push to the receiving node is detected If the number of consecutive abnormal occurrences of the service data is greater than the first threshold, the operating state of the first node is determined as the second operating state.

As an optional solution, after acquiring the running state of the first node, the device is further configured to: push predetermined data to the receiving node when the first node is in the second running state node; detecting whether the predetermined data pushed to the receiving node is abnormal; when it is determined that the predetermined data pushed to the receiving node is not abnormal, adjusting the state of the first node to the second A running state: when it is determined that the predetermined data pushed to the receiving node is abnormal, maintaining the state of the first node as the second running state.

As an optional solution, after acquiring the running state of the first node, the device is further configured to: push predetermined data to the receiving node when the first node is in the second running state node; detect the number of consecutive abnormal occurrences of the predetermined data pushed to the receiving node; and adjust the The state of the first node is the first operating state; when the number of consecutive abnormal occurrences of the predetermined data pushed to the receiving node is greater than or equal to the third threshold, the state of the first node is maintained is the second operating state.

As an optional solution, when the first node is in the first running state, after pushing the target service data to the receiving node, the device is further configured to: acquire and push the target service The sending duration of data; when the sending duration is greater than or equal to a first duration threshold, it is determined that the service data pushed to the receiving node is abnormal.

As an optional solution, when the first node is in the first running state, after pushing the target service data to the receiving node, the device is further configured to: acquire the target service data The running state of the corresponding target service, wherein the running state of the target service includes an available state and an unavailable state; when the target service is in an unavailable state, determine the target to be pushed to the receiving node An exception occurred in the service data.

It should be noted that the above-mentioned modules can be realized by software or hardware. For the latter, it can be realized by the following methods, but not limited to this: the above-mentioned modules are all located in the same processor; or, the above-mentioned modules can be combined in any combination The forms of are located in different processors.

According to yet another aspect of the embodiments of the present invention, there is also provided an electronic device for implementing the above method for pushing service data, and the electronic device may be the terminal device or the server shown in FIG. 1 . This embodiment is described by taking the electronic device as a server as an example. As shown in Figure 5, the electronic device includes a memory 502 and a processor 504, the memory 502 stores a computer program, and the processor 504 is configured to execute the steps in any one of the above method embodiments through the computer program.

Optionally, in this embodiment, the foregoing electronic device may be located in at least one network device among a plurality of network devices in the computer network.

Optionally, in this embodiment, the aforementioned processor may be configured to execute the following steps through a computer program:

S1, when it is determined that the target service data needs to be pushed to the receiving node, obtain the running status of the first node;

S2. When the first node is in the first operating state, push the target service data to the receiving node, wherein the first operating state is used to indicate that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is less than or equal to the first threshold;

S3. When the first node is in the second operating state, stop pushing the target service data to the first node, wherein the second operating state is used to indicate that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is greater than the first threshold .

Optionally, those of ordinary skill in the art can understand that the structure shown in FIG. 5 is only schematic, and the electronic device can also be a smart phone (such as an Android phone, an iOS phone, etc.), a tablet computer, a handheld computer, and a mobile Internet device (Mobile Internet Devices, MID), PAD and other terminal equipment. FIG. 5 does not limit the structure of the above-mentioned electronic device and electronic equipment. For example, the electronic device may also include more or fewer components than those shown in FIG. 5 (such as a network interface, etc.), or have a configuration different from that shown in FIG. 5 .

Wherein, the memory 502 can be used to store software programs and modules, such as program instructions/modules corresponding to the service data push method and device in the embodiment of the present invention, and the processor 504 runs the software programs and modules stored in the memory 502, thereby Execute various functional applications and data processing, that is, realize the above-mentioned service data push method. Memory 502 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 502 may further include memory located remotely relative to the processor 504, and these remote memories may be connected to the terminal through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof. Wherein, the memory 502 may specifically, but is not limited to, be used for information such as target service data and the running state of the first node. As an example, as shown in FIG. 5 , the memory 502 may include, but is not limited to, the acquiring module 402, the pushing module 404, and the terminating module 406 in the pushing device of the above-mentioned service data. In addition, it may also include but not limited to other module units in the device for pushing the above service data, which will not be repeated in this example.

Optionally, the above-mentioned transmission device 506 is configured to receive or send data via a network. The specific examples of the above-mentioned network may include a wired network and a wireless network. In one example, the transmission device 506 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices and routers through a network cable so as to communicate with the Internet or a local area network. In one example, the transmission device 506 is a radio frequency (Radio Frequency, RF) module, which is used to communicate with the Internet in a wireless manner.

In addition, the above-mentioned electronic device further includes: a display 508 for displaying the above-mentioned target service data information; and a connecting bus 510 for connecting various module components in the above-mentioned electronic device.

In other embodiments, the above-mentioned terminal device or server may be a node in a distributed system, wherein the distributed system may be a block chain system, and the block chain system may be composed of the multiple nodes communicating through the network A distributed system formed by connecting in the form of . Among them, nodes can form a peer-to-peer (P2P, Peer To Peer) network, and any form of computing equipment, such as servers, terminals and other electronic devices, can become a node in the blockchain system by joining the peer-to-peer network.

Embodiments of the present invention also provide a computer-readable storage medium, in which a computer program is stored, wherein the computer program is set to execute the steps in any one of the above method embodiments when running.

In this embodiment, the above-mentioned computer-readable storage medium may be configured to store a computer program for performing the following steps:

S1, when it is determined that the target service data needs to be pushed to the receiving node, obtain the running status of the first node;

S2. When the first node is in the first operating state, push the target service data to the receiving node, wherein the first operating state is used to indicate that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is less than or equal to the first threshold;

S3. When the first node is in the second operating state, stop pushing the target service data to the first node, wherein the second operating state is used to indicate that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is greater than the first threshold .

The computer readable storage medium is also configured to store a computer program for performing the steps of:

S1, when it is determined that the target service data needs to be pushed to the receiving node, obtain the running status of the first node;

S2. When the first node is in the first operating state, push the target service data to the receiving node, wherein the first operating state is used to indicate that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is less than or equal to the first threshold;

S3. When the first node is in the second operating state, stop pushing the target service data to the first node, wherein the second operating state is used to indicate that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is greater than the first threshold .

In an exemplary embodiment, the above-mentioned computer-readable storage medium may include but not limited to: U disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM) , mobile hard disk, magnetic disk or optical disk and other media that can store computer programs.

An embodiment of the present invention also provides an electronic device, including a memory and a processor, where a computer program is stored in the memory, and the processor is configured to run the computer program to perform the steps in any one of the above method embodiments.

In an exemplary embodiment, the electronic device may further include a transmission device and an input and output device, wherein the transmission device is connected to the processor, and the input and output device is connected to the processor.

In an exemplary embodiment, the above-mentioned processor may be configured to perform the following steps through a computer program:

S1, when it is determined that the target service data needs to be pushed to the receiving node, obtain the running status of the first node;

S2. When the first node is in the first operating state, push the target service data to the receiving node, wherein the first operating state is used to indicate that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is less than or equal to the first threshold;

S3. When the first node is in the second operating state, stop pushing the target service data to the first node, wherein the second operating state is used to indicate that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is greater than the first threshold .

For specific examples in this embodiment, reference may be made to the examples described in the foregoing embodiments and exemplary implementation manners, and details will not be repeated here in this embodiment.

Obviously, those skilled in the art should understand that each module or each step of the above-mentioned present invention can be realized by a general-purpose computing device, and they can be concentrated on a single computing device, or distributed in a network formed by multiple computing devices In fact, they can be implemented in program code executable by a computing device, and thus, they can be stored in a storage device to be executed by a computing device, and in some cases, can be executed in an order different from that shown here. Or described steps, or they are fabricated into individual integrated circuit modules, or multiple modules or steps among them are fabricated into a single integrated circuit module for implementation. As such, the present invention is not limited to any specific combination of hardware and software.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention can have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the principles of the present invention shall be included within the protection scope of the present invention.

Claims (10)

1. A method for pushing service data, comprising: When it is determined that the target service data needs to be pushed to the receiving node, acquiring the running status of the first node; When the first node is in a first operating state, pushing the target service data to the receiving node, wherein the first operating state is used to indicate that the service data pushed to the receiving node occurs continuously The number of abnormalities is less than or equal to a first threshold; wherein, during the process of pushing the target service data to the receiving node, the target service data passes through the first node; When the first node is in a second operating state, stop pushing the target service data to the first node, wherein the second operating state is used to indicate that the service data pushed to the receiving node is continuous The number of abnormal occurrences is greater than the first threshold; Wherein, terminating pushing the target service data to the first node includes: terminating pushing the target service data to the receiving node; Wherein, when the pushing of the target service data to the receiving node is terminated, the target service data is discarded. 2. The method according to claim 1, wherein after pushing the target service data to the receiving node, the method further comprises: Detecting the number of consecutive abnormal occurrences of the service data pushed to the receiving node; When it is detected that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is less than or equal to the second threshold, the operation state of the first node is determined as the first operation sub-state, and the second a threshold less than the first threshold, the first operating state comprising the first operating sub-state; When it is detected that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is greater than the second threshold and less than the first threshold, determine the operating state of the first node as the second an operating substate, the first operating state including the second operating substate; In a case where it is detected that the service data pushed to the receiving node has continuously experienced abnormal times greater than the first threshold, the operating state of the first node is determined as the second operating state. 3. The method according to claim 1, characterized in that, after acquiring the running state of the first node, the method further comprises: When the first node is in the second operating state, pushing predetermined data to the receiving node; Detecting whether the predetermined data pushed to the receiving node is abnormal; When it is determined that the predetermined data pushed to the receiving node is not abnormal, adjusting the state of the first node to the first running state; In a case where it is determined that the predetermined data pushed to the receiving node is abnormal, maintaining the state of the first node as the second running state. 4. The method according to claim 1, characterized in that, after acquiring the running status of the first node, the method further comprises: When the first node is in the second operating state, pushing predetermined data to the receiving node; Detecting the number of consecutive abnormal occurrences of the predetermined data pushed to the receiving node; Adjusting the state of the first node to the first operating state when it is detected that the number of consecutive abnormal occurrences of the predetermined data pushed to the receiving node is less than a third threshold; In a case where the number of consecutive abnormal occurrences of the predetermined data pushed to the receiving node is greater than or equal to the third threshold, maintaining the state of the first node as the second running state. 5. The method according to any one of claims 1 to 4, wherein when the first node is in the first running state, after the target service data is pushed to the receiving node, The method also includes: Obtain the sending duration of pushing the target service data; In a case where the sending duration is greater than or equal to a first duration threshold, it is determined that the service data pushed to the receiving node is abnormal. 6. The method according to any one of claims 1 to 4, wherein when the first node is in the first running state, after the target service data is pushed to the receiving node, The method also includes: Acquiring the running state of the target service corresponding to the target service data, wherein the running state of the target service includes an available state and an unavailable state; When the target service is in an unavailable state, it is determined that the target service data pushed to the receiving node is abnormal. 7. A device for pushing service data, comprising: An acquisition module, configured to acquire the running status of the first node when it is determined that the target service data needs to be pushed to the receiving node; A push module, configured to push the target service data to the receiving node when the first node is in a first operating state, wherein the first operating state is used to indicate pushing to the receiving node The number of consecutive abnormal occurrences of the service data is less than or equal to the first threshold; wherein, during the process of pushing the target service data to the receiving node, the target service data passes through the first node; A terminating module, configured to terminate pushing of the target service data to the first node when the first node is in a second operating state, wherein the second operating state is used to indicate that the data is pushed to the receiving The number of consecutive abnormal occurrences of the service data of the node is greater than the first threshold; Wherein, the termination module is further configured to terminate pushing the target service data to the receiving node, and discard the target service data when the pushing of the target service data to the receiving node is terminated . 8. The device according to claim 7, wherein the device is also used for: After pushing the target service data to the receiving node, detecting the number of consecutive abnormal occurrences of the service data pushed to the receiving node; When it is detected that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is less than or equal to the second threshold, the operation state of the first node is determined as the first operation sub-state, and the second a threshold less than the first threshold, the first operating state comprising the first operating sub-state; When it is detected that the number of consecutive abnormal occurrences of the service data pushed to the receiving node is greater than the second threshold and less than the first threshold, determine the operating state of the first node as the second an operating substate, the first operating state including the second operating substate; In a case where it is detected that the service data pushed to the receiving node has continuously experienced abnormal times greater than the first threshold, the operating state of the first node is determined as the second operating state. 9. A computer-readable storage medium, characterized in that, a computer program is stored in the computer-readable storage medium, wherein when the computer program is executed by a processor, any one of claims 1 to 6 is implemented. The steps of the method. 10. An electronic device comprising a memory, a processor, and a computer program stored on the memory and operable on the processor, characterized in that the rights are realized when the processor executes the computer program The steps of the method described in any one of Claims 1 to 6.

Images