CN113254274A - Message processing method, device, storage medium and server - Google Patents

Message processing method, device, storage medium and server Download PDF

Info

Publication number
CN113254274A
CN113254274A CN202110433425.1A CN202110433425A CN113254274A CN 113254274 A CN113254274 A CN 113254274A CN 202110433425 A CN202110433425 A CN 202110433425A CN 113254274 A CN113254274 A CN 113254274A
Authority
CN
China
Prior art keywords
message
cluster
queue
message queue
production end
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.)
Pending
Application number
CN202110433425.1A
Other languages
Chinese (zh)
Inventor
罗伟
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Dami Technology Co Ltd
Original Assignee
Beijing Dami Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Beijing Dami Technology Co Ltd filed Critical Beijing Dami Technology Co Ltd
Priority to CN202110433425.1A priority Critical patent/CN113254274A/en
Publication of CN113254274A publication Critical patent/CN113254274A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/16—Error detection or correction of the data by redundancy in hardware
    • G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
    • G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
    • G06F11/2023—Failover techniques
    • G06F11/2028—Failover techniques eliminating a faulty processor or activating a spare
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/54—Interprogram communication
    • G06F9/546—Message passing systems or structures, e.g. queues
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F2209/00—Indexing scheme relating to G06F9/00
    • G06F2209/54—Indexing scheme relating to G06F9/54
    • G06F2209/548—Queue

Abstract

The application discloses a message processing method, a message processing device, a storage medium and a server, and relates to the technical field of data processing. Firstly, when monitoring that a first cluster corresponding to a message queue is unavailable, determining the first cluster as a fault cluster; then controlling the message production end to write the received message into a second cluster corresponding to the message queue; and finally, the control message consumption end extracts the messages in the message queue from the first cluster or the second cluster. The cluster failure solving speed in the message queue can be improved because the failure cluster is reserved, the message in the failure cluster can not be lost, the message production end does not need to resend the message, and the double consumption states of the failure cluster and the new cluster are realized.

Description

Message processing method, device, storage medium and server
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a message processing method, an apparatus, a storage medium, and a server.
Background
With the development of science and technology, there are more and more scenes that people use terminals, and people can use terminals to implement various functions based on servers, wherein the servers need to process messages sent by the terminals or messages requested by the terminals, so that a method for processing messages also becomes one of the important points of research of technicians in the field.
In the related art, in order to improve the efficiency of processing messages by a server, a data structure of a Message Queue (MQ) may be used to process messages, specifically, a Message Queue is first established in the server, a Message may be put into the Message Queue after a Message is produced by a production end, and a Message may be obtained from the Message Queue at any time when a Message is needed by a consumption end, where the Message Queue may be implemented in a cluster-based manner, so as to improve the stability of the Message Queue, but when a cluster fails, a new cluster needs to be manually replaced after a cluster failure is manually detected, which results in a slow speed of solving the cluster failure and a Message loss in an original cluster.
Disclosure of Invention
The application provides a message processing method, a message processing device, a storage medium and a server, which can solve the technical problems that when a cluster fails, a new cluster needs to be manually replaced after the cluster failure is manually detected, so that the cluster failure solving speed is low and the message in the original cluster is lost in the related art.
In a first aspect, the present application provides a message processing method, including:
when monitoring that a first cluster corresponding to a message queue is unavailable, determining that the first cluster is a fault cluster;
the control message production end writes the received message into a second cluster corresponding to the message queue;
and controlling the message consuming end to extract the messages in the message queue from the first cluster or the second cluster.
Optionally, the monitoring that the first cluster corresponding to the message queue is unavailable includes: when it is monitored that a message production end fails to write a message into a first cluster corresponding to a message queue, determining that the first cluster is unavailable; or acquiring the registration information of the first cluster corresponding to the message queue through the header routing information, and determining that the first cluster is unavailable when the registration information does not meet the preset registration information condition.
Optionally, before the monitoring that the first cluster corresponding to the message queue is unavailable, the method further includes: initializing a first message production end and a second message production end corresponding to a message queue, and keeping the second message production end in a hot start state, wherein the first message production end corresponds to the first cluster, and the second message production end corresponds to the second cluster; and initializing a message consumption end corresponding to the message queue.
Optionally, before the monitoring that the first cluster corresponding to the message queue is unavailable, the method further includes: and controlling the first message production end to write the received message into the first cluster corresponding to the message queue, and controlling the message consumption end to extract the message in the message queue from the first cluster.
Optionally, the controlling the message producer to write the received message into the second cluster corresponding to the message queue includes: and controlling the second message production end to write the received message into the second cluster corresponding to the message queue.
Optionally, the controlling the message consumer end to extract the message in the message queue from the first cluster or the second cluster includes: the control message consumption end determines a target cluster according to a request title corresponding to the message acquisition request; if the target cluster is the first cluster, controlling the message consumption end to extract the target message corresponding to the message acquisition request in the message queue from the first cluster; and if the target cluster is the second cluster, controlling the message consumption end to extract the target message corresponding to the message acquisition request in the message queue from the second cluster.
Optionally, the method further comprises: and acquiring the fault information of the first cluster, and reporting the fault information.
Optionally, the method further comprises: detecting whether the first cluster is available at preset time intervals;
and when the first cluster is available, controlling the message production end to write the received message into the first cluster corresponding to the message queue.
In a second aspect, the present application provides a message processing apparatus, comprising:
the monitoring module is used for determining that a first cluster corresponding to the message queue is a fault cluster when monitoring that the first cluster is unavailable;
the message production module is used for controlling the message production end to write the received message into a second cluster corresponding to the message queue;
and the message consumption module is used for controlling a message consumption end to extract the messages in the message queue from the first cluster or the second cluster.
In a third aspect, the present application provides a computer storage medium having stored thereon a plurality of instructions adapted to be loaded by a processor and to carry out the steps of the method as described above.
In a fourth aspect, the present application provides a server comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method as described above when executing the program.
The beneficial effects brought by the technical scheme provided by some embodiments of the application at least comprise:
the application provides a message processing method, which comprises the steps of firstly, determining a first cluster as a fault cluster when monitoring that the first cluster corresponding to a message queue is unavailable; then controlling the message production end to write the received message into a second cluster corresponding to the message queue; and finally, the control message consumption end extracts the messages in the message queue from the first cluster or the second cluster. The cluster failure solving speed in the message queue can be improved because the failure cluster is reserved, the message in the failure cluster can not be lost, the message production end does not need to resend the message, and the double consumption states of the failure cluster and the new cluster are realized.
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, it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative efforts.
Fig. 1 is an exemplary system architecture of a message processing method provided in an embodiment of the present application;
fig. 2 is a system interaction diagram of a message processing method according to an embodiment of the present application;
fig. 3 is a schematic flowchart of a message processing method according to another embodiment of the present application;
fig. 4 is a schematic diagram of a cluster structure according to another embodiment of the present application;
fig. 5 is a flowchart illustrating a message processing method according to another embodiment of the present application;
fig. 6 is a schematic structural diagram of a message processing apparatus according to another embodiment of the present application;
fig. 7 is a schematic structural diagram of a message processing apparatus according to another embodiment of the present application;
fig. 8 is a schematic structural diagram of a server according to an embodiment of the present application.
Detailed Description
In order to make the features and advantages of the present application more obvious and understandable, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are only a part of the embodiments of the present application, and not all the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the application, as detailed in the appended claims.
In the description of the present application, it is to be understood that the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. The specific meaning of the above terms in the present application can be understood in a specific case by those of ordinary skill in the art. Further, in the description of the present application, "a plurality" means two or more unless otherwise specified. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
The present application will be described in detail with reference to specific examples.
Fig. 1 illustrates an exemplary system architecture 100 that may be applied to the message processing method of the present application.
As shown in fig. 1, the system architecture 100 may include a user terminal 101, a server 102, and a network 103. The network 103 is used as a medium for providing a communication link between the user terminal 101 and the server 102. Network 103 may include various types of wired or wireless communication links, such as: the wired communication link includes an optical fiber, a twisted pair wire or a coaxial cable, and the Wireless communication link includes a bluetooth communication link, a Wireless-Fidelity (Wi-Fi) communication link, a microwave communication link, or the like.
The user terminal 101 may interact with the server 102 via the network 103 to receive messages from the server 102 or to send messages to the server 102. Various communication client applications may be installed on the user terminal 101, such as: data synchronization system software, drawing applications, video recording applications, video playing applications, voice acquisition applications, voice interaction applications, search-type applications, instant messaging tools, mailbox clients, social platform software, and the like.
The user terminal 101 may be hardware or software. When the user terminal 101 is hardware, it may be various electronic devices having a display screen, including but not limited to smart phones, tablet computers, laptop portable computers, desktop computers, and the like. When the user terminal 101 is software, it may be installed in the electronic device listed above. Which may be implemented as a plurality of software or software modules (e.g., for providing distributed services) or as a single software or software module, and is not particularly limited herein.
When the user terminal 101 is a hardware, a display device may be further installed thereon, and the display device may be various devices capable of implementing a display function, for example: a Cathode ray tube display (CR), a Light-emitting diode display (LED), an electronic ink panel, a Liquid Crystal Display (LCD), a Plasma Display Panel (PDP), and the like. The user may utilize the display device on the user terminal 101 to view information such as displayed text, pictures, video, etc.
The server 102 may be provided with a corresponding database, where the database is a place for storing electronic files, and the user terminal 101 may perform operations such as adding, intercepting, updating, and deleting on data in the files.
The server 102 may be a business server that provides various services. The server 102 may be hardware or software. When the server 102 is hardware, it may be implemented as a server cluster consisting of a plurality of servers. When the server 102 is software, it may be implemented as a plurality of software or software modules (e.g., to provide distributed services).
It should be understood that the number of user terminals, networks and servers in fig. 1 is merely illustrative. There may be any number of user terminals, networks, and servers, as desired for the implementation.
Referring to fig. 2, fig. 2 is a system interaction diagram of a message processing method according to an embodiment of the present application, and a system interaction process in the message processing method will be described with reference to fig. 1 and fig. 2.
S201, the user terminal sends a message writing request to the message production terminal, so that the message production terminal writes the received message into a first cluster corresponding to the message queue.
S202, when monitoring that a first cluster corresponding to the message queue is unavailable, the server determines that the first cluster is a fault cluster.
Optionally, the monitoring that the first cluster corresponding to the message queue is unavailable includes: when it is monitored that the message production end fails to write the message into the first cluster corresponding to the message queue, determining that the first cluster is unavailable; or acquiring the registration information of the first cluster corresponding to the message queue through the header routing information, and determining that the first cluster is unavailable when the registration information does not meet the preset registration information condition.
Optionally, before monitoring that the first cluster corresponding to the message queue is unavailable, the method further includes: initializing a first message production end and a second message production end corresponding to the message queue, and keeping the second message production end in a hot start state, wherein the first message production end corresponds to a first cluster, and the second message production end corresponds to a second cluster; and initializing a message consumption end corresponding to the message queue.
Optionally, before monitoring that the first cluster corresponding to the message queue is unavailable, the method further includes: and controlling the first message production end to write the received message into a first cluster corresponding to the message queue, and controlling the message consumption end to extract the message in the message queue from the first cluster.
Optionally, controlling the message producer to write the received message into the second cluster corresponding to the message queue includes: and controlling a second message production end to write the received message into a second cluster corresponding to the message queue.
S203, the server control message production end writes the received message into a second cluster corresponding to the message queue.
Optionally, the controlling the message consumer to extract the message in the message queue from the first cluster or the second cluster includes: the control message consumption end determines a target cluster according to a request title corresponding to the message acquisition request; if the target cluster is the first cluster, controlling the message consumption end to extract the target message corresponding to the message acquisition request in the message queue from the first cluster; and if the target cluster is the second cluster, controlling the message consumption end to extract the target message corresponding to the message acquisition request in the message queue from the second cluster.
S204, the user terminal sends a message acquisition request to the message consumption end so as to acquire the message in the cluster corresponding to the message queue of the message consumption end.
S205, the server controls the message consumption end to extract the message in the message queue from the first cluster or the second cluster.
Optionally, the server is further configured to acquire fault information of the first cluster, and report the fault information. Detecting whether the first cluster is available or not at preset time intervals; and when the first cluster is available, the control message production end writes the received message into the first cluster corresponding to the message queue.
In the embodiment of the application, when a first cluster corresponding to a message queue is monitored to be unavailable, the first cluster is determined to be a fault cluster; then controlling the message production end to write the received message into a second cluster corresponding to the message queue; and finally, the control message consumption end extracts the messages in the message queue from the first cluster or the second cluster. The cluster failure solving speed in the message queue can be improved because the failure cluster is reserved, the message in the failure cluster can not be lost, the message production end does not need to resend the message, and the double consumption states of the failure cluster and the new cluster are realized.
Referring to fig. 3, fig. 3 is a flowchart illustrating a message processing method according to another embodiment of the present application.
As shown in fig. 3, the message processing method includes:
s301, when monitoring that the first cluster corresponding to the message queue is unavailable, determining that the first cluster is a fault cluster.
In one Message processing embodiment, to improve the efficiency of server processing messages, messages may be processed using a data structure of Message Queues (MQs), which may be considered a "first-in-first-out" data mechanism in an underlying data structure. Specifically, a message queue is first established in the server, a message production end may be further set in the server, where the message production end is configured to place a message into the message queue, so that when a terminal or an application program in the terminal needs to send a message to the server, the message production end may be controlled to receive the message and write the message into the message queue for storage, and when an application program in another terminal or another terminal needs to obtain a message from the server, the message receiving end may be controlled to obtain a corresponding message from the message queue, where the message queue may be implemented in a cluster-based manner for ensuring stability and security of the stored message, that is, when the server stores the message in the message queue, the message queue may be formed by a plurality of storage devices to store the message, so as to prevent loss of the message and improve storage efficiency of the message, The read efficiency.
When the messages in the message queue are stored in the cluster manner, when a cluster fails, the failed cluster needs to be manually closed and a new cluster needs to be replaced after the cluster failure is manually detected, so that the cluster failure solving speed is low and the messages in the original cluster are lost. For the above technical problem, the message processing method of the present application can effectively solve the above technical problem, specifically:
in this embodiment of the present application, at least two clusters may be set in a server in advance, and when the server includes two clusters, it may be determined that the two clusters are a first cluster and a second cluster, respectively, where the first cluster may be considered as a main cluster, the second cluster may be a standby cluster, and resources or configuration of the main cluster may be higher than that of the standby cluster, so when the server stores a message in a message queue, if both the first cluster and the second cluster are available, the message may be preferentially written into the first cluster.
Further, the availability status of the cluster currently used by the message queue may be monitored, and the cluster currently used by the message queue may be determined to be the first cluster, which may be considered to be the primary cluster. When it is monitored that the first cluster corresponding to the message queue is unavailable, the first cluster is determined to be a failure cluster, and the unavailability of the first cluster at least means that the message cannot be written into the first cluster. The method for determining whether the first cluster corresponding to the message queue is available may not be limited, and the available state of the first cluster may be determined by writing the message into the state of the first cluster or reading the message from the first cluster; the attribute information of the first cluster may also be obtained, and the available state of a cluster is determined according to the attribute information.
Optionally, after determining that the first cluster is a failed cluster, the first cluster may be retained, that is, the first cluster is not shut down, and resources may be further provided for the first cluster, so that the first cluster may maintain a running state, so that messages written before the failure of the first cluster may be further stored in the first cluster, and thus the first cluster may still read messages from the first cluster although the first cluster cannot continue to write messages at this time.
S302, the control message production end writes the received message into a second cluster corresponding to the message queue.
In the embodiment of the present application, at least two clusters are set in the server in advance, so when it is monitored that the first cluster corresponding to the message queue is unavailable, that is, the first cluster is automatically monitored to be a faulty cluster, at this time, the message production end can be controlled to write the received message into the second cluster corresponding to the message queue, where the second cluster can be considered to be in an idle state, and therefore, directly switching the write cluster corresponding to the message queue from the first cluster to the second cluster does not affect the write of the current message.
Optionally, when the number of the second clusters is multiple, the operation information of each second cluster may also be obtained, where the operation information includes, but is not limited to, data occupancy, configuration use conditions, and the like, and the current operation state of each second cluster is determined according to the operation information of each second cluster, so that the second cluster with the best operation state may be determined as the target second cluster, and the message production end is controlled to write the received message into the second cluster, so as to ensure storage stability of the message in the message queue.
S303, controlling the message consuming end to extract the message in the message queue from the first cluster or the second cluster.
After the write cluster corresponding to the message queue is switched from the first cluster to the second cluster, although the second cluster may continue to receive new messages written by the message production end, the messages written by the message production end before are still stored in the first cluster, if only the message consumption end is controlled to extract the messages from the second cluster, the messages written by the message production end before cannot be extracted from the second cluster, the terminal or an application program in the terminal needs to resend the previous messages, and the message production end drops the messages into the message queue again, which may cause current operation failure of a user for the user, and bring very poor use experience to the user.
Optionally, the above step is introduced, after it is determined that the first cluster is the failure cluster, the first cluster may be controlled to keep the running state, so in this embodiment of the application, when the message consumption end is controlled to extract the message from the message queue, the message consumption end may be specifically controlled to extract the message in the message queue from the first cluster or the second cluster, that is, the message consumption end may extract the message from the first cluster or the second cluster according to needs, so that the message in the message queue is not lost, and the user does not need to resend the message, thereby improving the user experience.
Referring to fig. 4, fig. 4 is a schematic diagram of a cluster structure according to another embodiment of the present application.
As shown in fig. 4, at least one application 401 corresponds to a message production end 402, each application 401 may send a message to the message production end 402, the message production end 402 may preferentially write the message into a first cluster 404 in a message queue 403, and when it is monitored that the first cluster 404 corresponding to the message queue 403 is unavailable, determine that the first cluster 404 is a failure cluster, then may control the message production end 402 to write the received message into a second cluster 405 corresponding to the message queue 403, and finally control the message consumption end 406 to extract the message in the message queue 403 from the first cluster 404 or the second cluster 405, and the other application 401 may obtain the message from the message consumption end 406, may implement automatic discovery of cluster failure, implement intelligent traffic scheduling, quickly switch the traffic to a standby cluster, that is, the second cluster 405, and save the time for manual switching during failure, the message escape efficiency is greatly improved, and meanwhile, the risk of misoperation caused by manual modification of cluster configuration is reduced. Further, in the fault disaster recovery switching process, the user side application 401 has no perception, and the message write-in request in the cluster fault process is directly sent to the standby cluster, so that the user side is not required to resend the message write-in request, and the user experience is improved.
In the embodiment of the application, when a first cluster corresponding to a message queue is monitored to be unavailable, the first cluster is determined to be a fault cluster; then controlling the message production end to write the received message into a second cluster corresponding to the message queue; and finally, the control message consumption end extracts the messages in the message queue from the first cluster or the second cluster. The cluster failure solving speed in the message queue can be improved because the failure cluster is reserved, the message in the failure cluster can not be lost, the message production end does not need to resend the message, and the double consumption states of the failure cluster and the new cluster are realized.
Referring to fig. 5, fig. 5 is a flowchart illustrating a message processing method according to another embodiment of the present application.
As shown in fig. 5, the method includes:
s501, initializing a first message production end and a second message production end corresponding to the message queue, and keeping the second message production end in a hot start state, wherein the first message production end corresponds to a first cluster, and the second message production end corresponds to a second cluster.
It can be understood that, in the embodiment of the present application, at least two clusters may be set in the server in advance, so as to facilitate subsequent transfer of the message to the standby cluster for storage when the cluster fails, and the standby cluster may be kept in an active state in advance.
Specifically, the clusters and the message production ends in the message queue are in a corresponding relationship, so if a standby cluster is to be maintained in an active state, a first message production end and a second message production end corresponding to the message queue may be initialized, where the first message production end corresponds to the first cluster and the second message production end corresponds to the second cluster. Because the first cluster is the main cluster, the first message production end can keep the active state, and the corresponding first cluster also keeps the active state, so that the first message production end can receive the message in the following process and write the message into the main cluster corresponding to the message queue, namely the first cluster.
Furthermore, the second message producing end can be kept in a warm-start state, that is, the second message producing end is provided with the most basic resources and configuration required for keeping running, so that the power consumption consumed by keeping the second message producing end in the warm-start state is reduced. Because the second message producer is in a warm-boot state, there is no need for the second message producer to write messages to the message queue for a while, and the second message producer requires less resources and less configuration than the first message producer.
S502, initializing a message consuming end corresponding to the message queue.
After initializing the message production end, in order to facilitate the subsequent other terminals or application programs in the terminals to acquire messages from the message queue, the message consumption end corresponding to the message queue may be initialized to keep the message consumption end in an active state.
S503, controlling the first message production end to write the received message into the first cluster corresponding to the message queue, and controlling the message consumption end to extract the message in the message queue from the first cluster.
In the above step, after initializing the first message production end and the second message production end corresponding to the message queue, the first message production end may be kept in an active state, and the second message production end may be kept in a hot start state, so that when the main cluster corresponding to the message queue, that is, the first cluster, normally works, the first message production end may be controlled to write the received message into the first cluster corresponding to the message queue.
The method for controlling the first message production end to write the received message into the first cluster corresponding to the message queue may be various, and one feasible method is that the first message production end sends the message to the first message production end according to the terminal or an application program in the terminal, the first message production end determines a target cluster in the first cluster corresponding to the message queue according to a request header (topic) corresponding to the message, and then the first message production end writes the message into the target cluster.
Further, when the terminal or an application program in the terminal needs to acquire the message from the message queue, the message consuming end can be controlled to extract the message in the message queue from the first cluster. One possible way is that, when the terminal or an application program in the terminal sends a message acquisition request to the message consuming side, the message consuming side determines a request header corresponding to the message acquisition request, determines a target cluster corresponding to the first cluster of the request header, and finally extracts the message from the target cluster and sends the message to the terminal or the application program in the terminal.
S504, when it is monitored that the message production end fails to write the message into the first cluster corresponding to the message queue, determining that the first cluster is unavailable.
The above steps introduce that, under the normal working condition of the first cluster, for the message processing method in the message queue, in order to implement the automatic sending of the cluster fault, the available state of the first cluster corresponding to the message queue may be monitored, and a feasible way is that, the available state of the first cluster corresponding to the message queue may be monitored, that is, the state of the first cluster corresponding to the message queue into which the message is written by the message production end is monitored, the state of the first cluster corresponding to the message queue into which the message is written by the first message production end includes write success and write failure, when the first cluster has a fault, the first cluster cannot continue to write the message, and then the state of the first cluster corresponding to the message queue into which the message is written by the first message production end is failed, so when it is monitored that the message production end fails to write the first cluster corresponding to the message queue, it is determined that the first cluster is unavailable.
And S505, acquiring the registration information of the first cluster corresponding to the message queue through the header routing information, and determining that the first cluster is unavailable when the registration information does not meet the preset registration information condition.
It can be understood that, when the first cluster works, the first cluster registers cluster information to the registered device at regular time, where the cluster information may include cluster heartbeat information, that is, the cluster initiates a heartbeat with the registered device at a certain time interval, the registered device obtains the latest header routing information corresponding to the cluster, and determines whether the cluster is still alive according to the cluster heartbeat information in the header routing information, and when the cluster heartbeat information is abnormal, it may be determined that the cluster fails.
Therefore, the available state of the first cluster corresponding to the message queue is monitored, and another feasible way is that the registration information of the first cluster corresponding to the message queue can be obtained through the header routing information, and when the registration information does not meet the preset registration information condition, that is, when the cluster heartbeat information in the registration information is abnormal and does not meet the preset heartbeat information, the first cluster can be determined to be unavailable.
Through the two modes for monitoring the available state of the first cluster corresponding to the message queue, the automatic fault monitoring of the cluster corresponding to the message queue can be realized.
S506, when the first cluster corresponding to the message queue is monitored to be unavailable, the first cluster is determined to be a fault cluster.
For step S506, please refer to the detailed description in step S301, which is not repeated herein.
And S507, controlling a second message production end to write the received message into a second cluster corresponding to the message queue.
After determining that the first cluster is a failed cluster, the first cluster may be retained, that is, the first cluster is not shut down, and resources may be provided for the first cluster, so that the first cluster may keep a running state, so that messages written before the failure of the first cluster may be continuously stored in the first cluster, and thus the first cluster may still read messages from the first cluster although the first cluster cannot continuously write messages at this time.
Because the standby cluster, that is, the second cluster, is set in the embodiment of the present application, and the second cluster corresponds to the second message production end, the second message production end can be directly controlled to write the received message into the second cluster corresponding to the message queue. The above embodiment describes that the second message production end can be kept in a hot start state all the time, so that when the first cluster fails, the second cluster can be used to store the message without spending more time to start the standby cluster, that is, the second cluster, and the switching speed of the clusters can be greatly improved.
And S508, controlling the message consumption end to determine the target cluster according to the request header corresponding to the message acquisition request.
After the write cluster corresponding to the message queue is switched from the first cluster to the second cluster, although the second cluster may continue to receive new messages written by the message production end, the messages written by the message production end before are still stored in the first cluster, if only the message consumption end is controlled to extract the messages from the second cluster, the messages written by the message production end before cannot be extracted from the second cluster, the terminal or an application program in the terminal needs to resend the previous messages, and the message production end drops the messages into the message queue again, which may cause current operation failure of a user for the user, and bring very poor use experience to the user.
Optionally, it is introduced in the above step that after the first cluster is determined to be the failure cluster, the first cluster may be controlled to maintain the operating state, so in this embodiment of the application, when the control message consumer extracts the message from the message queue, the control message consumer may specifically control the message consumer to extract the message in the message queue from the first cluster or the second cluster.
The method for controlling the message consuming end to extract the message in the message queue from the first cluster or the second cluster may be that, first, the control message consuming end determines a target cluster according to a request header corresponding to the message acquisition request, because the message producing end determines the request header corresponding to the message when writing the message into the first cluster or the second cluster, and after the message is written into the first cluster or the second cluster, the request header corresponding to the message corresponds to the corresponding cluster, the message consuming end may determine the target cluster according to the request header corresponding to the message acquisition request, and the target cluster may be the first cluster or the second cluster.
S509, if the target cluster is the first cluster, the message consuming end is controlled to extract the target message corresponding to the message obtaining request in the message queue from the first cluster.
If the target cluster is the first cluster, the target message corresponding to the message acquisition request is written into the first cluster by representing the first message production end, and the first cluster is still reserved, so that the message consumption end can be controlled to extract the target message corresponding to the message acquisition request in the message queue from the first cluster.
And S510, if the target cluster is the second cluster, controlling the message consumption end to extract the target message corresponding to the message acquisition request in the message queue from the second cluster.
If the target cluster is the second cluster, the target message corresponding to the message acquisition request is written into the second cluster by the second message production terminal, that is, the target message is written into the second cluster after the first cluster fails, and the second cluster has message storage capacity in spite of being a standby cluster, so that the message consumption terminal can be controlled to extract the target message corresponding to the message acquisition request in the message queue from the second cluster.
And S511, acquiring the fault information of the first cluster, and reporting the fault information.
It can be understood that, in order to facilitate a manager of the cluster to know the operation state of the cluster in time, the fault information of the first cluster may be obtained after the first cluster is determined to be the fault cluster, and the fault information is reported, and the reporting mode and the specific reported device may not be limited, for example, the reporting mode may send the fault information of the first cluster to the communication device of the cluster manager in a short message manner, so that the cluster manager may know the operation state of the cluster in the first time, and may conveniently and timely troubleshoot the cluster fault.
And S512, detecting whether the first cluster is available at preset time intervals.
Optionally, because the first cluster is used as a primary cluster and has greater storage and processing capabilities for messages than a second cluster used as a standby cluster, after the first cluster is removed from the failure, the first cluster may still be used as the primary cluster corresponding to the message queue, and then, in order to switch the second cluster corresponding to the message queue to the first cluster in time, whether the first cluster is available may be detected at intervals of a preset event, where the method for detecting whether the first cluster is available may refer to step S504 and step S505, which is not described herein again.
S513, when the first cluster is available, the control message production end writes the received message into the first cluster corresponding to the message queue.
When detecting that the first cluster is available, in order to improve the message processing speed and efficiency in the message queue, the message producing end may be controlled to rewrite the received message into the first cluster corresponding to the message queue, and reserve the second cluster, so that the message consuming end may extract the message in the message queue from the first cluster or the second cluster.
In the method, when a first cluster corresponding to a message queue is monitored to be unavailable, the first cluster is determined to be a fault cluster; then controlling the message production end to write the received message into a second cluster corresponding to the message queue; and finally, the control message consumption end extracts the messages in the message queue from the first cluster or the second cluster. The cluster failure solving speed in the message queue can be improved because the failure cluster is reserved, the message in the failure cluster can not be lost, the message production end does not need to resend the message, and the double consumption states of the failure cluster and the new cluster are realized.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a message processing apparatus according to another embodiment of the present application.
As shown in fig. 6, the message processing apparatus 600 includes:
the monitoring module 610 is configured to determine that a first cluster corresponding to the message queue is a faulty cluster when it is monitored that the first cluster is unavailable.
And a message generating module 620, configured to control the message generating end to write the received message into the second cluster corresponding to the message queue.
And a message consumption module 630, configured to control the message consumption end to extract the message in the message queue from the first cluster or the second cluster.
Referring to fig. 7, fig. 7 is a schematic structural diagram of a message processing apparatus according to another embodiment of the present application.
As shown in fig. 7, the message processing apparatus 700 includes:
the production initialization module 710 is configured to initialize a first message production end and a second message production end corresponding to the message queue, and keep the second message production end in a hot start state, where the first message production end corresponds to the first cluster and the second message production end corresponds to the second cluster.
And the consumption initialization module 720 is configured to initialize a message consumption end corresponding to the message queue.
And a normal processing module 730, configured to control the first message producing end to write the received message into the first cluster corresponding to the message queue, and control the message consuming end to extract the message in the message queue from the first cluster.
The first determining module 740 is configured to determine that the first cluster is unavailable when it is monitored that the message producer fails to write a message into the first cluster corresponding to the message queue.
And a second determining module 750, configured to obtain, through the header routing information, registration information of the first cluster corresponding to the message queue, and determine that the first cluster is unavailable when the registration information does not satisfy a preset registration information condition.
The failure determining module 760 is configured to determine that a first cluster corresponding to the message queue is a failed cluster when it is monitored that the first cluster is unavailable.
The exception handling module 770 is configured to control the second message producer to write the received message into the second cluster corresponding to the message queue.
And the target cluster determining module 780 is configured to control the message consuming end to determine the target cluster according to the request header corresponding to the message obtaining request.
The first consuming module 790 is configured to, if the target cluster is the first cluster, control the message consuming end to extract the target message corresponding to the message obtaining request in the message queue from the first cluster.
The second consuming module 7100 is configured to, if the target cluster is the second cluster, control the message consuming end to extract the target message corresponding to the message obtaining request in the message queue from the second cluster.
And a fault reporting module 7110, configured to obtain fault information of the first cluster and report the fault information.
A detecting module 7120, configured to detect whether the first cluster is available at preset time intervals.
A rewriting module 7130, configured to, when the first cluster is available, control the message producer to write the received message into the first cluster corresponding to the message queue.
In an embodiment of the present application, a message processing apparatus includes: the monitoring module is used for determining that the first cluster is a fault cluster when monitoring that the first cluster corresponding to the message queue is unavailable; the message production module is used for controlling the message production end to write the received message into a second cluster corresponding to the message queue; and the message consumption module is used for controlling the message consumption end to extract the messages in the message queue from the first cluster or the second cluster. The cluster failure solving speed in the message queue can be improved because the failure cluster is reserved, the message in the failure cluster can not be lost, the message production end does not need to resend the message, and the double consumption states of the failure cluster and the new cluster are realized.
Embodiments of the present application also provide a computer storage medium, which may store a plurality of instructions adapted to be loaded by a processor and to perform the steps of the method according to any of the above embodiments.
Please refer to fig. 8, fig. 8 is a schematic structural diagram of a server according to an embodiment of the present disclosure. As shown in fig. 8, the server 800 may include: at least one processor 801, at least one network interface 804, a user interface 803, a memory 805, at least one communication bus 802.
Wherein a communication bus 802 is used to enable connective communication between these components.
The user interface 803 may include a Display screen (Display) and a Camera (Camera), and the optional user interface 803 may also include a standard wired interface and a wireless interface.
The network interface 804 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface).
Processor 801 may include one or more processing cores, among other things. The processor 801 interfaces with various components throughout the server 800 using various interfaces and lines to perform various functions of the server 800 and process data by executing or executing instructions, programs, code sets, or instruction sets stored in the memory 805 and invoking data stored in the memory 805. Alternatively, the processor 801 may be implemented in at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor 801 may integrate one or more of a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a modem, and the like. Wherein, the CPU mainly processes an operating system, a user interface, an application program and the like; the GPU is used for rendering and drawing the content required to be displayed by the display screen; the modem is used to handle wireless communications. It is to be understood that the modem may not be integrated into the processor 801, but may be implemented by a single chip.
The Memory 805 may include a Random Access Memory (RAM) or a Read-Only Memory (ROM). Optionally, the memory 805 includes a non-transitory computer-readable medium. The memory 805 may be used to store instructions, programs, code sets, or instruction sets. The memory 805 may include a stored program area and a stored data area, wherein the stored program area may store instructions for implementing an operating system, instructions for at least one function (such as a touch function, a sound playing function, an image playing function, etc.), instructions for implementing the various method embodiments described above, and the like; the storage data area may store data and the like referred to in the above respective method embodiments. The memory 805 may optionally be at least one memory device located remotely from the processor 801 as previously described. As shown in fig. 8, the memory 805, which is a kind of computer storage medium, may include therein an operating system, a network communication module, a user interface module, and a message processing program.
In the server 800 shown in fig. 8, the user interface 803 is mainly used for providing an input interface for a user to obtain data input by the user; and the processor 801 may be configured to call the message handler stored in the memory 805, and specifically perform the following operations:
when monitoring that a first cluster corresponding to the message queue is unavailable, determining the first cluster as a fault cluster;
the control message production end writes the received message into a second cluster corresponding to the message queue;
and the control message consumption end extracts the messages in the message queue from the first cluster or the second cluster.
In an embodiment, when the processor 801 monitors that the first cluster corresponding to the message queue is unavailable, the following steps are specifically performed: when it is monitored that the message production end fails to write the message into the first cluster corresponding to the message queue, determining that the first cluster is unavailable; or acquiring the registration information of the first cluster corresponding to the message queue through the header routing information, and determining that the first cluster is unavailable when the registration information does not meet the preset registration information condition.
In an embodiment, before the processor 801 monitors that the first cluster corresponding to the message queue is unavailable, the following steps are further specifically performed: initializing a first message production end and a second message production end corresponding to the message queue, and keeping the second message production end in a hot start state, wherein the first message production end corresponds to a first cluster, and the second message production end corresponds to a second cluster; and initializing a message consumption end corresponding to the message queue.
In an embodiment, before the processor 801 monitors that the first cluster corresponding to the message queue is unavailable, the following steps are further specifically performed: and controlling the first message production end to write the received message into a first cluster corresponding to the message queue, and controlling the message consumption end to extract the message in the message queue from the first cluster.
In an embodiment, when the processor 801 executes the control message generation end to write the received message into the second cluster corresponding to the message queue, the following steps are specifically executed: and controlling a second message production end to write the received message into a second cluster corresponding to the message queue.
In an embodiment, when the processor 801 executes the control message consumer to extract the message in the message queue from the first cluster or the second cluster, the following steps are specifically executed: the control message consumption end determines a target cluster according to a request title corresponding to the message acquisition request; if the target cluster is the first cluster, controlling the message consumption end to extract the target message corresponding to the message acquisition request in the message queue from the first cluster; and if the target cluster is the second cluster, controlling the message consumption end to extract the target message corresponding to the message acquisition request in the message queue from the second cluster.
In an embodiment, the processor 801 is further configured to obtain fault information of the first cluster, and report the fault information.
In one embodiment, the processor 801 is further configured to perform detecting whether the first cluster is available at preset time intervals; and when the first cluster is available, the control message production end writes the received message into the first cluster corresponding to the message queue.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, a division of modules is merely a division of logical functions, and an actual implementation may have another division, for example, a plurality of modules or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
Modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, functional modules in the embodiments of the present application may be integrated into one processing module, or each of the modules may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode.
The integrated module, if implemented in the form of a software functional module and sold or used as a separate product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method of the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
It should be noted that, for the sake of simplicity, the above-mentioned method embodiments are described as a series of acts or combinations, but those skilled in the art should understand that the present application is not limited by the described order of acts, as some steps may be performed in other orders or simultaneously according to the present application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
In view of the above description of the message processing method, device, storage medium and server provided by the present application, those skilled in the art will recognize that there are variations in the embodiments and applications of the method, device and server according to the concepts of the present application.

Claims (11)

1. A method of message processing, the method comprising:
when monitoring that a first cluster corresponding to a message queue is unavailable, determining that the first cluster is a fault cluster;
the control message production end writes the received message into a second cluster corresponding to the message queue;
and controlling the message consuming end to extract the messages in the message queue from the first cluster or the second cluster.
2. The method of claim 1, wherein the monitoring that the first cluster corresponding to the message queue is unavailable comprises:
when it is monitored that a message production end fails to write a message into a first cluster corresponding to a message queue, determining that the first cluster is unavailable; or
And acquiring the registration information of a first cluster corresponding to the message queue through header routing information, and determining that the first cluster is unavailable when the registration information does not meet the preset registration information condition.
3. The method of claim 1, wherein prior to the monitoring that the first cluster corresponding to the message queue is unavailable, further comprising:
initializing a first message production end and a second message production end corresponding to a message queue, and keeping the second message production end in a hot start state, wherein the first message production end corresponds to the first cluster, and the second message production end corresponds to the second cluster;
and initializing a message consumption end corresponding to the message queue.
4. The method of claim 3, wherein prior to the monitoring that the first cluster corresponding to the message queue is unavailable, further comprising:
and controlling the first message production end to write the received message into the first cluster corresponding to the message queue, and controlling the message consumption end to extract the message in the message queue from the first cluster.
5. The method of claim 4, wherein the controlling message producer writes the received message into a second cluster corresponding to the message queue, and comprises:
and controlling the second message production end to write the received message into the second cluster corresponding to the message queue.
6. The method of claim 1, wherein the controlling the message consumer to extract the message in the message queue from the first cluster or the second cluster comprises:
the control message consumption end determines a target cluster according to a request title corresponding to the message acquisition request;
if the target cluster is the first cluster, controlling the message consumption end to extract the target message corresponding to the message acquisition request in the message queue from the first cluster;
and if the target cluster is the second cluster, controlling the message consumption end to extract the target message corresponding to the message acquisition request in the message queue from the second cluster.
7. The method of claim 1, further comprising:
and acquiring the fault information of the first cluster, and reporting the fault information.
8. The method of claim 1, further comprising:
detecting whether the first cluster is available at preset time intervals;
and when the first cluster is available, controlling the message production end to write the received message into the first cluster corresponding to the message queue.
9. A message processing apparatus, characterized in that the apparatus comprises:
the monitoring module is used for determining that a first cluster corresponding to the message queue is a fault cluster when monitoring that the first cluster is unavailable;
the message production module is used for controlling the message production end to write the received message into a second cluster corresponding to the message queue;
and the message consumption module is used for controlling a message consumption end to extract the messages in the message queue from the first cluster or the second cluster.
10. A computer storage medium storing a plurality of instructions adapted to be loaded by a processor and to perform the steps of the method according to any of claims 1 to 8.
11. A server comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the steps of the method of any one of claims 1 to 8 when executing the program.
CN202110433425.1A 2021-04-21 2021-04-21 Message processing method, device, storage medium and server Pending CN113254274A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202110433425.1A CN113254274A (en) 2021-04-21 2021-04-21 Message processing method, device, storage medium and server

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202110433425.1A CN113254274A (en) 2021-04-21 2021-04-21 Message processing method, device, storage medium and server

Publications (1)

Publication Number Publication Date
CN113254274A true CN113254274A (en) 2021-08-13

Family

ID=77221221

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202110433425.1A Pending CN113254274A (en) 2021-04-21 2021-04-21 Message processing method, device, storage medium and server

Country Status (1)

Country Link
CN (1) CN113254274A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115134217A (en) * 2022-06-20 2022-09-30 政采云有限公司 Data processing method, device, equipment and storage medium
CN115550280A (en) * 2022-11-24 2022-12-30 云账户技术(天津)有限公司 Multi-level message queue implementation method, system, electronic device and readable storage medium

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007133795A (en) * 2005-11-14 2007-05-31 Hitachi Ltd Cluster-structured business system
CN108418859A (en) * 2018-01-24 2018-08-17 华为技术有限公司 The method and apparatus for writing data
CN111176888A (en) * 2018-11-13 2020-05-19 浙江宇视科技有限公司 Cloud storage disaster recovery method, device and system
CN112291082A (en) * 2020-09-30 2021-01-29 北京大米科技有限公司 Computer room disaster recovery processing method, terminal and storage medium
CN112286723A (en) * 2020-09-30 2021-01-29 北京大米科技有限公司 Computer room disaster recovery control method, terminal and storage medium
CN112527567A (en) * 2020-12-24 2021-03-19 北京百度网讯科技有限公司 System disaster tolerance method, device, equipment and storage medium

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2007133795A (en) * 2005-11-14 2007-05-31 Hitachi Ltd Cluster-structured business system
CN108418859A (en) * 2018-01-24 2018-08-17 华为技术有限公司 The method and apparatus for writing data
CN111176888A (en) * 2018-11-13 2020-05-19 浙江宇视科技有限公司 Cloud storage disaster recovery method, device and system
CN112291082A (en) * 2020-09-30 2021-01-29 北京大米科技有限公司 Computer room disaster recovery processing method, terminal and storage medium
CN112286723A (en) * 2020-09-30 2021-01-29 北京大米科技有限公司 Computer room disaster recovery control method, terminal and storage medium
CN112527567A (en) * 2020-12-24 2021-03-19 北京百度网讯科技有限公司 System disaster tolerance method, device, equipment and storage medium

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115134217A (en) * 2022-06-20 2022-09-30 政采云有限公司 Data processing method, device, equipment and storage medium
CN115550280A (en) * 2022-11-24 2022-12-30 云账户技术(天津)有限公司 Multi-level message queue implementation method, system, electronic device and readable storage medium
CN115550280B (en) * 2022-11-24 2023-03-31 云账户技术(天津)有限公司 Multi-level message queue implementation method, system, electronic device and readable storage medium

Similar Documents

Publication Publication Date Title
US20180270182A1 (en) Message notification method, system, and device for a communication account
JP6127150B2 (en) Send notifications to multiple devices associated with a user
US10417062B2 (en) Method and apparatus of unloading out of memory processing flow to user space
EP3547715A1 (en) Method and apparatus for reducing continuous-wakeup delay of bluetooth loudspeaker, and bluetooth loudspeaker
CN109756417A (en) Offline message distribution method, server and storage medium
CN113254274A (en) Message processing method, device, storage medium and server
CN115004673B (en) Message pushing method, device, electronic equipment and computer readable medium
CN102196033A (en) Remote content classification and transmission using multiple transport channels
CN113452774B (en) Message pushing method, device, equipment and storage medium
CN112437001B (en) Method and device for guaranteeing reliable delivery and consumption of messages
CN110300067A (en) Queue regulation method, device, equipment and computer readable storage medium
CN113923397A (en) Method and device for detecting state of conference room equipment, electronic equipment and storage medium
CN115964153A (en) Asynchronous task processing method, device, equipment and storage medium
CN113014608A (en) Flow distribution control method and device, electronic equipment and storage medium
CN116594563A (en) Distributed storage capacity expansion method and device, electronic equipment and storage medium
CN113452948B (en) Conference terminal control method, device, equipment and storage medium
CN110362395A (en) Background program management method, device, computer equipment and storage medium
CN114268799B (en) Streaming media transmission method and device, electronic equipment and medium
CN109040491A (en) On-hook behavior processing method, device, computer equipment and storage medium
CN115499501A (en) Message pushing method, system, service gateway and storage medium
CN111290873B (en) Fault processing method and device
CN113709214A (en) Message processing method and device, electronic equipment and storage medium
CN113641688A (en) Node updating method, related device and computer program product
CN107809743A (en) A kind of information synchronization method, terminal device and computer-readable recording medium
CN113014404A (en) Message transmission method and device, server and second client

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