CN109039803A - A kind of method, system and the computer equipment of processing readjustment notification message - Google Patents
A kind of method, system and the computer equipment of processing readjustment notification message Download PDFInfo
- Publication number
- CN109039803A CN109039803A CN201810750708.7A CN201810750708A CN109039803A CN 109039803 A CN109039803 A CN 109039803A CN 201810750708 A CN201810750708 A CN 201810750708A CN 109039803 A CN109039803 A CN 109039803A
- Authority
- CN
- China
- Prior art keywords
- key
- zookeeper
- notification message
- callback notification
- value pair
- 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
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/12—Network monitoring probes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Electric Clocks (AREA)
Abstract
The present invention provides method, system and the computer equipment of a kind of processing readjustment notification message, method includes: when the nodal information of zookeeper changes, and multiple oracle listeners receive the readjustment notification message that zookeeper is sent；To adjust back the event identifier ID in notification message as key key, self ID is written in the corresponding value of the key respectively, forms key-value pair, key-value pair includes one；Judge whether self ID can match with the value in key-value pair, if can, readjustment notification message is handled；So, because key-value pair only includes one, that is the ID of only one oracle listener could form key-value pair with key, the oracle listener of the value successful match in self ID and key-value pair is just only so handled into readjustment notification message, processing readjustment notification message thus can be all removed to avoid multiple oracle listeners, and then the wasting of resources is avoided, resource consumption is excessive.
Description
Technical Field
The invention belongs to the technical field of internet, and particularly relates to a method, a system and computer equipment for processing callback notification messages.
Background
With the popularization of large flow and large application, distributed deployment is popularized. In a simple manner, the distributed architecture utilizes cluster computing resources to face large-flow access, and improves the availability and expansibility of the system. In the application of the cluster zookeeper, an event callback mechanism is commonly used, namely a node is monitored, and when the node changes, a monitoring program is notified.
However, when a plurality of programs monitor the event change of a certain node in the zookeeper at the same time, if the node changes, the zookeeper notifies each listener, and each listener processes the notification message after receiving the notification message, but in actual application, only a single listener processes the notification message, which results in excessive resource consumption.
Disclosure of Invention
For solving the problems in the prior art, embodiments of the present invention provide a method, a system, and a computer device for processing a callback notification message, which are used to solve the technical problem in the prior art that in applications of a zookeeper, when a plurality of programs monitor event changes of a certain node in the zookeeper at the same time, if the node changes, the zookeeper notifies each monitoring program, and after receiving the notification message, each monitoring program processes the message, which results in excessive resource consumption.
The invention provides a method for processing callback notification message, which is applied to a zookeeper cluster and comprises the following steps:
when the target node information of the zookeeper changes, a plurality of monitoring programs receive callback notification messages sent by the zookeeper;
taking the event identification ID in the callback notification message as a key, and respectively writing the ID into a value corresponding to the key to form a key value pair, wherein the key value pair comprises one;
and judging whether the self ID can be matched with the value in the key value pair, and if so, processing the callback notification message.
In the above solution, the writing the ID of the event identifier ID into a value corresponding to the key to form a key-value pair with the event identifier ID as the key includes:
and the plurality of monitoring programs respectively write the IDs into the values corresponding to the keys by using the unique write command in the memory database to form key value pairs.
In the above scheme, when node information of the zookeeper changes, before the plurality of monitoring programs receive the callback notification message sent by the zookeeper, the method includes:
the plurality of listeners send registration requests to the zookeeper to listen for the callback notification message.
In the foregoing scheme, the processing the callback notification message includes:
the processed identification is marked in the event ID, and the marked event ID is stored in a shared data block.
The invention also provides a system for processing callback notification messages, which comprises: the zookeeper cluster comprises a zookeeper cluster and a plurality of application servers, wherein each application server is provided with a monitoring program; wherein,
the application servers are used for receiving callback notification messages sent by the zookeeper when target node information of the zookeeper changes, wherein the callback notification messages carry unique event Identifiers (IDs);
respectively writing the ID of the event identification ID into a value corresponding to the key by taking the event identification ID as the key to form a key value pair, wherein the key value pair comprises one;
and judging whether the self ID can be matched with the value in the key value pair, and if so, processing the callback notification message.
In the foregoing solution, the plurality of application servers are specifically configured to:
and respectively writing the ID into the value corresponding to the key by using the unique write command in the memory database to form a key value pair.
In the above scheme, when node information of the zookeeper changes and before receiving a callback notification message sent by the zookeeper, the plurality of application servers are further configured to: and sending a registration request for monitoring the callback notification message to the zookeeper.
In the foregoing solution, the application server is further configured to: after the callback notification message is processed, marking the processed identifier in the event ID, and storing the marked event ID in a shared data block.
The invention also provides a computer-readable storage medium, on which a computer program is stored, characterized in that the program, when executed by a processor, implements the method of any of the above.
The invention also provides a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements any of the methods described above when executing the program.
The invention provides a method, a system and computer equipment for processing callback notification messages, wherein the method comprises the following steps: when the node information of the zookeeper changes, a plurality of monitoring programs receive callback notification messages sent by the zookeeper; taking the event identification ID in the callback notification message as a key, and respectively writing the ID into a value corresponding to the key to form a key value pair, wherein the key value pair comprises one; judging whether the ID of the user can be matched with the value in the key value pair, if so, processing the callback notification message; therefore, only one key value pair is included, namely only the ID of one monitoring program and the key value form the key value pair, and only the monitoring program which successfully matches the ID of the monitoring program with the value in the key value pair processes the callback notification message, so that the situation that a plurality of monitoring programs process the callback notification message can be avoided, resource waste is avoided, and resource consumption is overlarge.
Drawings
Fig. 1 is a flowchart illustrating a method for processing a callback notification message according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a system for processing a callback notification message according to an embodiment of the present invention.
Detailed Description
The technical problem that in the application of a zookeeper in the prior art, when a plurality of programs monitor the event change of a certain node in the zookeeper at the same time, if the node changes, the zookeeper can notify each monitoring program, and each monitoring program can process the message after receiving the notification message, so that the resource consumption is overlarge is solved, the embodiment of the invention provides a method, a system and computer equipment for processing callback notification messages, wherein the method comprises the following steps: when the node information of the zookeeper changes, a plurality of monitoring programs receive callback notification messages sent by the zookeeper; taking the event identification ID in the callback notification message as a key, and respectively writing the ID into a value corresponding to the key to form a key value pair, wherein the key value pair comprises one; and judging whether the ID of the user can be matched with the value in the key value pair, and if so, processing the callback notification message.
The technical solution of the present invention is further described in detail by the accompanying drawings and the specific embodiments.
Example one
This embodiment provides a method for processing a callback notification message, as shown in fig. 1, where the method includes:
s110, when the target node information of the zookeeper changes, a plurality of monitoring programs receive callback notification messages sent by the zookeeper;
here, the listener is provided in application servers, each of which is connected to zookeeper via an interface.
When node information of the zookeeper changes, before a plurality of listeners receive callback notification messages sent by the zookeeper, the method comprises the following steps: the plurality of monitoring programs send requests for registering and monitoring the callback notification message to the zookeeper by using an Application Programming Interface (API) provided by the zookeeper, so that when the target node information of the zookeeper changes, the plurality of monitoring programs can receive the callback notification message sent by the zookeeper. The callback notification message carries a unique event identifier ID.
S111, taking the event identification ID in the callback notification message as a key, and respectively writing the ID into a value corresponding to the key to form a key value pair, wherein the key value pair comprises one;
and after each monitoring program receives the callback notification message, analyzing the callback notification message to acquire an event identifier ID carried by the callback notification message.
After the event identification ID is obtained, the event identification ID is used as a key, unique write commands in a memory database redis are used for respectively trying to write the ID into a value corresponding to the key to form a key value pair, and the key value pair is stored in the memory database. Here, since the write is performed by using the unique write command, the key value pair includes one, that is, after one listener writes successfully, other listeners do not write, and finally only one listener writes successfully. The self-ID may include an IP address and/or a port address of the application server.
For example, if the event ID is 11 and the self ID of a certain listener is 123456, then the unique write command SETNX in the memory database is used to respectively try to write the self ID into the value corresponding to the key, and the code forming the key value pair is implemented as follows:
SETNX 11 123456
and S112, judging whether the self ID can be matched with the value in the key value pair, and if so, processing the callback notification message.
After the key value pair is formed, each monitoring program queries the key value pair in the memory database, judges whether the ID of the monitoring program can be matched with the value in the key value pair, if so, the monitoring program is a monitoring program which is written successfully, and processes the callback notification message. If not, the listener is not the successfully written listener, and the callback notification message is ignored. The specific code is implemented as follows:
SETNX 11 123456
val＝GET 11
if(val＝＝123456){
v/processing messages for specific business processing
}else{
//do nothing
}
As an optional embodiment, after the listener that successfully matches finishes processing the callback notification message, the method includes: and feeding back a feedback message of successful processing to the zookeeper, marking the processed identification at the event identification ID, and storing the marked event identification ID in a shared data block of the memory data. For example, the processed identifier may include a default number or letter.
However, when the monitoring program which is successfully matched is down, and thus the callback notification message cannot be processed, the monitoring program cannot send a feedback message to the zookeeper, and the zookeeper cannot receive the feedback message within a preset time, and then the callback notification message is sent to the plurality of monitoring programs again, so that the callback notification message can be processed again by the monitoring programs. The preset time is generally 1-2 s.
As an alternative embodiment, in order to improve the processing efficiency, the preset time is generally set to be about 100ms in some instant scenarios (such as transaction scenarios). However, if network congestion occurs, the monitor has already processed the callback notification message, the zookeeper cannot receive the feedback message in time, and when the callback notification message is sent to multiple monitors again, in order to avoid repeated processing, after receiving the event identifier ID, the multiple monitors will search the event identifier ID in the shared data block, if it can find the event identifier ID, determine whether the event identifier ID has a processed mark, if so, ignore the callback notification message, and avoid resource waste.
Based on the same inventive concept, the invention further provides a system for processing the callback notification message, which can be seen in embodiment two.
Example two
The present embodiment provides a system for processing a callback notification message, as shown in fig. 2, the system includes: as shown in fig. 2, the zookeeper cluster and the plurality of application servers include n application servers, including 1-n application servers, each application server is provided with a monitoring program, and each application server is connected with the zookeeper through an interface.
When node information of the zookeeper changes, the multiple application servers are used for sending a request for registering and monitoring the callback notification message to the zookeeper by using an application program interface API (application program interface) provided by the zookeeper before receiving the callback notification message sent by the zookeeper, so that when target node information of the zookeeper changes, a monitoring program in the multiple application servers can receive the callback notification message sent by the zookeeper. The callback notification message carries a unique event identifier ID.
And when the monitoring program in each application server receives the callback notification message, analyzing the callback notification message to acquire an event identifier ID carried by the callback notification message.
After the event identification ID is obtained, the monitoring program in each application server takes the event identification ID as a key, respectively tries to write the ID into a value corresponding to the key by using a unique write command in a memory database redis to form a key value pair, and stores the key value pair in a memory database. Here, the key-value pair comprises one, i.e. only one listener write succeeds, since the write is performed with a unique write command. The self-ID may include an IP address and/or a port address of the application server.
For example, if the event ID is 11 and the self ID of a certain listener is 123456, then the unique write command SETNX in the memory database is used to respectively try to write the self ID into the value corresponding to the key, and the code forming the key value pair is implemented as follows:
SETNX 11 123456
after the key-value pairs are formed, the listener of each application server is further configured to: and inquiring the key value pair in the memory database, judging whether the ID of the listener can be matched with the value in the key value pair, if so, indicating that the listener is a listener with successful writing, and processing the callback notification message. If not, the listener is not the successfully written listener, and the callback notification message is ignored. The specific code is implemented as follows:
SETNX 11 123456
val＝GET 11
if(val＝＝123456){
v/processing messages for specific business processing
}else{
//do nothing
}
As an optional embodiment, after the successfully matched listener finishes processing the callback notification message, the listener of the application server is further configured to: and feeding back a feedback message of successful processing to the zookeeper, marking the processed identification at the event identification ID, and storing the marked event identification ID in a shared data block of the memory data. For example, the processed identifier may include a default number or letter.
However, when the monitoring program which is successfully matched is down, and thus the callback notification message cannot be processed, the monitoring program cannot send a feedback message to the zookeeper, and the zookeeper cannot receive the feedback message within a preset time, and then the callback notification message is sent to the plurality of monitoring programs again, so that the callback notification message can be processed again by the monitoring programs. The preset time is generally 1-2 s.
As an alternative embodiment, in order to improve the processing efficiency, the preset time is generally set to be about 100ms in some instant scenarios (such as transaction scenarios). However, if network congestion occurs, the monitor has already processed the callback notification message, the zookeeper cannot receive the feedback message in time, and when the callback notification message is sent to multiple monitors again, in order to avoid repeated processing, after receiving the event identifier ID, the monitors in multiple application servers search the event identifier ID in the shared data block, if so, determine whether the event identifier ID has a processed mark, and if so, ignore the callback notification message, thereby avoiding resource waste.
The technical scheme provided in the embodiment of the application at least has the following technical effects or advantages:
the invention provides a method, a system and computer equipment for processing callback notification messages, wherein the method comprises the following steps: when the node information of the zookeeper changes, a plurality of monitoring programs receive callback notification messages sent by the zookeeper; taking the event identification ID in the callback notification message as a key, and respectively writing the ID into a value corresponding to the key to form a key value pair, wherein the key value pair comprises one; judging whether the ID of the user can be matched with the value in the key value pair, if so, processing the callback notification message; therefore, only one key value pair is included, namely only the ID of one monitoring program and the key value form the key value pair, and only the monitoring program which successfully matches the ID of the monitoring program with the value in the key value pair processes the callback notification message, so that the situation that a plurality of monitoring programs process the callback notification message can be avoided, the resource waste is avoided, and the resource consumption is overlarge; and when the successfully matched monitoring program is down, the callback notification message can be sent to the monitoring program again so as to process the message again, thereby avoiding the occurrence of service problems.
The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In the description provided herein, numerous specific details are set forth. It is understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
The various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that a microprocessor or Digital Signal Processor (DSP) may be used in practice to implement some or all of the functions of some or all of the components of a system, computer device, or the like, according to embodiments of the present invention. The present invention may also be embodied as apparatus or system programs (e.g., computer programs and computer program products) for performing a portion or all of the methods described herein. Such programs implementing the present invention may be stored on computer-readable media or may be in the form of one or more signals. Such a signal may be downloaded from an internet website or provided on a carrier signal or in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several systems, several of these systems may be embodied by one and the same item of hardware. The usage of the words first, second and third, etcetera do not indicate any ordering. These words may be interpreted as names.
The above description is only exemplary of the present invention and should not be taken as limiting the scope of the present invention, and any modifications, equivalents, improvements, etc. that are within the spirit and principle of the present invention should be included in the present invention.
Claims (10)
1. A method of processing callback notification messages, for use in a clustered zookeeper, the method comprising:
when the target node information of the zookeeper changes, a plurality of monitoring programs receive callback notification messages sent by the zookeeper;
taking the event identification ID in the callback notification message as a key, and respectively writing the ID into a value corresponding to the key to form a key value pair, wherein the key value pair comprises one;
and judging whether the self ID can be matched with the value in the key value pair, and if so, processing the callback notification message.
2. The method of claim 1, wherein the writing of the self ID into the value corresponding to the key with the event identification ID as the key to form a key-value pair comprises:
and the plurality of monitoring programs respectively write the IDs into the values corresponding to the keys by using the unique write command in the memory database to form key value pairs.
3. The method of claim 1, wherein when node information of zookeeper changes, before receiving callback notification messages sent by zookeeper, the plurality of listeners comprises:
the plurality of listeners send registration requests to the zookeeper to listen for the callback notification message.
4. The method of claim 1, wherein processing the callback notification message comprises:
the processed identification is marked in the event ID, and the marked event ID is stored in a shared data block.
5. A system for processing callback notification messages, said system comprising: the zookeeper cluster comprises a zookeeper cluster and a plurality of application servers, wherein each application server is provided with a monitoring program; wherein,
the application servers are used for receiving callback notification messages sent by the zookeeper when target node information of the zookeeper changes, wherein the callback notification messages carry unique event Identifiers (IDs);
respectively writing the ID of the event identification ID into a value corresponding to the key by taking the event identification ID as the key to form a key value pair, wherein the key value pair comprises one;
and judging whether the self ID can be matched with the value in the key value pair, and if so, processing the callback notification message.
6. The system of claim 5, wherein the plurality of application servers are specifically configured to:
and respectively writing the ID into the value corresponding to the key by using the unique write command in the memory database to form a key value pair.
7. The system of claim 5, wherein when zookeeper's node information changes, the plurality of application servers are configured to, prior to receiving a callback notification message sent by zookeeper: and sending a registration request for monitoring the callback notification message to the zookeeper.
8. The system of claim 5, wherein the application server is further to: after the callback notification message is processed, marking the processed identifier in the event ID, and storing the marked event ID in a shared data block.
9. A computer-readable storage medium, on which a computer program is stored, which program, when being executed by a processor, is adapted to carry out the method of any one of claims 1 to 4.
10. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any of claims 1 to 4 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810750708.7A CN109039803A (en) | 2018-07-10 | 2018-07-10 | A kind of method, system and the computer equipment of processing readjustment notification message |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810750708.7A CN109039803A (en) | 2018-07-10 | 2018-07-10 | A kind of method, system and the computer equipment of processing readjustment notification message |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN109039803A true CN109039803A (en) | 2018-12-18 |
Family
ID=64640822
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810750708.7A Pending CN109039803A (en) | 2018-07-10 | 2018-07-10 | A kind of method, system and the computer equipment of processing readjustment notification message |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109039803A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109961273A (en) * | 2019-03-20 | 2019-07-02 | 广州精选速购网络科技有限公司 | Payment readjustment processing method, system and storage medium |
| CN111857798A (en) * | 2020-06-30 | 2020-10-30 | 厦门亿联网络技术股份有限公司 | Method for notifying configuration change of embedded equipment |
| CN111897646A (en) * | 2020-08-13 | 2020-11-06 | 银联商务股份有限公司 | Asynchronous distributed lock implementation method and device, storage medium and electronic device |
| CN112818063A (en) * | 2021-02-04 | 2021-05-18 | 厦门安盟网络股份有限公司 | Data synchronization method and device of distributed system |
| CN113220472A (en) * | 2021-04-16 | 2021-08-06 | 阿波罗智联(北京)科技有限公司 | Application program communication method, device and storage medium |
| CN116405384A (en) * | 2023-03-21 | 2023-07-07 | 北京志凌海纳科技有限公司 | Method, system, equipment and storage medium for solving declarative API resource race |
| RU2805125C1 (en) * | 2020-03-27 | 2023-10-11 | Ханчжоу Хиквижен Диджитал Текнолоджи Ко., Лтд. | Method, system and device for determining action |
Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102377576A (en) * | 2010-08-06 | 2012-03-14 | 高通创锐讯通讯科技(上海)有限公司 | Multicast realization method |
| CN102661487A (en) * | 2012-04-18 | 2012-09-12 | 浙江大学城市学院 | Mobile data collection method of pipeline gas internet of things (IOT) |
| WO2013064815A1 (en) * | 2011-11-04 | 2013-05-10 | Performance Horizon Group | Method and database system for manipulating data |
| CN104333614A (en) * | 2014-10-31 | 2015-02-04 | 北京奇虎科技有限公司 | Terminal recognition method, device and system |
| CN105245471A (en) * | 2015-09-25 | 2016-01-13 | 京信通信技术(广州)有限公司 | Message sending method and message sending device |
| CN106156864A (en) * | 2015-03-27 | 2016-11-23 | 天脉聚源（北京）科技有限公司 | A kind of method and system of big quantity ticket booking |
| CN106649646A (en) * | 2016-12-09 | 2017-05-10 | 北京锐安科技有限公司 | Method and device for deleting duplicated data |
| CN106776156A (en) * | 2016-12-13 | 2017-05-31 | 东软集团股份有限公司 | A kind of service control method and device |
| CN106970958A (en) * | 2017-03-17 | 2017-07-21 | 浙江大华技术股份有限公司 | A kind of inquiry of stream file and storage method and device |
| CN107391276A (en) * | 2017-07-05 | 2017-11-24 | 腾讯科技（深圳）有限公司 | Distributed monitor method, interception control device and system |
| CN107894919A (en) * | 2017-11-30 | 2018-04-10 | 中国平安财产保险股份有限公司 | Timed task triggering method, device, equipment and readable storage medium storing program for executing |
| CN108063808A (en) * | 2017-12-11 | 2018-05-22 | 海尔优家智能科技（北京）有限公司 | A kind of acquisition methods of business, device, storage medium and computer equipment |
-
2018
- 2018-07-10 CN CN201810750708.7A patent/CN109039803A/en active Pending
Patent Citations (12)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102377576A (en) * | 2010-08-06 | 2012-03-14 | 高通创锐讯通讯科技(上海)有限公司 | Multicast realization method |
| WO2013064815A1 (en) * | 2011-11-04 | 2013-05-10 | Performance Horizon Group | Method and database system for manipulating data |
| CN102661487A (en) * | 2012-04-18 | 2012-09-12 | 浙江大学城市学院 | Mobile data collection method of pipeline gas internet of things (IOT) |
| CN104333614A (en) * | 2014-10-31 | 2015-02-04 | 北京奇虎科技有限公司 | Terminal recognition method, device and system |
| CN106156864A (en) * | 2015-03-27 | 2016-11-23 | 天脉聚源（北京）科技有限公司 | A kind of method and system of big quantity ticket booking |
| CN105245471A (en) * | 2015-09-25 | 2016-01-13 | 京信通信技术(广州)有限公司 | Message sending method and message sending device |
| CN106649646A (en) * | 2016-12-09 | 2017-05-10 | 北京锐安科技有限公司 | Method and device for deleting duplicated data |
| CN106776156A (en) * | 2016-12-13 | 2017-05-31 | 东软集团股份有限公司 | A kind of service control method and device |
| CN106970958A (en) * | 2017-03-17 | 2017-07-21 | 浙江大华技术股份有限公司 | A kind of inquiry of stream file and storage method and device |
| CN107391276A (en) * | 2017-07-05 | 2017-11-24 | 腾讯科技（深圳）有限公司 | Distributed monitor method, interception control device and system |
| CN107894919A (en) * | 2017-11-30 | 2018-04-10 | 中国平安财产保险股份有限公司 | Timed task triggering method, device, equipment and readable storage medium storing program for executing |
| CN108063808A (en) * | 2017-12-11 | 2018-05-22 | 海尔优家智能科技（北京）有限公司 | A kind of acquisition methods of business, device, storage medium and computer equipment |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109961273A (en) * | 2019-03-20 | 2019-07-02 | 广州精选速购网络科技有限公司 | Payment readjustment processing method, system and storage medium |
| RU2805125C1 (en) * | 2020-03-27 | 2023-10-11 | Ханчжоу Хиквижен Диджитал Текнолоджи Ко., Лтд. | Method, system and device for determining action |
| CN111857798A (en) * | 2020-06-30 | 2020-10-30 | 厦门亿联网络技术股份有限公司 | Method for notifying configuration change of embedded equipment |
| CN111857798B (en) * | 2020-06-30 | 2022-09-13 | 厦门亿联网络技术股份有限公司 | Method for notifying configuration change of embedded equipment |
| CN111897646A (en) * | 2020-08-13 | 2020-11-06 | 银联商务股份有限公司 | Asynchronous distributed lock implementation method and device, storage medium and electronic device |
| CN112818063A (en) * | 2021-02-04 | 2021-05-18 | 厦门安盟网络股份有限公司 | Data synchronization method and device of distributed system |
| CN113220472A (en) * | 2021-04-16 | 2021-08-06 | 阿波罗智联(北京)科技有限公司 | Application program communication method, device and storage medium |
| CN116405384A (en) * | 2023-03-21 | 2023-07-07 | 北京志凌海纳科技有限公司 | Method, system, equipment and storage medium for solving declarative API resource race |
| CN116405384B (en) * | 2023-03-21 | 2024-01-30 | 北京志凌海纳科技有限公司 | Method, system, equipment and storage medium for solving declarative API resource race |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109039803A (en) | A kind of method, system and the computer equipment of processing readjustment notification message | |
| US11068964B2 (en) | Method and device for processing service request | |
| WO2020181813A1 (en) | Task scheduling method based on data processing and related device | |
| WO2021151312A1 (en) | Method for determining inter-service dependency, and related apparatus | |
| CN107633016B (en) | Data processing method and device and electronic device | |
| US10425502B2 (en) | System and method for acquiring, processing and updating global information | |
| US20190158626A1 (en) | Method, apparatus and computer readable storage medium for processing service | |
| CN106909451A (en) | A kind of distributed task dispatching system and method | |
| JP2007503628A5 (en) | ||
| US20160371122A1 (en) | File processing workflow management | |
| US10454795B1 (en) | Intermediate batch service for serverless computing environment metrics | |
| CN114189525B (en) | Service request method and device and electronic equipment | |
| CN114024972A (en) | Long connection communication method, system, device, equipment and storage medium | |
| CN108170551A (en) | Front and back end error handling method, server and storage medium based on crawler system | |
| US20200310828A1 (en) | Method, function manager and arrangement for handling function calls | |
| CN113821495B (en) | Database cluster implementation system and method | |
| WO2017118318A1 (en) | Data storage and service processing method and device | |
| CN113986995A (en) | Request distribution method and device, storage medium and electronic equipment | |
| CN115002000B (en) | Fault tolerance method, device, equipment and storage medium for abnormal interface | |
| WO2019062066A1 (en) | On-line task execution method for terminal device, server, and readable storage medium | |
| CN111930542A (en) | Data acquisition method and device, electronic equipment and computer readable storage medium | |
| US20170004012A1 (en) | Methods and apparatus to manage operations situations in computing environments using presence protocols | |
| CN104636131A (en) | Special instruction execution method and device | |
| CN111835809B (en) | Work order message distribution method, work order message distribution device, server and storage medium | |
| US20170139808A1 (en) | Method and dispatcher node for server processing management |
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 | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20181218 |