CN110166528A - The method, apparatus and computer equipment for preventing node Notification of Changes from losing - Google Patents
The method, apparatus and computer equipment for preventing node Notification of Changes from losing Download PDFInfo
- Publication number
- CN110166528A CN110166528A CN201910305189.8A CN201910305189A CN110166528A CN 110166528 A CN110166528 A CN 110166528A CN 201910305189 A CN201910305189 A CN 201910305189A CN 110166528 A CN110166528 A CN 110166528A
- Authority
- CN
- China
- Prior art keywords
- changes
- notification
- node
- server
- node notification
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- 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
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- 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/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Abstract
This application discloses a kind of methods for preventing node Notification of Changes from losing, device and computer equipment, pass through the first node Notification of Changes set stored in zookeeper server, and the second node Notification of Changes set stored in subscriber's server, both the node Notification of Changes lacked in second node Notification of Changes set relative to first node Notification of Changes collection kind can quickly have been found out, these node Notifications of Changes lacked are the loss node Notification of Changes that subscriber's server is not received by, ensure that the Notification of Changes of zookeeper node congestion will not occur because of network, the reasons such as subscriber's system failure are lost.
Description
Technical field
This application involves the technical fields for arriving node Notification of Changes, and especially relating to one kind prevents node Notification of Changes from losing
The method, apparatus and computer equipment of mistake.
Background technique
ESG-ADMIN (subscriber's server) is a kind of enterprises service improvement platform management system, for monitoring
Node change of zookeeper etc., because (zookeeper is one distributed to zookeeper, the distribution of open source code
Application program coordination service is the realization of Chubby mono- open source of Google, is the significant components of Hadoop and Hbase) only
Support listening mode that subscriber (third party system, such as ESG-ADMIN), that is, zookeeper is notified only to be responsible for subscription
Whether square server sending node Notification of Changes, subscriber's server receive the node Notification of Changes of zookeeper transmission,
Zookeeper is not relevant for, so will lead to subscriber's server when congestion, subscriber's system failure occurs in network cannot connect
Whole node Notifications of Changes that zookeeper is sent to it are received, that is, there are problems that node Notification of Changes loss.
Summary of the invention
The main purpose of the application is that the method, apparatus for providing sending node Notification of Changes, computer equipment and storage are situated between
Matter, it is intended to solve the problems, such as because network occur congestion, subscriber's system failure and cause node Notification of Changes lose.
In order to achieve the above-mentioned object of the invention, a kind of method that the application proposes sending node Notification of Changes, is used for
To subscriber's server sending node Notification of Changes, be equipped in the zookeeper server makes zookeeper server
The notification component that zookeeper server supports RESTful interface to call, the method for the sending node Notification of Changes include:
Zookeeper server obtains node Notification of Changes, wherein the node Notification of Changes includes instant node path
With the change time；
The first RESTful interface that subscriber's server is called using the notification component, the node is changed
It notifies to send to subscriber's server, and, the node Notification of Changes is stored in local first node and changed and is led to
Know in set；
On a preset condition based, preset 2nd RESTful of subscriber's server is called to connect by the notification component
Mouthful, and the first node Notification of Changes set is transferred to subscriber's server by the 2nd RESTful interface.
Further, it is described on a preset condition based, call subscriber's server preset by the notification component
2nd RESTful interface, and the first node Notification of Changes set is transferred to by the 2nd RESTful interface described
The step of subscriber's server, comprising:
Judge whether the quantity of the node Notification of Changes in the first node Notification of Changes set is equal to preset quantity
Threshold value；
If so, calling the preset 2nd RESTful interface of subscriber's server by the notification component, and will
The first node Notification of Changes set is transferred to subscriber's server by the 2nd RESTful interface.
Further, it is described on a preset condition based, call subscriber's server preset by the notification component
2nd RESTful interface, and the first node Notification of Changes set is transferred to by the 2nd RESTful interface described
The step of subscriber's server, comprising:
The first node Notification of Changes set is once sent before obtaining to the first time of subscriber's server, with
And obtain the second current time；
Judge whether the time difference of the first time and the second time are equal to preset time threshold；
If so, calling the preset 2nd RESTful interface of subscriber's server by the notification component, and will
The first node Notification of Changes set is transferred to subscriber's server by the 2nd RESTful interface.
The application also by a kind of method for preventing node Notification of Changes from losing, is prevented for subscriber's server
The node Notification of Changes that the method for zookeeper server by utilizing sending node Notification of Changes as described in any one of the above embodiments is sent
It loses；The method for preventing node Notification of Changes from losing, comprising:
Subscriber's server is sent by zookeeper server described in the first RESTful interface
Node Notification of Changes, and the node Notification of Changes received is stored in preset memory space, it is logical to form second node change
Know set；
After receiving the first node Notification of Changes set that the zookeeper server is sent, described the
The loss node Notification of Changes for being not present in the second node Notification of Changes set is searched in one node Notification of Changes set；
Corresponding processing operation is completed according to the instant node path for losing node Notification of Changes.
Further, described search in the first node Notification of Changes set is not present in second node Notification of Changes
The step of loss node Notification of Changes of set includes:
Extract the first change time of each of first node Notification of Changes set node Notification of Changes；
It searches into the second node Notification of Changes set and becomes with the first change time identical second described in each
The more time；
The remaining first change time for not finding the identical second change time is obtained, by remaining described first
The change time, corresponding node Notification of Changes was denoted as the loss node Notification of Changes.
Further, described after receiving the zookeeper server transmission first node Notification of Changes set,
The loss node Notification of Changes for being not present in second node Notification of Changes set is searched in the first node Notification of Changes set
The step of after, further includes:
It calculates the quantity for losing node Notification of Changes and accounts for whole nodes changes in the first node Notification of Changes set
The ratio value of the quantity more notified；
If the ratio value is greater than preset proportion threshold value, warning message is generated.
The application also provides a kind of device of sending node Notification of Changes, takes for zookeeper server to subscriber
It is engaged in device sending node Notification of Changes, being equipped in the zookeeper server makes zookeeper server support RESTful
The notification component that interface calls, described device include:
Acquiring unit obtains node Notification of Changes for zookeeper server, wherein the node Notification of Changes packet
Include instant node path and change time；
Storage unit is sent, for calling the first RESTful of subscriber's server to connect using the notification component
Mouthful, the node Notification of Changes is sent to subscriber's server, and, the node Notification of Changes is stored in local
First node Notification of Changes set in；
Transmission unit is called, on a preset condition based, calling subscriber's server pre- by the notification component
If the 2nd RESTful interface, and the first node Notification of Changes set is transferred to by the 2nd RESTful interface described
Subscriber's server.
The application also provides a kind of device for preventing node Notification of Changes from losing, and prevents for subscriber's server
The node Notification of Changes that the method for zookeeper server by utilizing sending node Notification of Changes as described in any one of the above embodiments is sent
It loses；The device for preventing node Notification of Changes from losing, comprising:
Receiving unit passes through zookeeper described in the first RESTful interface for subscriber's server
The node Notification of Changes that server is sent, and the node Notification of Changes received is stored in preset memory space forms the
Two node Notification of Changes set；
Searching unit, for when the first node Notification of Changes collection for receiving the zookeeper server transmission
After conjunction, the loss section for being not present in the second node Notification of Changes set is searched in the first node Notification of Changes set
Point Notification of Changes；
Processing unit, for completing corresponding processing behaviour according to the instant node path for losing node Notification of Changes
Make.
The application also provides a kind of computer equipment, including memory and processor, and the memory is stored with computer
Program, the processor realize that the change of sending node described in any one of claims 1 to 3 is logical when executing the computer program
The step for the method for preventing node Notification of Changes from losing described in any one of the step of method known, or realization claim 4 to 6
Suddenly.
The application also provides a kind of computer readable storage medium, is stored thereon with computer program, the computer journey
The step of method of sending node Notification of Changes described in any one of claims 1 to 3 is realized when sequence is executed by processor, or
The step of realizing the method for preventing node Notification of Changes from losing described in any one of claim 4 to 6.
The method, apparatus and computer equipment for preventing node Notification of Changes from losing of the application, by being taken in zookeeper
The second node Notification of Changes collection stored in the first node Notification of Changes set and subscriber's server stored in business device
It closes, both can quickly find out the section lacked in second node Notification of Changes set relative to first node Notification of Changes collection kind
Point Notification of Changes, these node Notifications of Changes lacked are that the loss node change that is not received by of subscriber's server is logical
Know, it is ensured that the reasons such as congestion, subscriber's system failure loss will not occur because of network in the Notification of Changes of zookeeper node.
Detailed description of the invention
Fig. 1 is the flow diagram of the method for the sending node Notification of Changes of one embodiment of the application；
Fig. 2 is the method flow schematic diagram for preventing node Notification of Changes from losing of one embodiment of the application；
Fig. 3 is the structural schematic block diagram of the device of the sending node Notification of Changes of one embodiment of the application；
Fig. 4 is the structural schematic block diagram of the device for preventing node Notification of Changes from losing of one embodiment of the application；
Fig. 5 is the structural schematic block diagram of the computer equipment of one embodiment of the application.
The embodiments will be further described with reference to the accompanying drawings for realization, functional characteristics and the advantage of the application purpose.
Specific embodiment
It is with reference to the accompanying drawings and embodiments, right in order to which the objects, technical solutions and advantages of the application are more clearly understood
The application is further elaborated.It should be appreciated that specific embodiment described herein is only used to explain the application, not
For limiting the application.
Referring to Fig.1, the embodiment of the present application provides a kind of method of sending node Notification of Changes, services for zookeeper
For device to subscriber's server sending node Notification of Changes, being equipped in the zookeeper server makes zookeeper server
The notification component for supporting RESTful interface to call.
Above-mentioned zookeeper server is the server for running zookeeper, and zookeeper is only to support listening mode
Subscriber is notified, without supporting RESTful (Representational State Transfer, abbreviation REST) to describe one
The network system of a framework pattern refers to one group of framework constraint condition and principle.Meet answering for these constraint conditions and principle
Be exactly RESTful with program or design) tool of interface notification subscriber, so, in the application developer oneself write or
Person calls existing RESTful notification component, and RESTful notification component is added in zookeeper, makes zookeeper branch
Hold RESTful interface notification.
The method of above-mentioned sending node Notification of Changes, includes the following steps:
S10, zookeeper server obtain node Notification of Changes, wherein the node Notification of Changes includes instant node
Path and change time；
S20, the first RESTful interface that subscriber's server is called using the notification component, by the node
Notification of Changes is sent to subscriber's server, and, the node Notification of Changes is stored in local first node and is become
In more notice set；
S30, on a preset condition based passes through the notification component and calls subscriber's server preset second
RESTful interface, and the first node Notification of Changes set is transferred to the subscriber by the 2nd RESTful interface and is taken
Business device.
As described in above-mentioned steps S10 and S20, zookeeper server is got after each node once changes, and can all be sent out
It plays a http and calls the first RESTful interface notification subscriber's server, and the node Notification of Changes storage of generation is arrived
One memory space of zookeeper server local, to form a first node Notification of Changes set.Because passing through
When http calls the first RESTful interface notification subscriber's server, there are network congestion or subscriber's servers
The system failure causes node Notification of Changes to be lost, i.e., zookeeper server has executed sending node Notification of Changes and ordered to described
After the side's of readding server, do not ensure that the subscribed square server of the node Notification of Changes receives.First node is changed and is collected
A memory space for being stored in zookeeper server local is closed, the node Notification of Changes stored in the memory space is not deposited
The case where losing.
As described in above-mentioned steps S30, above-mentioned preset condition is a kind of pre-set precondition, only reaches this
Precondition can just execute corresponding operation.In the application, above-mentioned preset condition includes a variety of, such as when must be some
Between qualifications, it is necessary to be the qualifications etc. of some collective data amount.In the present embodiment, when reaching above-mentioned default item
Part, just by the above-mentioned notification component calling preset 2nd RESTful interface of subscriber's server, and by described the
One node Notification of Changes set is transferred to subscriber's server by the 2nd RESTful interface.When subscriber's server connects
After receiving the first change node set, it can determine what it was not received according to the node Notification of Changes that it has been received
Node Notification of Changes, the node change for then subscriber's server in first node Notification of Changes set being called not receive are logical
The instant node path known, completes corresponding processing operation again.
In one embodiment, it is above-mentioned on a preset condition based, pass through the notification component and call subscriber's server
Preset 2nd RESTful interface, and the first node Notification of Changes set is transmitted by the 2nd RESTful interface
To the step S30 of subscriber's server, comprising:
S3011, to judge whether the quantity of the node Notification of Changes in the first node Notification of Changes set is equal to default
Amount threshold；
S3012, if so, calling preset 2nd RESTful of subscriber's server to connect by the notification component
Mouthful, and the first node Notification of Changes set is transferred to subscriber's server by the 2nd RESTful interface.
As described in above-mentioned steps S3011 and S3012, i.e., above-mentioned preset condition is the section in first node Notification of Changes set
The quantity of point Notification of Changes is equal to preset amount threshold, if amount threshold is 50, the node in first node notice set
When Notification of Changes quantity is 50, i.e., it can trigger and subscriber's server preset second is called by the notification component
RESTful interface, and the first node Notification of Changes set is transferred to the subscription by the 2nd RESTful interface
The operation of square server.Using amount threshold as preset condition, the node Notification of Changes in first node notice set can be prevented
When quantity is excessive, it is then forwarded in subscriber's server and causes network congestion.
In another embodiment, it is above-mentioned on a preset condition based, pass through the notification component and call subscriber service
The preset 2nd RESTful interface of device, and the first node Notification of Changes set is passed by the 2nd RESTful interface
It is defeated by the step S30 of subscriber's server, comprising:
The first node Notification of Changes set is once sent before S3021, acquisition to the first of subscriber's server
Time, and obtain the second current time；
S3022, judge whether the time difference of the first time and the second time are equal to preset time threshold；
S3023, if so, calling preset 2nd RESTful of subscriber's server to connect by the notification component
Mouthful, and the first node Notification of Changes set is transferred to subscriber's server by the 2nd RESTful interface.
As described in above-mentioned steps S3021 to S3023, i.e., above-mentioned preset condition once sends the first node change to be preceding
Notice was gathered to the first time of subscriber's server, and the time difference of the second current time is equal to the preset time
Threshold value currently once sends the first node Notification of Changes set and services to the subscriber if time threshold is 30 minutes
The first time of device is 30 minutes at 1 point in afternoons, and when the time is 2 pm on the same day, the time difference of the two is equal to the time
Threshold value can trigger and call the preset 2nd RESTful interface of subscriber's server by the notification component, and by institute
State the operation that the first node Notification of Changes set is transferred to subscriber's server by the 2nd RESTful interface.
In one embodiment, above-mentioned to transmit the first node Notification of Changes set by the 2nd RESTful interface
The step of to subscriber's server, comprising:
Preset handshake request is sent to subscriber's server；
If the successful feedback of shaking hands of subscriber's server is received, by the first node Notification of Changes set
Subscriber's server is transferred to by the 2nd RESTful interface.
In the present embodiment, receive shake hands successfully feedback after, just the first node Notification of Changes set is led to
It crosses the 2nd RESTful interface and is transferred to subscriber's server, first node Notification of Changes set can be prevented because of network
Obstructed reason is without being successfully sent to above-mentioned subscriber's server.Further, if not receiving subscriber's clothes
The successful feedback of shaking hands of business device, then give subscriber's server to send handshake request according to predeterminated frequency, until receiving
To after successfully feedback of shaking hands, it can just execute and transmit the first node Notification of Changes set by the 2nd RESTful interface
To the operation of subscriber's server.In at the appointed time length, successful feedback of shaking hands is not received, then generates alarm
Information is sent to preset terminal, in order to which staff goes and finds out what's going on, carries out technical treatment.
The method of the sending node Notification of Changes of the present embodiment, compared with prior art, when zookeeper server receives
To after the monitoring request of subscriber's server, not only corresponding node Notification of Changes can be sent to subscriber's server, can also
Node Notification of Changes is stored in local, local first node Notification of Changes set owner will be stored in after reaching preset condition
Dynamic is sent to subscriber's server, in order to which subscriber's server by utilizing first node Notification of Changes set search goes out loss
Node Notification of Changes, to supplement the processing completed to the node Notification of Changes of loss.
Referring to Fig. 2, the embodiment of the present application also provides a kind of method for preventing node Notification of Changes from losing, and takes for subscriber
Business device prevents zookeeper server by utilizing as the method for the sending node Notification of Changes in any of the above-described embodiment is sent
Node Notification of Changes is lost；The above-mentioned method for preventing node Notification of Changes from losing, includes the following steps:
S11, subscriber's server pass through the hair of zookeeper server described in the first RESTful interface
The node Notification of Changes sent, and the node Notification of Changes received is stored in preset memory space, it forms second node and becomes
More notice set；
S21, after receiving the first node Notification of Changes set that the zookeeper server is sent, in institute
It states to search the loss node for being not present in the second node Notification of Changes set in first node Notification of Changes set and change and lead to
Know；
S31, corresponding processing operation is completed according to the instant node path for losing node Notification of Changes.
As described in above-mentioned steps S11 to S31, the node Notification of Changes that zookeeper server is sent is to above-mentioned subscriber
When server, it may cause node Notification of Changes if there is the system failure of network congestion or subscriber's server and lose
It loses, i.e., the node Notification of Changes not necessarily zookeeper server that subscriber's server receives has transmitted to its
Whole node Notifications of Changes, it is understood that there may be the loss node Notification of Changes of loss.In this application, subscriber's server will record
Received node Notification of Changes, and it is stored in local, second node Notification of Changes set is formed, second node at this time becomes
Node Notification of Changes in more notice set changes the node Notification of Changes in being combined with first node, may be all identical,
The few a part of the node Notification of Changes in combining may be changed than first node, and this few a part is subscriber's server
The node Notification of Changes being not received by, that is, above-mentioned loss node Notification of Changes.When the loss node for finding out loss
After Notification of Changes, both corresponding processing operation can be completed according to the instant node path for losing node Notification of Changes, so as to order
Processing of server supplement in the side's of readding to node Notification of Changes is lost.
In one embodiment, above-mentioned when the first node change for receiving the zookeeper server transmission
After notice set, is searched in the first node Notification of Changes set and be not present in the second node Notification of Changes set
Lose node Notification of Changes step S21 include:
S2111, after receiving the first node Notification of Changes set that the zookeeper server is sent, mention
The first of each of first node Notification of Changes set node Notification of Changes is taken to change the time；
S2112, into the second node Notification of Changes set, lookup is identical with the first change time described in each
Second change time；
S2113, acquisition do not find the remaining first change time of identical second change time, by remaining institute
It states the first change time corresponding node Notification of Changes and is denoted as the loss node Notification of Changes.
As described in above-mentioned steps S2111 to S2113, because of change time when node Notification of Changes is with generation notice,
So using the change time of node Notification of Changes as the node judged in first node Notification of Changes set in the present embodiment
The whether identical foundation of node Notification of Changes in Notification of Changes and second node Notification of Changes set, if first node changes
Node Notification of Changes in notice set is identical as the node Notification of Changes in second node Notification of Changes set, then illustrates the section
The subscribed square server of point Notification of Changes receives and processes, if it is not the same, then illustrating that the node Notification of Changes is losing for loss
A disloyal point Notification of Changes.
In one embodiment, above-mentioned to receive the zookeeper server transmission first node Notification of Changes collection
After conjunction, the loss node change for being not present in second node Notification of Changes set is searched in the first node Notification of Changes set
After the step S21 more notified, further includes:
S2101, the quantity for calculating the loss node Notification of Changes account in the first node Notification of Changes set all
The ratio value of the quantity of node Notification of Changes；
If S2102, the ratio value are greater than preset proportion threshold value, warning message is generated.
As described in above-mentioned steps S2101 and S2102, node Notification of Changes is lost if there is a large amount of, then illustrates exist
The serious problems such as network congestion or the system failure of subscriber's server generate warning message in order to which staff is timely
Situation is solved, is repaired accordingly.Warning message can be sound/light physical alert, be also possible to through texts such as mail, short messages
The alarm of font formula.
The method for preventing node Notification of Changes from losing of the application, by receiving store in zookeeper server the
The second node Notification of Changes set stored in one node Notification of Changes set and subscriber's server, both can be quick
The node Notification of Changes lacked in second node Notification of Changes set relative to first node Notification of Changes collection kind is found out, these
The node Notification of Changes lacked is the loss node Notification of Changes that subscriber's server is not received by, it is ensured that zookeeper
The reasons such as congestion, subscriber's system failure loss will not occur because of network in the Notification of Changes of node.
Referring to Fig. 3, also a kind of device of sending node Notification of Changes of the embodiment of the present application is used for zookeeper server
To subscriber's server sending node Notification of Changes, being equipped in the zookeeper server makes zookeeper server branch
The notification component of RESTful interface calling is held, described device includes:
Acquiring unit 10 obtains node Notification of Changes for zookeeper server, wherein the node Notification of Changes
Including instant node path and change time；
Storage unit 20 is sent, for calling the first RESTful of subscriber's server using the notification component
Interface sends the node Notification of Changes to subscriber's server, and, the node Notification of Changes is stored in this
In the first node Notification of Changes set on ground；
Transmission unit 30 is called, on a preset condition based, calling subscriber's server by the notification component
Preset 2nd RESTful interface, and the first node Notification of Changes set is transferred to institute by the 2nd RESTful interface
State subscriber's server.
Such as above-mentioned acquiring unit 10 and transmission storage unit 20, zookeeper server gets each node and once becomes
After more, it can all initiate a http and call the first RESTful interface notification subscriber's server, and the node of generation is changed
A memory space of zookeeper server local is arrived in notice storage, to form a first node Notification of Changes set.Cause
For when calling the first RESTful interface notification subscriber's server by http, there are network congestion or subscribers
The system failure of server causes node Notification of Changes to be lost, i.e., zookeeper server has executed sending node Notification of Changes
After subscriber's server, do not ensure that the subscribed square server of the node Notification of Changes receives.By first segment
Point change set is stored in a memory space of zookeeper server local, the node change stored in the memory space
There is no lose notice.
Such as above-mentioned calling transmission unit 30, above-mentioned preset condition is a kind of pre-set precondition, is only reached
This precondition can just execute corresponding operation.In the application, above-mentioned preset condition includes a variety of, for example must be a certain
The qualifications of a time, it is necessary to be the qualifications etc. of some collective data amount.In the present embodiment, when reaching above-mentioned pre-
If condition, just by the above-mentioned notification component calling preset 2nd RESTful interface of subscriber's server, and by the institute
It states first node Notification of Changes set and subscriber's server is transferred to by the 2nd RESTful interface.When subscriber services
After device receives the first change node set, it can determine that it is not received according to the node Notification of Changes that it has been received
The node Notification of Changes arrived, the node for then subscriber's server in first node Notification of Changes set being called not receive become
The instant node path more notified, completes corresponding processing operation again.
In one embodiment, above-mentioned calling transmission unit 30, comprising:
First judgment module, for judging that the quantity of the node Notification of Changes in the first node Notification of Changes set is
It is no to be equal to preset amount threshold；
First calls sending module, if the quantity for the node Notification of Changes in the first node Notification of Changes set
Equal to preset amount threshold, then preset 2nd RESTful of subscriber's server is called to connect by the notification component
Mouthful, and the first node Notification of Changes set is transferred to subscriber's server by the 2nd RESTful interface.
If above-mentioned first judgment module and first call sending module, i.e., above-mentioned preset condition is first node Notification of Changes
The quantity of node Notification of Changes in set is equal to preset amount threshold, if amount threshold is 50, when first node notifies to collect
When node Notification of Changes quantity in conjunction is 50, i.e., it can trigger and call subscriber's server default by the notification component
The 2nd RESTful interface, and the first node Notification of Changes set is transferred to institute by the 2nd RESTful interface
State the operation of subscriber's server.Using amount threshold as preset condition, it can prevent the node in first node notice set from becoming
When more notice quantity is excessive, it is then forwarded in subscriber's server and causes network congestion.
In another embodiment, above-mentioned calling transmission unit 30, comprising:
Module is obtained, for once sending the first node Notification of Changes set to subscriber's server before obtaining
First time, and obtain the second current time；
Second judgment module, for judging whether the time difference of the first time and the second time are equal to the preset time
Threshold value；
If second calls sending module, the time difference to be equal to preset time threshold, pass through the notification component tune
With the preset 2nd RESTful interface of subscriber's server, and the first node Notification of Changes set is passed through
2nd RESTful interface is transferred to subscriber's server.
If above-mentioned acquisition module, the second judgment module and second call sending module, i.e., above-mentioned preset condition is preceding primary
The first node Notification of Changes set is sent to the first time of subscriber's server, and the second current time
Time difference is equal to preset time threshold, if time threshold is 30 minutes, currently once sends the first node Notification of Changes
Gathering to the first time of subscriber's server is 30 minutes at 1 point in afternoons, when the time is 2 pm on the same day,
The time difference of the two is equal to time threshold, i.e., can trigger and call subscriber's server preset the by the notification component
Two RESTful interfaces, and the first node Notification of Changes set is transferred to described order by the 2nd RESTful interface
The operation of the side's of readding server.
In one embodiment, above-mentioned calling transmission unit 30, comprising:
Sending module, for sending preset handshake request to subscriber's server；
Transmission module, if the successful feedback of shaking hands for receiving subscriber's server, by the first segment
Point Notification of Changes set is transferred to subscriber's server by the 2nd RESTful interface.
In the present embodiment, receive shake hands successfully feedback after, just the first node Notification of Changes set is led to
It crosses the 2nd RESTful interface and is transferred to subscriber's server, first node Notification of Changes set can be prevented because of network
Obstructed reason is without being successfully sent to above-mentioned subscriber's server.Further, if not receiving subscriber's clothes
The successful feedback of shaking hands of business device, then give subscriber's server to send handshake request according to predeterminated frequency, until receiving
To after successfully feedback of shaking hands, it can just execute and transmit the first node Notification of Changes set by the 2nd RESTful interface
To the operation of subscriber's server.In at the appointed time length, successful feedback of shaking hands is not received, then generates alarm
Information is sent to preset terminal, in order to which staff goes and finds out what's going on, carries out technical treatment.
The device of the sending node Notification of Changes of the present embodiment, when zookeeper server receives subscriber's server
Monitoring request after, not only corresponding node Notification of Changes can be sent to subscriber's server, can also be by node Notification of Changes
It is stored in local, is sent to subscription for be stored in local first node Notification of Changes set active after reaching preset condition
Square server, in order to which subscriber's server by utilizing first node Notification of Changes set search goes out the node Notification of Changes lost,
To supplement the processing completed to the node Notification of Changes of loss.
Referring to Fig. 4, also a kind of device for preventing node Notification of Changes from losing of the embodiment of the present application is used for subscriber's server
The section that the method for preventing sending node Notification of Changes of the zookeeper server by utilizing as described in any of the above-described embodiment is sent
Point Notification of Changes is lost；The device for preventing node Notification of Changes from losing, comprising:
Receiving unit 11 passes through described in the first RESTful interface for subscriber's server
The node Notification of Changes that zookeeper server is sent, and the node Notification of Changes received is stored in preset storage sky
Between, form second node Notification of Changes set；
Searching unit 21, for when the first node Notification of Changes for receiving the zookeeper server transmission
After set, the loss for being not present in the second node Notification of Changes set is searched in the first node Notification of Changes set
Node Notification of Changes；
Processing unit 31, for completing corresponding processing behaviour according to the instant node path for losing node Notification of Changes
Make.
Such as above-mentioned receiving unit 11, searching unit 21 and processing unit 31, the node change that zookeeper server is sent
When notice to above-mentioned subscriber's server, it may be led if there is network congestion or the system failure of subscriber's server
Node Notification of Changes is caused to lose, i.e., the node Notification of Changes not necessarily zookeeper that subscriber's server receives is serviced
Device has transmitted to its whole node Notifications of Changes, it is understood that there may be the loss node Notification of Changes of loss.In this application, it orders
The side's of readding server will record received node Notification of Changes, and be stored in local, form second node Notification of Changes set,
The node Notification of Changes in second node Notification of Changes set at this time changes the node Notification of Changes in being combined with first node,
It may be all identical, it is also possible to it is few more a part of than the node Notification of Changes in first node change combination, and this few a part
The as node Notification of Changes that is not received by of subscriber's server, that is, above-mentioned loss node Notification of Changes.Work as lookup
After the loss node Notification of Changes lost out, it can both be completed according to the instant node path for losing node Notification of Changes corresponding
Processing operation, so that processing of subscriber's server supplement to node Notification of Changes is lost.
In one embodiment, above-mentioned searching unit 21, comprising:
Extraction module, for when the first node Notification of Changes collection for receiving the zookeeper server transmission
After conjunction, the first change time of each of first node Notification of Changes set node Notification of Changes is extracted；
Searching module, for being searched into the second node Notification of Changes set and each first change time
The identical second change time；
Confirmation unit, when for obtaining the remaining described first change for not finding the identical second change time
Between, time corresponding node Notification of Changes, which is changed, by remaining described first is denoted as the loss node Notification of Changes.
Such as above-mentioned extraction module, searching module and confirmation unit, because node Notification of Changes is with the change generated when notifying
The more time, so using the change time of node Notification of Changes as judging in first node Notification of Changes set in the present embodiment
Node Notification of Changes and second node Notification of Changes set in the whether identical foundation of node Notification of Changes, if first segment
Node Notification of Changes in point Notification of Changes set is identical as the node Notification of Changes in second node Notification of Changes set, then says
The subscribed square server of the bright node Notification of Changes receives and processes, if it is not the same, then illustrating that the node Notification of Changes is to lose
The loss node Notification of Changes of mistake.
In one embodiment, the above-mentioned device for preventing node Notification of Changes from losing, further includes:
Ratio computing unit accounts for the first node Notification of Changes for calculating the quantity for losing node Notification of Changes
The ratio value of the quantity of whole node Notifications of Changes in set；
Generation unit generates warning message if being greater than preset proportion threshold value for the ratio value.
Such as aforementioned proportion computing unit and generation unit, node Notification of Changes is lost if there is a large amount of, then explanation is deposited
In the serious problems such as network congestion or the system failure of subscriber's server, warning message is generated in order to which staff is timely
It goes and finds out what's going on, is repaired accordingly.Warning message can be sound/light physical alert, be also possible to through mail, short message etc.
The alarm of written form.
The device for preventing node Notification of Changes from losing of the application, by receiving store in zookeeper server the
The second node Notification of Changes set stored in one node Notification of Changes set and subscriber's server, both can be quick
The node Notification of Changes lacked in second node Notification of Changes set relative to first node Notification of Changes collection kind is found out, these
The node Notification of Changes lacked is the loss node Notification of Changes that subscriber's server is not received by, it is ensured that zookeeper
The reasons such as congestion, subscriber's system failure loss will not occur because of network in the Notification of Changes of node.
Referring to Fig. 5, a kind of computer equipment is also provided in the embodiment of the present application, which can be above-mentioned pipe
It manages server or the corresponding server of management node, internal structure can be as shown in Figure 5.The computer equipment includes logical
Cross processor, memory, network interface and the database of system bus connection.Wherein, the processor of the Computer Design is used for
Calculating and control ability are provided.The memory of the computer equipment includes non-volatile memory medium, built-in storage.This is non-volatile
Property storage medium is stored with operating system, computer program and database.The internal memory is the behaviour in non-volatile memory medium
The operation for making system and computer program provides environment.The database of the computer equipment is for storing first node Notification of Changes
The data such as set or second node Notification of Changes set.The network interface of the computer equipment is used to pass through with external terminal
Network connection communication.A kind of method when the computer program is executed by processor to realize sending node Notification of Changes, or
The method for preventing node Notification of Changes from losing.
In one embodiment, it when above-mentioned processor executes the method for above-mentioned sending node Notification of Changes, is used for
To subscriber's server sending node Notification of Changes, be equipped in the zookeeper server makes zookeeper server
The notification component that zookeeper server supports RESTful interface to call, the method for the sending node Notification of Changes include:
Zookeeper server obtains node Notification of Changes, wherein when the node Notification of Changes includes instant node path and change
Between；The first RESTful interface that subscriber's server is called using the notification component, by the node Notification of Changes to
Subscriber's server is sent, and, the node Notification of Changes is stored in local first node Notification of Changes set
In；On a preset condition based, the preset 2nd RESTful interface of subscriber's server is called by the notification component, and
The first node Notification of Changes set is transferred to subscriber's server by the 2nd RESTful interface.
In one embodiment, it is above-mentioned on a preset condition based, pass through the notification component and call subscriber's server
Preset 2nd RESTful interface, and the first node Notification of Changes set is transmitted by the 2nd RESTful interface
The step of to subscriber's server, comprising: judge the node Notification of Changes in the first node Notification of Changes set
Whether quantity is equal to preset amount threshold；If so, calling subscriber's server preset by the notification component
2nd RESTful interface, and the first node Notification of Changes set is transferred to by the 2nd RESTful interface described
Subscriber's server.
In one embodiment, it is above-mentioned on a preset condition based, pass through the notification component and call subscriber's server
Preset 2nd RESTful interface, and the first node Notification of Changes set is transmitted by the 2nd RESTful interface
The step of to subscriber's server, comprising: once send the first node Notification of Changes set before obtaining and ordered to described
The first time of the side's of readding server, and obtain the second current time；Judge the time of the first time and the second time
Whether difference is equal to preset time threshold；If so, calling subscriber's server preset the by the notification component
Two RESTful interfaces, and the first node Notification of Changes set is transferred to described order by the 2nd RESTful interface
The side's of readding server.
In another embodiment, it when above-mentioned processor executes the above-mentioned method for preventing node Notification of Changes from losing, is used for
The method that subscriber's server prevents zookeeper server by utilizing sending node Notification of Changes as described in any one of the above embodiments is sent out
The node Notification of Changes sent is lost；The method for preventing node Notification of Changes from losing, comprising: subscriber's server passes through
The node Notification of Changes that zookeeper server described in the first RESTful interface is sent, and the node that will be received
Notification of Changes is stored in preset memory space, forms second node Notification of Changes set；It is taken when receiving the zookeeper
It is engaged in after the first node Notification of Changes set that device is sent, searches and be not present in the first node Notification of Changes set
The loss node Notification of Changes of the second node Notification of Changes set；According to the instant node for losing node Notification of Changes
Complete corresponding processing operation in path.
In one embodiment, above-mentioned search in the first node Notification of Changes set is not present in second node change
The step of more notifying the loss node Notification of Changes of set includes: to extract each of described first node Notification of Changes set
The first change time of node Notification of Changes；It is searched into the second node Notification of Changes set and each first change
The more time identical second change time；When obtaining the remaining first change for not finding the identical second change time
Between, time corresponding node Notification of Changes, which is changed, by remaining described first is denoted as the loss node Notification of Changes.
In one embodiment, above-mentioned to receive the zookeeper server transmission first node Notification of Changes collection
After conjunction, the loss node change for being not present in second node Notification of Changes set is searched in the first node Notification of Changes set
After the step of more notifying, further includes: calculate the quantity for losing node Notification of Changes and account for the first node Notification of Changes
The ratio value of the quantity of whole node Notifications of Changes in set；If the ratio value is greater than preset proportion threshold value, report is generated
Alert information.
It will be understood by those skilled in the art that structure shown in Fig. 5, only part relevant to application scheme is tied
The block diagram of structure does not constitute the restriction for the computer equipment being applied thereon to application scheme.
The computer equipment of the embodiment of the present application is changed logical by the first node stored in zookeeper server
Know the second node Notification of Changes set stored in set and subscriber's server, both can quickly find out the second section
The node Notification of Changes lacked in point Notification of Changes set relative to first node Notification of Changes collection kind, these nodes lacked become
More notice is the loss node Notification of Changes that subscriber's server is not received by, it is ensured that the change of zookeeper node is logical
The reasons such as congestion, subscriber's system failure loss will not be occurred because of network by knowing.
The embodiment of the present application also provides a kind of computer readable storage medium, is stored thereon with computer program, computer
A kind of method that sending node Notification of Changes is realized when program is executed by processor, or the side for preventing node Notification of Changes from losing
Method.
In one embodiment, it when above-mentioned processor executes the method for above-mentioned sending node Notification of Changes, is used for
To subscriber's server sending node Notification of Changes, be equipped in the zookeeper server makes zookeeper server
The notification component that zookeeper server supports RESTful interface to call, the method for the sending node Notification of Changes include:
Zookeeper server obtains node Notification of Changes, wherein when the node Notification of Changes includes instant node path and change
Between；The first RESTful interface that subscriber's server is called using the notification component, by the node Notification of Changes to
Subscriber's server is sent, and, the node Notification of Changes is stored in local first node Notification of Changes set
In；On a preset condition based, the preset 2nd RESTful interface of subscriber's server is called by the notification component, and
The first node Notification of Changes set is transferred to subscriber's server by the 2nd RESTful interface.
In one embodiment, it is above-mentioned on a preset condition based, pass through the notification component and call subscriber's server
Preset 2nd RESTful interface, and the first node Notification of Changes set is transmitted by the 2nd RESTful interface
The step of to subscriber's server, comprising: judge the node Notification of Changes in the first node Notification of Changes set
Whether quantity is equal to preset amount threshold；If so, calling subscriber's server preset by the notification component
2nd RESTful interface, and the first node Notification of Changes set is transferred to by the 2nd RESTful interface described
Subscriber's server.
In one embodiment, it is above-mentioned on a preset condition based, pass through the notification component and call subscriber's server
Preset 2nd RESTful interface, and the first node Notification of Changes set is transmitted by the 2nd RESTful interface
The step of to subscriber's server, comprising: once send the first node Notification of Changes set before obtaining and ordered to described
The first time of the side's of readding server, and obtain the second current time；Judge the time of the first time and the second time
Whether difference is equal to preset time threshold；If so, calling subscriber's server preset the by the notification component
Two RESTful interfaces, and the first node Notification of Changes set is transferred to described order by the 2nd RESTful interface
The side's of readding server.
In another embodiment, it when above-mentioned processor executes the above-mentioned method for preventing node Notification of Changes from losing, is used for
The method that subscriber's server prevents zookeeper server by utilizing sending node Notification of Changes as described in any one of the above embodiments is sent out
The node Notification of Changes sent is lost；The method for preventing node Notification of Changes from losing, comprising: subscriber's server passes through
The node Notification of Changes that zookeeper server described in the first RESTful interface is sent, and the node that will be received
Notification of Changes is stored in preset memory space, forms second node Notification of Changes set；It is taken when receiving the zookeeper
It is engaged in after the first node Notification of Changes set that device is sent, searches and be not present in the first node Notification of Changes set
The loss node Notification of Changes of the second node Notification of Changes set；According to the instant node for losing node Notification of Changes
Complete corresponding processing operation in path.
In one embodiment, above-mentioned search in the first node Notification of Changes set is not present in second node change
The step of more notifying the loss node Notification of Changes of set includes: to extract each of described first node Notification of Changes set
The first change time of node Notification of Changes；It is searched into the second node Notification of Changes set and each first change
The more time identical second change time；Obtain remaining first change for not finding the identical second change time
Time changes time corresponding node Notification of Changes for remaining described first and is denoted as the loss node Notification of Changes.
In one embodiment, above-mentioned to receive the zookeeper server transmission first node Notification of Changes collection
After conjunction, the loss node change for being not present in second node Notification of Changes set is searched in the first node Notification of Changes set
After the step of more notifying, further includes: calculate the quantity for losing node Notification of Changes and account for the first node Notification of Changes
The ratio value of the quantity of whole node Notifications of Changes in set；If the ratio value is greater than preset proportion threshold value, report is generated
Alert information.
Those of ordinary skill in the art will appreciate that realizing all or part of the process in above-described embodiment method, being can be with
Relevant hardware is instructed to complete by computer program, the computer program can be stored in a non-volatile computer
In read/write memory medium, the computer program is when being executed, it may include such as the process of the embodiment of above-mentioned each method.Wherein,
Any reference used in provided herein and embodiment to memory, storage, database or other media,
Including non-volatile and/or volatile memory.Nonvolatile memory may include read-only memory (ROM), programming ROM
(PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM) or flash memory.Volatile memory may include
Random access memory (RAM) or external cache.By way of illustration and not limitation, RAM is available in many forms,
Such as static state RAM (SRAM), dynamic ram (DRAM), synchronous dram (SDRAM), double speed are according to rate SDRAM (SSRSDRAM), enhancing
Type SDRAM (ESDRAM), synchronization link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM
(RDRAM), direct memory bus dynamic ram (DRDRAM) and memory bus dynamic ram (RDRAM) etc..
The foregoing is merely preferred embodiment of the present application, are not intended to limit the scope of the patents of the application, all utilizations
Equivalent structure or equivalent flow shift made by present specification and accompanying drawing content is applied directly or indirectly in other correlations
Technical field, similarly include in the scope of patent protection of the application.
Claims (10)
1. a kind of method of sending node Notification of Changes becomes for zookeeper server to subscriber's server sending node
It more notifies, the notice for making zookeeper server that RESTful interface be supported to call is installed in the zookeeper server
Component, which is characterized in that the method for the sending node Notification of Changes includes:
Zookeeper server obtains node Notification of Changes, wherein the node Notification of Changes includes instant node path and change
The more time；
The first RESTful interface that subscriber's server is called using the notification component, by the node Notification of Changes
It is sent to subscriber's server, and, the node Notification of Changes is stored in local first node Notification of Changes collection
In conjunction；
On a preset condition based, the preset 2nd RESTful interface of subscriber's server is called by the notification component, and
The first node Notification of Changes set is transferred to subscriber's server by the 2nd RESTful interface.
2. the method for sending node Notification of Changes according to claim 1, which is characterized in that it is described on a preset condition based,
The preset 2nd RESTful interface of subscriber's server is called by the notification component, and by the first segment
The step of point Notification of Changes set is transferred to subscriber's server by the 2nd RESTful interface, comprising:
Judge whether the quantity of the node Notification of Changes in the first node Notification of Changes set is equal to preset amount threshold；
If so, calling the preset 2nd RESTful interface of subscriber's server by the notification component, and will be described
The first node Notification of Changes set is transferred to subscriber's server by the 2nd RESTful interface.
3. the method for sending node Notification of Changes according to claim 1, which is characterized in that it is described on a preset condition based,
The preset 2nd RESTful interface of subscriber's server is called by the notification component, and by the first segment
The step of point Notification of Changes set is transferred to subscriber's server by the 2nd RESTful interface, comprising:
The first node Notification of Changes set is once sent to the first time of subscriber's server before obtaining, and is obtained
Take the second current time；
Judge whether the time difference of the first time and the second time are equal to preset time threshold；
If so, calling the preset 2nd RESTful interface of subscriber's server by the notification component, and will be described
The first node Notification of Changes set is transferred to subscriber's server by the 2nd RESTful interface.
4. a kind of method for preventing node Notification of Changes from losing, prevents zookeeper server by utilizing for subscriber's server
The node Notification of Changes that the method for sending node Notification of Changes as claimed in any one of claims 1-3 is sent is lost；It is special
Sign is, the method for preventing node Notification of Changes from losing, comprising:
The node that subscriber's server is sent by zookeeper server described in the first RESTful interface
Notification of Changes, and the node Notification of Changes received is stored in preset memory space, form second node Notification of Changes collection
It closes；
After receiving the first node Notification of Changes set that the zookeeper server is sent, in the first segment
The loss node Notification of Changes for being not present in the second node Notification of Changes set is searched in point Notification of Changes set；
Corresponding processing operation is completed according to the instant node path for losing node Notification of Changes.
5. the method according to claim 4 for preventing node Notification of Changes from losing, which is characterized in that described described first
The step of being not present in the loss node Notification of Changes of second node Notification of Changes set packet is searched in node Notification of Changes set
It includes:
Extract the first change time of each of first node Notification of Changes set node Notification of Changes；
When searching the second change identical with the first change time described in each into the second node Notification of Changes set
Between；
The remaining first change time for not finding the identical second change time is obtained, by remaining described first
The change time, corresponding node Notification of Changes was denoted as the loss node Notification of Changes.
6. the method according to claim 5 for preventing node Notification of Changes from losing, which is characterized in that described to receive institute
After stating zookeeper server transmission first node Notification of Changes set, searched in the first node Notification of Changes set
After the step of being not present in the loss node Notification of Changes of second node Notification of Changes set, further includes:
It calculates the quantity for losing node Notification of Changes and accounts for whole nodes in the first node Notification of Changes set and change and lead to
The ratio value for the quantity known；
If the ratio value is greater than preset proportion threshold value, warning message is generated.
7. a kind of device of sending node Notification of Changes becomes for zookeeper server to subscriber's server sending node
It more notifies, the notice for making zookeeper server that RESTful interface be supported to call is installed in the zookeeper server
Component, which is characterized in that described device includes:
Acquiring unit obtains node Notification of Changes for zookeeper server, wherein the node Notification of Changes includes real
Example node path and change time；
Storage unit is sent, it, will for calling the first RESTful interface of subscriber's server using the notification component
The node Notification of Changes is sent to subscriber's server, and, the node Notification of Changes is stored in local
In one node Notification of Changes set；
Transmission unit is called, on a preset condition based, calling subscriber's server preset by the notification component
2nd RESTful interface, and the first node Notification of Changes set is transferred to the subscription by the 2nd RESTful interface
Square server.
8. a kind of device for preventing node Notification of Changes from losing, prevents zookeeper server by utilizing for subscriber's server
The node Notification of Changes that the method for sending node Notification of Changes as claimed in any one of claims 1-3 is sent is lost；It is special
Sign is, the device for preventing node Notification of Changes from losing, comprising:
Receiving unit passes through the service of zookeeper described in the first RESTful interface for subscriber's server
The node Notification of Changes that device is sent, and the node Notification of Changes received is stored in preset memory space, form the second section
Point Notification of Changes set；
Searching unit, for after receiving the first node Notification of Changes set that the zookeeper server is sent,
The loss node change for being not present in the second node Notification of Changes set is searched in the first node Notification of Changes set
More notify；
Processing unit, for completing corresponding processing operation according to the instant node path for losing node Notification of Changes.
9. a kind of computer equipment, including memory and processor, the memory are stored with computer program, feature exists
In the processor realizes sending node Notification of Changes described in any one of claims 1 to 3 when executing the computer program
Method the step of, or realize the step for the method for preventing node Notification of Changes from losing described in any one of claim 4 to 6
Suddenly.
10. a kind of computer readable storage medium, is stored thereon with computer program, which is characterized in that the computer program
The step of method of sending node Notification of Changes described in any one of claims 1 to 3 is realized when being executed by processor, Huo Zheshi
The step of method for preventing node Notification of Changes from losing described in any one of existing claim 4 to 6.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910305189.8A CN110166528B (en) | 2019-04-16 | 2019-04-16 | Method and device for preventing node change notification from being lost and computer equipment |
| PCT/CN2019/118161 WO2020211361A1 (en) | 2019-04-16 | 2019-11-13 | Method for preventing loss of node change notification, device and computer apparatus |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910305189.8A CN110166528B (en) | 2019-04-16 | 2019-04-16 | Method and device for preventing node change notification from being lost and computer equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110166528A true CN110166528A (en) | 2019-08-23 |
| CN110166528B CN110166528B (en) | 2022-03-18 |
Family
ID=67639613
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910305189.8A Active CN110166528B (en) | 2019-04-16 | 2019-04-16 | Method and device for preventing node change notification from being lost and computer equipment |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN110166528B (en) |
| WO (1) | WO2020211361A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020211361A1 (en) * | 2019-04-16 | 2020-10-22 | 平安科技（深圳）有限公司 | Method for preventing loss of node change notification, device and computer apparatus |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH033054A (en) * | 1989-05-31 | 1991-01-09 | Yokogawa Electric Corp | Method for preventing communication data from being missed |
| US6687848B1 (en) * | 2000-05-31 | 2004-02-03 | Sun Microsystems, Inc. | Techniques for preventing information loss in a business to business message in an enterprise computer system |
| CN1822533A (en) * | 2006-03-27 | 2006-08-23 | 阿里巴巴公司 | Message reliable informing method and system between systems |
| CN105282118A (en) * | 2014-07-21 | 2016-01-27 | 中兴通讯股份有限公司 | Control resource change notification message sending method and apparatus |
| CN106712981A (en) * | 2015-07-23 | 2017-05-24 | 阿里巴巴集团控股有限公司 | Method and device for informing node change |
| CN106980643A (en) * | 2017-02-14 | 2017-07-25 | 阿里巴巴集团控股有限公司 | Change sending method, device and the electronic equipment of message |
| CN108255592A (en) * | 2017-12-19 | 2018-07-06 | 武汉市烽视威科技有限公司 | A kind of Quartz clusters timing task processing system and method |
| CN108984544A (en) * | 2017-05-31 | 2018-12-11 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus of distributed system modification configuration information |
| CN109525466A (en) * | 2019-01-03 | 2019-03-26 | 杭州云英网络科技有限公司 | Back end monitor method and device |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104092718B (en) * | 2013-12-12 | 2017-10-24 | 腾讯数码（天津）有限公司 | The update method of configuration information in distributed system and distributed system |
| CN104636135B (en) * | 2014-12-31 | 2018-05-04 | 北京奇虎科技有限公司 | A kind of node visit method and system, Client Agent and client |
| US10887173B2 (en) * | 2016-12-21 | 2021-01-05 | Juniper Networks, Inc. | Communicating state information in distributed operating systems |
| CN110166528B (en) * | 2019-04-16 | 2022-03-18 | 平安科技（深圳）有限公司 | Method and device for preventing node change notification from being lost and computer equipment |
-
2019
- 2019-04-16 CN CN201910305189.8A patent/CN110166528B/en active Active
- 2019-11-13 WO PCT/CN2019/118161 patent/WO2020211361A1/en active Application Filing
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH033054A (en) * | 1989-05-31 | 1991-01-09 | Yokogawa Electric Corp | Method for preventing communication data from being missed |
| US6687848B1 (en) * | 2000-05-31 | 2004-02-03 | Sun Microsystems, Inc. | Techniques for preventing information loss in a business to business message in an enterprise computer system |
| CN1822533A (en) * | 2006-03-27 | 2006-08-23 | 阿里巴巴公司 | Message reliable informing method and system between systems |
| US20110173495A1 (en) * | 2006-03-27 | 2011-07-14 | Alibaba Group Holding Limited | Method and System for Reliable Intersystem Message Notification |
| CN105282118A (en) * | 2014-07-21 | 2016-01-27 | 中兴通讯股份有限公司 | Control resource change notification message sending method and apparatus |
| CN106712981A (en) * | 2015-07-23 | 2017-05-24 | 阿里巴巴集团控股有限公司 | Method and device for informing node change |
| CN106980643A (en) * | 2017-02-14 | 2017-07-25 | 阿里巴巴集团控股有限公司 | Change sending method, device and the electronic equipment of message |
| CN108984544A (en) * | 2017-05-31 | 2018-12-11 | 北京京东尚科信息技术有限公司 | A kind of method and apparatus of distributed system modification configuration information |
| CN108255592A (en) * | 2017-12-19 | 2018-07-06 | 武汉市烽视威科技有限公司 | A kind of Quartz clusters timing task processing system and method |
| CN109525466A (en) * | 2019-01-03 | 2019-03-26 | 杭州云英网络科技有限公司 | Back end monitor method and device |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2020211361A1 (en) * | 2019-04-16 | 2020-10-22 | 平安科技（深圳）有限公司 | Method for preventing loss of node change notification, device and computer apparatus |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2020211361A1 (en) | 2020-10-22 |
| CN110166528B (en) | 2022-03-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CA2849961C (en) | System and method for disaster recovery | |
| CN108965381A (en) | Implementation of load balancing, device, computer equipment and medium based on Nginx | |
| CN109714319A (en) | Management system, method, apparatus, computer equipment and the storage medium of micro services | |
| US11361027B2 (en) | Historical state management in databases | |
| CN108062243B (en) | Execution plan generation method, task execution method and device | |
| CN113055421B (en) | Service grid management method and system | |
| CN104023083A (en) | Method and device for log collection cluster load balance | |
| CN111861140A (en) | Service processing method, device, storage medium and electronic device | |
| CN105653425A (en) | Complicated event processing engine based monitoring system | |
| CN106533944A (en) | Distributed API gateway, management method and management system | |
| CN106648903A (en) | Method and system for calling distributed file system | |
| CN103888539B (en) | Bootstrap technique, device and the P2P caching systems of P2P cachings | |
| CN109787827B (en) | CDN network monitoring method and device | |
| US20140143202A1 (en) | Regulated Texting Solution for Mobile Devices | |
| CN109428779A (en) | A kind of monitoring alarm method and device of distributed service | |
| CA2911989C (en) | Method, system and apparatus for dectecting instant message spam | |
| CN109495567A (en) | A kind of dispositions method of static routing, equipment and system | |
| CN110309109A (en) | Data monitoring method, device, computer equipment and storage medium | |
| CN109992427A (en) | DPI correlation rule backfills processing method, device, equipment and medium | |
| US8224933B2 (en) | Method and apparatus for case-based service composition | |
| CN108834148B (en) | 5G-oriented NFV-based fraud telephone handling system and method | |
| CN110166528A (en) | The method, apparatus and computer equipment for preventing node Notification of Changes from losing | |
| CN112699136B (en) | Cross-link certificate storage method and related device | |
| CN107959696A (en) | A kind of daily record bill processing method and system | |
| CN113905129A (en) | Method and device for intercepting crank call |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |