CN110213309A - A kind of method, equipment and the storage medium of binding relationship management - Google Patents
A kind of method, equipment and the storage medium of binding relationship management Download PDFInfo
- Publication number
- CN110213309A CN110213309A CN201810205327.0A CN201810205327A CN110213309A CN 110213309 A CN110213309 A CN 110213309A CN 201810205327 A CN201810205327 A CN 201810205327A CN 110213309 A CN110213309 A CN 110213309A
- Authority
- CN
- China
- Prior art keywords
- pod object
- container
- task
- pod
- newly
- 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
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/255—Maintenance or indexing of mapping tables
- H04L61/2553—Binding renewal aspects, e.g. using keep-alive messages
-
- 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/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
-
- 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/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- 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/56—Provisioning of proxy services
- H04L67/568—Storing data temporarily at an intermediate stage, e.g. caching
- H04L67/5682—Policies or rules for updating, deleting or replacing the stored data
Abstract
The embodiment of the present application discloses a kind of method of binding relationship management, it include: the update event for monitoring pea pods POD object in target collection, each POD object in target collection includes the description information that container is corresponded in container arranging system, container arranging system includes multiple containers, and at least one of multiple containers have binding relationship with load balancer；If the POD object listened in target collection is updated, it is determined that the POD object of update is newly-increased POD object or POD object to be deleted；If it is determined that the POD object updated is newly-increased POD object, then the binding relationship of container and load balancer corresponding to newly-increased POD object is established；If it is determined that the POD object updated is POD object to be deleted, then the binding relationship of container and load balancer corresponding to POD object to be deleted is released.The scheme of the embodiment of the present application can reduce the consumption to system resource.
Description
Technical field
This application involves field of cloud computer technology, and in particular to a kind of method, equipment and the computer of binding relationship management
Readable storage medium storing program for executing.
Background technique
With the rapid development of Internet technology, the background service equipment of various applications is mostly realized by cloud system
's.In cloud system container arranging system (such as: multiple containers can be created on Kubernetes), application can be with
Corresponding multiple containers, provide service by cell therefor when user is using respective application for user.
When user uses respective application, which container to provide service for user by is allocated by load balancer
's.The binding relationship of the load balancer Yu each container can be safeguarded on load balancer.Because container is not constant always
, it will increase new container sometimes, delete faulty container because of existing reservoir failure sometimes.So load balancer will timing
The case where monitoring container, binds new volume increasing device or the deleted container of unbundlings.
Be currently by being periodically acquired to the capsule address information in Kubernetes, then by the address of acquisition with
Address on load balancer is matched, and has address not in load balancing if discovery is certain, it is determined that the address is newly-increased
The address of container then binds new volume increasing device with load balancer, conversely, if having extra ground out on load balancer
Location, it is determined that the out extra corresponding container in address has been deleted, then is unbinded deleted container with load balancer.
The maintenance mode of current this binding relationship, needs periodically to adopt address a large amount of in Kubernetes and load balancer
Collection, the mode of this seismic acquisition can occupy more Internet resources, cause the significant wastage of system resource.
Summary of the invention
In order to solve the problems, such as that system resources consumption is big when safeguarding binding relationship in the prior art, the embodiment of the present application is mentioned
For a kind of method of binding relationship management, the consumption of system resource can be reduced when safeguarding binding relationship.The embodiment of the present application
Additionally provide corresponding equipment and computer readable storage medium.
On the one hand the embodiment of the present application provides a kind of method of binding relationship management, comprising:
The update event of pea pods POD object in target collection is monitored, each POD object in the target collection includes
Correspond to the description information of container in container arranging system, the container arranging system includes multiple containers, in the multiple container
At least one there is with load balancer binding relationship；
If the POD object listened in the target collection is updated, it is determined that the POD object of update is newly-increased
POD object or POD object to be deleted；
If it is determined that the POD object of the update is the newly-increased POD object, then establish corresponding to the newly-increased POD object
Container and the load balancer binding relationship；
If it is determined that the POD object of the update is the POD object to be deleted, then the POD object institute to be deleted is released
The binding relationship of corresponding container and the load balancer.
On the other hand the embodiment of the present application provides a kind of equipment of binding relationship management, comprising:
Oracle listener unit, for monitoring the update event of pea pods POD object in target collection, in the target collection
Each POD object include correspond to the description information of container in container arranging system, the container arranging system includes multiple appearances
Device, at least one of the multiple container have binding relationship with load balancer；
It determines program unit, occurs if listening to the POD object in the target collection for the oracle listener unit
It updates, it is determined that the POD object of update is newly-increased POD object or POD object to be deleted；
Program unit is established, if determining that the POD object of the update is the newly-increased POD for the determining program unit
Object then establishes the binding relationship of container and the load balancer corresponding to the newly-increased POD object；
Program unit is unbinded, if determining that the POD object of the update is described to be deleted for the determining program unit
POD object then releases the binding relationship of container and the load balancer corresponding to the POD object to be deleted.
The another aspect of the embodiment of the present application provides a kind of computer readable storage medium, the computer-readable storage medium
Instruction is stored in matter, when run on a computer, so that computer executes the side of binding relationship management described above
Method.
The another aspect of the embodiment of the present application provides a kind of computer program product comprising instruction, when its on computers
When operation, so that the method that computer executes binding relationship management described in above-mentioned various aspects.
Container and load balancing are safeguarded by monitoring the update event of POD object in target collection in the embodiment of the present application
Binding relationship between device, it is possible to reduce the consumption to system resource.
Detailed description of the invention
Fig. 1 is an embodiment schematic diagram of container arranging system in the embodiment of the present application；
Fig. 2 is another embodiment schematic diagram of container arranging system in the embodiment of the present application；
Fig. 3 is an embodiment schematic diagram of cloud system in the embodiment of the present application；
Fig. 4 is the embodiment schematic diagram that terminal is interacted with cloud system in the embodiment of the present application；
Fig. 5 is an embodiment schematic diagram of the method for binding relationship management in the embodiment of the present application；
Fig. 6 is the web interface schematic diagram bound or unbinded in the embodiment of the present application；
Fig. 7 is an embodiment schematic diagram of the process of binding relationship management in the embodiment of the present application；
Fig. 8 is another embodiment schematic diagram of the process of binding relationship management in the embodiment of the present application；
Fig. 9 is an embodiment schematic diagram of update event process flow in the embodiment of the present application；
Figure 10 be in the embodiment of the present application task manager to an embodiment schematic diagram of the process flow of binding task；
Figure 11 be in the embodiment of the present application task manager to unbundlings task process flow an embodiment schematic diagram；
Figure 12 is an embodiment schematic diagram of the equipment of binding relationship management in the embodiment of the present application；
Figure 13 is another embodiment schematic diagram of the equipment of binding relationship management in the embodiment of the present application.
Specific embodiment
With reference to the accompanying drawing, embodiments herein is described, it is clear that described embodiment is only the application
The embodiment of a part, instead of all the embodiments.Those of ordinary skill in the art are it is found that with the development of technology and new field
The appearance of scape, technical solution provided by the embodiments of the present application are equally applicable for similar technical problem.
The embodiment of the present application provides a kind of method of binding relationship management, and system money can be reduced when safeguarding binding relationship
The consumption in source.The embodiment of the present application also provides corresponding equipment and computer readable storage mediums.It carries out individually below detailed
Explanation.
Container arranging system can be Kubernetes, and Kubernetes is by the container of the open source of the leading exploitation of Google
Arranging system can be scheduled container, stretches, manages and monitor.
Container: container is a kind of method for realizing operating system virtualization, and process can be made to operate in one and be isolated
In environment.
Kubernetes describes container using pea pods (peasecod, POD) object, and pea pods can also be translated directly
For pod, POD and pod in the embodiment of the present application are identical.It may include the Internet protocol of container in POD object
(Internet Protocol, IP), the IP of place physical machine, the process of operation and current state etc..In Kubernetes
In system, each container can have a corresponding POD object.
Service object is the set of POD object in the embodiment of the present application, and Service object is Kubernetes system
It is used to describe the object of one group of POD set in system, Service object can be according to certain screening rule by multiple POD objects
It is summarized as a set, the POD object for meeting screening rule will be automatically added to gather, when the POD in set is abnormal
When, Service object, which also can automatically remove out the POD, to be gathered.
Event: in Kubernetes, Kubernetes can current state in a manner of event in external output system.
Event in Kubernetes is divided into increase, deletion and updates three kinds of events, only exists wherein increasing with deletion event
It can just be triggered when Kubernetes internal system additions and deletions object, and only triggering is primary, update event is removed when object updates
Triggering is outer, also can periodically trigger.
Fig. 1 is an embodiment schematic diagram of container arranging system in the embodiment of the present application.
As shown in Figure 1, may include multiple containers in the container arranging system, such as: container 1, container M, container N etc.,
Wherein, M and N is the integer greater than 1, and M is less than N.Each container has one corresponding POD pairs in the container arranging system
As, wherein the POD object of container 1 is POD object 1, and the POD object of container M is POD object M, and the POD object of container N is POD
Object N.
Multiple containers in container arranging system can be located in a physical machine, can also be located in multiple physical machines,
As shown in another embodiment schematic diagram of Fig. 2 container arranging system, multiple containers are located in multiple physical machines, wherein container
1 is located in physical machine 1, and container M and container N are located on physical machine X, and X is the integer greater than 1.
Fig. 3 is an embodiment schematic diagram of cloud system in the embodiment of the present application.
As shown in figure 3, including container arranging system, the equipment 10 of binding relationship management and load balancer in cloud system
20, the equipment 10 of binding relationship management is responsible for the binding relationship of container and load balancer 20 in maintenance container arranging system.
The equipment 10 of binding relationship management can bind container and load balancer, can also unbind appearance according to the operating condition of container
Device and load balancer 20.Load balancer 20 is responsible for equally loaded, as terminal is interacted with cloud system in Fig. 4 the embodiment of the present application
An embodiment schematic diagram shown in, using in application, for example in terminal 30: wechat application, the application data of terminal 30
The load of corresponding container can be applied according to wechat to load balancer 20, load balancer 20 is sent to by network 40
Which container situation, determination will be assigned on using data, be that corresponding terminal 30 provides corresponding service by corresponding container.
The equipment 20 of binding relationship management shown in above-mentioned Fig. 3 and Fig. 4 can wrap the method for binding relationship management
It includes:
101, the update event of pea pods POD object in target collection, each POD object in the target collection are monitored
Description information comprising corresponding to container in container arranging system, the container arranging system include multiple containers, the multiple appearance
At least one of device has binding relationship with load balancer.
The relationship of container arranging system and container, the relationship of container and POD object, the relationship of target collection and POD object,
And the relationship of load balancer and container can be understood refering to the description in previous embodiment.
Update event is to have increased POD object newly, or have POD object to be deleted.
If the POD object 102, listened in the target collection is updated, it is determined that the POD object of update is new
Increase POD object or POD object to be deleted.
103, if it is determined that the POD object of the update is the newly-increased POD object, then the newly-increased POD object institute is established
The binding relationship of corresponding container and the load balancer.
104, if it is determined that the POD object of the update is the POD object to be deleted, then described POD pairs to be deleted is released
As the binding relationship of corresponding container and the load balancer.
Container and load balancing are safeguarded by monitoring the update event of POD object in target collection in the embodiment of the present application
Binding relationship between device, it is possible to reduce the consumption to system resource.
Wherein, optionally, described true in another embodiment of the method for binding relationship management provided by the embodiments of the present application
Surely the POD object updated is newly-increased POD object or POD object to be deleted, may include:
Inquiring in database whether there is request relevant to the POD object of the update；
Request relevant to the POD object of the update if it exists, it is determined that the POD object of update is newly-increased POD object
Or POD object to be deleted.
In the embodiment of the present application, backstage manager can be sent to the equipment of binding relationship management for a certain container or
The bind request or unbundlings request, the equipment of binding relationship management of certain containers can store these requests, listen to update thing
After part, the equipment of binding relationship management can determine whether to have in request transmitted by backstage manager the POD object pair with update
The request answered just determines the binding task for executing the POD object updated or unbundlings task, if not right if there is corresponding request
The request answered ignores the update event listened to, then so as to avoid the wasting of resources.
Wherein, optionally, described true in another embodiment of the method for binding relationship management provided by the embodiments of the present application
Surely the POD object updated is newly-increased POD object or POD object to be deleted, may include:
It whether determines in the POD object of the update comprising deleting mark information；
If comprising deleting mark information, it is determined that the POD object of the update is the POD object to be deleted；
Mark information is deleted if not including, and the POD object of the update includes Internet protocol IP information, it is determined that institute
The POD object for stating update is the newly-increased POD object.
In the embodiment of the present application, after the POD object of update determines, it can detecte in the POD object of the update and whether wrap
Containing mark information is deleted, if comprising deleting mark information, then it represents that the POD object of the update is to be deleted, to execute unbundlings and appoint
Business.Mark information is deleted if not including, then it represents that the POD object of the update is not deleted, if including in the POD object of the update
IP information, then it represents that the POD object of the update is newly-increased POD object, Yao Zhihang binding task.
Optionally, described to establish institute in another embodiment of the method for binding relationship management provided by the embodiments of the present application
The binding relationship for stating container and the load balancer corresponding to newly-increased POD object may include:
Binding task is created, and is the binding task allocation identification information, the identification information includes to be bound bears
The information of container corresponding to the information of load balanced device and the newly-increased POD object；
According to the identification information, appearance corresponding to the load balancer and the newly-increased POD object to be bound is established
The binding relationship of device.
In the embodiment of the present application, when determining POD object is newly-increased POD object, it is right to need to bind the newly-increased POD object institute
The container and load balancer answered so needing to create binding task, and are the binding task allocation identification information, Ke Yiwei
Each binding task generates unique task identification (ID), and task ID may include load balancer ID, Container Name, container IP
And container port.According to the information in task ID, by load balancer indicated by load balancer ID and cell therefor with
And container port is bound.
Optionally, in another embodiment of the method for binding relationship management provided by the embodiments of the present application, the method is also
Include:
Corresponding unbundlings task is created for the binding task；
If also confiscate binding task identical with the identification information of the binding task at the end of heart beat cycle,
According to the unbundlings task, container corresponding to the load balancer and the newly-increased POD object is unbinded；
If receive binding task identical with the identification information of the binding task in heart beat cycle, institute is updated
State the execution time of unbundlings task.
In the embodiment of the present application, in order to avoid the container bound also is constantly in binding state after failure, institute
A unbundlings task is created again so that the binding task of the container can be directed to, and the container is periodically detected after people, the period
It is properly termed as heart beat cycle, if receiving binding task identical with the ID of the binding task in a heart beat cycle, is said
Bright container health, it is also necessary to be bound, then refresh the execution period of the unbundlings task.If being not received by identical
The binding task of ID then illustrates that exception occurs in the container, then executes the unbundlings task and unbind the container.
Optionally, described according to institute in another embodiment of the method for binding relationship management provided by the embodiments of the present application
Unbundlings task is stated, container corresponding to the load balancer and the newly-increased POD object is unbinded, may include:
Determine that the corresponding unbundlings container of the unbundlings task whether there is；
If container is not present, unbundlings task is executed, is unbinded corresponding to the load balancer and the newly-increased POD object
Container；
If container exists, and receive corresponding unbundlings task, then execute unbundlings task, unbind the load balancer and
Container corresponding to the newly-increased POD object.
In the embodiment of the present application, is tied up in order to avoid misreading, when executing unbundlings task, need to carry out double check, it can be with
First the detection container to be unbinded whether there is, if container is not present, can unbind the container.If container exists,
Determine whether that backstage manager will unbind the task, if then unbinding the container, if backstage manager will not unbind this
Unbundlings task is then not carried out in container.
Optionally, in another embodiment of the method for binding relationship management provided by the embodiments of the present application, the determination is more
New POD object is newly-increased POD object or POD object to be deleted, can also include:
Check whether automatic binding/unbundlings switch of container corresponding to the POD object of the update closes；
If the automatic binding/unbundlings switch is in the open state, it is determined that the POD object of update is newly-increased POD object
Or POD object to be deleted.
It, can also be according to back-stage management other than executing binding task or unbundlings task automatically in the embodiment of the present application
The instruction of member executes binding or unbundlings task, and backstage manager can close automatic binding/unbundlings switch on web page, this
Even if when detect that the container needs to bind or unbind, corresponding binding or unbundlings operation will not be executed.Only tying up automatically
When fixed/unbundlings switch is in the open state, can just execute container corresponding to newly-increased POD object bindings or POD to be deleted
The unbundlings of container corresponding to object operate.Web page can be understood refering to Fig. 6.As shown in fig. 6, load balancer uses
ID indicates that each ID corresponds to only one load balancer；Bound container port, as shown in 6 figures, load balancer meeting
Flow is imported into 80 ports of container；Automatic binding switch, when switch is in an open state, system can be automatically by the appearance of health
Device is tied to load balancer, also can unbind unsound container from load balancer；When switch is in off state, institute
There are binding and unbundlings operation all voluntarily to be completed by user；Operation button.User can click button and be tied up after selected container
It is fixed to be operated with unbundlings.
Fig. 7 is an embodiment schematic diagram of the process of binding relationship management in the embodiment of the present application.
As shown in fig. 7, binding relationship management includes event sniffer, request manager, task manager, task performer
And log manager.
Event sniffer is used to monitor the update event of POD object.
Request manager is used for the request that preservation and management user submits, and all requests can all be output to database progress
It saves.
For task manager for managing binding task and unbundlings task, the task in task manager can be with certain frequency quilt
It is issued to task performer, can guarantee that each task is only handed down to a task performer in mission dispatching.
Task performer is for binding and unbinding operation.
For saving the log that task performer operates generation every time, certain contents therein can be fed back log manager
To user.
In Fig. 7, container arranging system exports the update event of POD object, which acquires and handle through event sniffer
After export to task manager.
Backstage manager initiates to request by the operation in Web page to the equipment of binding relationship management, and request is asked
It asks manager to receive, and then exports to task manager and database.
Task manager is managed and issues to receiving for task, each task is assigned to a task execution
Device executes.
Task performer can export the implementing result of task to log manager after the completion of execution, certain when meeting
When condition, task performer can also be fed back to task manager, carry out the operation of some task deletions；When user's request is appointed
When the implementation progress of business, the execution record of task can feed back to user.
The method of binding relationship management can also be understood refering to the process of Fig. 8 in the embodiment of the present application.
Fig. 8 is another embodiment schematic diagram of the process of binding relationship management in the embodiment of the present application.
As shown in figure 8, another embodiment of the method for binding relationship management includes: in the embodiment of the present application
201, backstage manager by the Web page of back-stage management equipment towards the equipment of binding relationship management send binding/
Unbundlings request, the binding/unbundlings request are received by request manager.
202, event sniffer, which listens in container arranging system, has occurred POD object update event.
203, event sniffer sends inquiry request to request manager.
The inquiry request is used to inquire whether backstage manager to be transmitted across the binding for the POD object or unbind request.
204, request manager returns to query result to event sniffer.
Query result is that backstage manager is transmitted across the binding for the POD object or unbinds request.
205, event sniffer creates binding/unbundlings task and is sent to task manager.
206, task manager issues binding/unbundlings task to task performer.
207, after task performer has executed binding/unbundlings task, by log manager logger task state.
The task status can either bind progress or unbundlings progress to have bound or having unbinded.
208, backstage manager passes through the web page request implementing result of back-stage management equipment.
209, request manager is to log manager result of query execution.
210, log manager returns to task daily record to request manager.
211, request manager returns to implementing result to the web page of backstage management equipment.
Be above to binding relationship management entirety introduce, below with reference to Fig. 9 introduce in the embodiment of the present application to update
The snoop procedure of event.
The processing of POD object update event is completed by event sniffer, update event process flow is as shown in Figure 9:
301, event receives, and determines the POD object updated.
302, inquiry user request.
User in the embodiment of the present application refers to backstage manager.
303, judge whether user's request is related to the POD object.
If 304, not being related to the POD object in user's request, terminate process.
If whether 305, POD object involved in user's request detects to be provided in POD object and deletes label.
If 306, being provided with and deleting label, unbundlings task is created.
Label is deleted if being provided with, illustrates that the POD object can be deleted after a certain time, therefore, event sniffer meeting
A unbundlings task is created for this POD, unbundlings task can be output at task manager.
If 307, being not provided with deletion label, event sniffer can check whether the IP field in POD object is empty.
If 308, IP field is sky, illustrate to have bound, does not need to terminate process in creation binding task.
If 309, IP field is not empty, for one binding task of the POD Object Creation and export to task manager.
Task manager, which receives binding task or the process of unbundlings task, to be understood with refering to fig. 10 and Figure 11.
As shown in Figure 10, which includes: to the process flow of binding task
401, binding task is received.
After task manager receives the binding task of event sniffer, unique task can be generated for each binding task
ID, task ID are made of following elements: load balancer ID, Container Name, container IP, container port.
For each binding task, task manager all can create a corresponding unbundlings task for it, unbind task
Timing executes, and when task manager receives the identical binding task of a task ID, can all refresh corresponding unbundlings task
Timing, when being more than that timing receives corresponding binding task not yet, task manager will will be under unbundlings task
Issue task performer execution.
402, query load balanced device.
403, determine whether container is bundled on load balancer.
404, if so, no longer needing to bind, terminate process.
405, if it is not, then needing for the corresponding container of the binding task to be bundled on load balancer.
406, implementing result is recorded.
As shown in figure 11, which includes: to the process flow of unbundlings task
501, unbundlings task is received.
502, container arranging system is inquired.
503, container whether there is also.
If 504, container is not present, the container is unbinded.
505, after unbinding container, implementing result is recorded.
506, inquiry user request.
User in the embodiment of the present application refers to backstage manager.
507, unbundlings request whether was received.
If receiving unbundlings request, 504 are executed, the container is unbinded.
If 508, not receiving unbundlings request, terminate process.
By the description in above embodiments it is found that scheme provided by the embodiments of the present application disobeys the binding of container with unbundlings
Any specific event of Lai Yu, and being all saved in the database of executing of request due to user and system, that is, use
Existing individual case is lost or system reboot, and whole system can still operate normally.Meanwhile even if encountering the pole that database empties
End is abnormal, since system will not read any unbundlings task from database, so will not be wrong because of the exception of database
Container accidentally is unbinded, reliability is improved.
The embodiment of the present application does not need the container state periodically inquired in an active manner in Kubernetes system, and absolutely
Most of update events only take up less Internet resources from system cache, to save Internet resources.
The foregoing describe the method for the binding relationship management in the embodiment of the present application and locating systems, with reference to the accompanying drawing
Introduce the device of the binding relationship management in the embodiment of the present application.
As shown in figure 12, the equipment 60 of binding relationship management provided by the embodiments of the present application includes:
Oracle listener unit 601, for monitoring the update event of pea pods POD object in target collection, the object set
Each POD object in conjunction includes the description information that container is corresponded in container arranging system, and the container arranging system includes more
A container, at least one of the multiple container have binding relationship with load balancer；
Program unit 602 is determined, if listening to POD pairs in the target collection for the oracle listener unit 601
As being updated, it is determined that the POD object of update is newly-increased POD object or POD object to be deleted；
Program unit 603 is established, if determining that the POD object of the update is described for the determining program unit 602
Newly-increased POD object, then establish the binding relationship of container and the load balancer corresponding to the newly-increased POD object；
Program unit 604 is unbinded, if determining that the POD object of the update is described for the determining program unit 602
POD object to be deleted then releases the binding relationship of container and the load balancer corresponding to the POD object to be deleted.
Container and load balancing are safeguarded by monitoring the update event of POD object in target collection in the embodiment of the present application
Binding relationship between device, it is possible to reduce the consumption to system resource.
Optionally, in another embodiment of the equipment 60 of binding relationship management provided by the embodiments of the present application,
The determining program unit 602 is used for:
Inquiring in database whether there is request relevant to the POD object of the update；
Request relevant to the POD object of the update if it exists, it is determined that the POD object of update is newly-increased POD object
Or POD object to be deleted.
In the embodiment of the present application, backstage manager can be sent to the equipment of binding relationship management for a certain container or
The bind request or unbundlings request, the equipment of binding relationship management of certain containers can store these requests, listen to update thing
After part, the equipment of binding relationship management can determine whether to have in request transmitted by backstage manager the POD object pair with update
The request answered just determines the binding task for executing the POD object updated or unbundlings task, if not right if there is corresponding request
The request answered ignores the update event listened to, then so as to avoid the wasting of resources.
Optionally, in another embodiment of the equipment 60 of binding relationship management provided by the embodiments of the present application,
The determining program unit 602 is used for:
It whether determines in the POD object of the update comprising deleting mark information；
If comprising deleting mark information, it is determined that the POD object of the update is the POD object to be deleted；
Mark information is deleted if not including, and the POD object of the update includes Internet protocol IP information, it is determined that institute
The POD object for stating update is the newly-increased POD object.
In the embodiment of the present application, after the POD object of update determines, it can detecte in the POD object of the update and whether wrap
Containing mark information is deleted, if comprising deleting mark information, then it represents that the POD object of the update is to be deleted, to execute unbundlings and appoint
Business.Mark information is deleted if not including, then it represents that the POD object of the update is not deleted, if including in the POD object of the update
IP information, then it represents that the POD object of the update is newly-increased POD object, Yao Zhihang binding task.
Optionally, in another embodiment of the equipment 60 of binding relationship management provided by the embodiments of the present application,
The program unit 603 of establishing is used for:
Binding task is created, and is the binding task allocation identification information, the identification information includes to be bound bears
The information of container corresponding to the information of load balanced device and the newly-increased POD object；
According to the identification information, appearance corresponding to the load balancer and the newly-increased POD object to be bound is established
The binding relationship of device.
In the embodiment of the present application, when determining POD object is newly-increased POD object, it is right to need to bind the newly-increased POD object institute
The container and load balancer answered so needing to create binding task, and are the binding task allocation identification information, Ke Yiwei
Each binding task generates unique task identification (ID), and task ID may include load balancer ID, Container Name, container IP
And container port.According to the information in task ID, by load balancer indicated by load balancer ID and cell therefor with
And container port is bound.
Optionally, in another embodiment of the equipment 60 of binding relationship management provided by the embodiments of the present application, the equipment
It further include updating program unit 605,
It is described to establish program unit 603, it is also used to create corresponding unbundlings task for the binding task；
The unbundlings program unit 604, if being also used to also confiscate at the end of heart beat cycle and the binding task
When the identical binding task of identification information, then according to the unbundlings task, the load balancer and newly-increased POD pairs described is unbinded
As corresponding container；
The update program unit 605, if for receiving the identification information with the binding task in heart beat cycle
When identical binding task, then the execution time of the unbundlings task is updated.
In the embodiment of the present application, in order to avoid the container bound also is constantly in binding state after failure, institute
A unbundlings task is created again so that the binding task of the container can be directed to, and the container is periodically detected after people, the period
It is properly termed as heart beat cycle, if receiving binding task identical with the ID of the binding task in a heart beat cycle, is said
Bright container health, it is also necessary to be bound, then refresh the execution period of the unbundlings task.If being not received by identical
The binding task of ID then illustrates that exception occurs in the container, then executes the unbundlings task and unbind the container.
Optionally, in another embodiment of the equipment 60 of binding relationship management provided by the embodiments of the present application, the unbundlings
Program unit 604 is used for:
Determine that the corresponding unbundlings container of the unbundlings task whether there is；
If container is not present, unbundlings task is executed, is unbinded corresponding to the load balancer and the newly-increased POD object
Container；
If container exists, and receive corresponding unbundlings task, then execute unbundlings task, unbind the load balancer and
Container corresponding to the newly-increased POD object.
In the embodiment of the present application, is tied up in order to avoid misreading, when executing unbundlings task, need to carry out double check, it can be with
First the detection container to be unbinded whether there is, if container is not present, can unbind the container.If container exists,
Determine whether that backstage manager will unbind the task, if then unbinding the container, if backstage manager will not unbind this
Unbundlings task is then not carried out in container.
Optionally, in another embodiment of the equipment 60 of binding relationship management provided by the embodiments of the present application,
The determining program unit 602 is used for:
Check whether automatic binding/unbundlings switch of container corresponding to the POD object of the update closes；
If the automatic binding/unbundlings switch is in the open state, it is determined that the POD object of update is newly-increased POD object
Or POD object to be deleted.
It, can also be according to back-stage management other than executing binding task or unbundlings task automatically in the embodiment of the present application
The instruction of member executes binding or unbundlings task, and backstage manager can close automatic binding/unbundlings switch on web page, this
Even if when detect that the container needs to bind or unbind, corresponding binding or unbundlings operation will not be executed.Only tying up automatically
When fixed/unbundlings switch is in the open state, can just execute container corresponding to newly-increased POD object bindings or POD to be deleted
The unbundlings of container corresponding to object operate.
Figure 13 is the structural schematic diagram of the equipment 60 of binding relationship management provided by the embodiments of the present application.The binding relationship
The equipment 60 of management includes processor 610, memory 640 and input and output (I/O) interface 630, and memory 640 may include only
Memory and random access memory are read, and provides operational order and data to processor 610.A part of memory 640 is also
It may include nonvolatile RAM (NVRAM).
In some embodiments, memory 640 stores following element, executable modules or data structures, or
Their subset of person or their superset:
In the embodiment of the present application, during binding relationship manages, referred to by the operation for calling memory 640 to store
(operational order is storable in operating system) is enabled,
The update event of pea pods POD object in target collection is monitored, each POD object in the target collection includes
Correspond to the description information of container in container arranging system, the container arranging system includes multiple containers, in the multiple container
At least one there is with load balancer binding relationship；
If the POD object listened in the target collection is updated, it is determined that the POD object of update is newly-increased
POD object or POD object to be deleted；
If it is determined that the POD object of the update is the newly-increased POD object, then establish corresponding to the newly-increased POD object
Container and the load balancer binding relationship；
If it is determined that the POD object of the update is the POD object to be deleted, then the POD object institute to be deleted is released
The binding relationship of corresponding container and the load balancer.
Container and load balancing are safeguarded by monitoring the update event of POD object in target collection in the embodiment of the present application
Binding relationship between device, it is possible to reduce the consumption to system resource.
Processor 610 controls the operation of the equipment 60 of binding relationship management, and processor 610 can also be known as CPU
(Central Processing Unit, central processing unit).Memory 640 may include read-only memory and arbitrary access
Memory, and instruction and data is provided to processor 610.The a part of of memory 640 can also deposit including non-volatile random
Access to memory (NVRAM).The various components of the equipment 60 of binding relationship management are coupled by bus system 620 in specific application
Together, wherein bus system 620 can also include power bus, control bus and state letter in addition to including data/address bus
Number bus etc..But for the sake of clear explanation, various buses are all designated as bus system 620 in figure.
The method that above-mentioned the embodiment of the present application discloses can be applied in processor 610, or be realized by processor 610.
Processor 610 may be a kind of IC chip, the processing capacity with signal.During realization, the above method it is each
Step can be completed by the integrated logic circuit of the hardware in processor 610 or the instruction of software form.Above-mentioned processing
Device 610 can be general processor, digital signal processor (DSP), specific integrated circuit (ASIC), ready-made programmable gate array
(FPGA) either other programmable logic device, discrete gate or transistor logic, discrete hardware components.May be implemented or
Person executes disclosed each method, step and logic diagram in the embodiment of the present application.General processor can be microprocessor or
Person's processor is also possible to any conventional processor etc..The step of method in conjunction with disclosed in the embodiment of the present application, can be straight
Connect and be presented as that hardware decoding processor executes completion, or in decoding processor hardware and software module combination executed
At.Software module can be located at random access memory, and flash memory, read-only memory, programmable read only memory or electrically-erasable can
In the storage medium of this fields such as programmable memory, register maturation.The storage medium is located at memory 640, and processor 610 is read
Information in access to memory 640, in conjunction with the step of its hardware completion above method.
Optionally, processor 610 is used for:
Inquiring in database whether there is request relevant to the POD object of the update；
Request relevant to the POD object of the update if it exists, it is determined that the POD object of update is newly-increased POD object
Or POD object to be deleted.
Optionally, processor 610 is used for:
It whether determines in the POD object of the update comprising deleting mark information；
If comprising deleting mark information, it is determined that the POD object of the update is the POD object to be deleted；
Mark information is deleted if not including, and the POD object of the update includes Internet protocol IP information, it is determined that institute
The POD object for stating update is the newly-increased POD object.
Optionally, processor 610 is also used to:
According to each user in the general vector of all channels of the sets of channels and each user in the channel
The exclusive vector for concentrating each channel determines each user to the interest vector of each channel.
Optionally, processor 610 is also used to:
Binding task is created, and is the binding task allocation identification information, the identification information includes to be bound bears
The information of container corresponding to the information of load balanced device and the newly-increased POD object；
According to the identification information, appearance corresponding to the load balancer and the newly-increased POD object to be bound is established
The binding relationship of device.
Optionally, processor 610 is also used to:
Corresponding unbundlings task is created for the binding task；
If also confiscate binding task identical with the identification information of the binding task at the end of heart beat cycle,
According to the unbundlings task, container corresponding to the load balancer and the newly-increased POD object is unbinded；
If receive binding task identical with the identification information of the binding task in heart beat cycle, institute is updated
State the execution time of unbundlings task.
Optionally, processor 610 is used for:
Determine that the corresponding unbundlings container of the unbundlings task whether there is；
If container is not present, unbundlings task is executed, is unbinded corresponding to the load balancer and the newly-increased POD object
Container；
If container exists, and receive corresponding unbundlings task, then execute unbundlings task, unbind the load balancer and
Container corresponding to the newly-increased POD object.
Optionally, processor 610 is also used to:
Check whether automatic binding/unbundlings switch of container corresponding to the POD object of the update closes；
If the automatic binding/unbundlings switch is in the open state, it is determined that the POD object of update is newly-increased POD object
Or POD object to be deleted.
On to the description of the equipment 60 of binding relationship management can the description refering to fig. 1 to the part Figure 11 understand, this
It is no longer repeated at place.
In the above-described embodiments, can come wholly or partly by software, hardware, firmware or any combination thereof real
It is existing.When implemented in software, it can entirely or partly realize in the form of a computer program product.
The computer program product includes one or more computer instructions.Load and execute on computers the meter
When calculation machine program instruction, entirely or partly generate according to process or function described in the embodiment of the present application.The computer can
To be general purpose computer, special purpose computer, computer network or other programmable devices.The computer instruction can be deposited
Storage in a computer-readable storage medium, or from a computer readable storage medium to another computer readable storage medium
Transmission, for example, the computer instruction can pass through wired (example from a web-site, computer, server or data center
Such as coaxial cable, optical fiber, Digital Subscriber Line (DSL)) or wireless (such as infrared, wireless, microwave) mode to another website
Website, computer, server or data center are transmitted.The computer readable storage medium can be computer and can deposit
Any usable medium of storage either includes that the data storages such as one or more usable mediums integrated server, data center are set
It is standby.The usable medium can be magnetic medium, (for example, floppy disk, hard disk, tape), optical medium (for example, DVD) or partly lead
Body medium (such as solid state hard disk Solid StateDisk (SSD)) etc..
Those of ordinary skill in the art will appreciate that all or part of the steps in the various methods of above-described embodiment is can
It is completed with instructing relevant hardware by program, which can be stored in a computer readable storage medium, storage
Medium may include: ROM, RAM, disk or CD etc..
Above to the method, equipment of binding relationship management provided by the embodiment of the present application, system and computer-readable
Storage medium is described in detail, and specific case used herein explains the principle and embodiment of the application
It states, the description of the example is only used to help understand the method for the present application and its core ideas；Meanwhile for this field
Those skilled in the art, according to the thought of the application, there will be changes in the specific implementation manner and application range, to sum up institute
It states, the contents of this specification should not be construed as limiting the present application.
Claims (15)
1. a kind of method of binding relationship management characterized by comprising
The update event of pea pods POD object in target collection is monitored, each POD object in the target collection includes container
Correspond to the description information of container in arranging system, the container arranging system includes multiple containers, in the multiple container extremely
Few one has binding relationship with load balancer；
If the POD object listened in the target collection is updated, it is determined that the POD object of update is POD pairs newly-increased
As or POD object to be deleted；
If it is determined that the POD object of the update is the newly-increased POD object, then appearance corresponding to the newly-increased POD object is established
The binding relationship of device and the load balancer；
If it is determined that the POD object of the update is the POD object to be deleted, then release corresponding to the POD object to be deleted
Container and the load balancer binding relationship.
2. the method according to claim 1, wherein the determining POD object updated be newly-increased POD object or
POD object to be deleted, comprising:
Inquiring in database whether there is request relevant to the POD object of the update；
Request relevant to the POD object of the update if it exists, it is determined that the POD object of update be newly-increased POD object or to
Delete POD object.
3. the method according to claim 1, wherein the determining POD object updated be newly-increased POD object or
POD object to be deleted, comprising:
It whether determines in the POD object of the update comprising deleting mark information；
If comprising deleting mark information, it is determined that the POD object of the update is the POD object to be deleted；
If do not include delete mark information, and the POD object of the update include Internet protocol IP information, it is determined that it is described more
New POD object is the newly-increased POD object.
4. method according to claim 1 to 3, which is characterized in that described to establish corresponding to the newly-increased POD object
Container and the load balancer binding relationship, comprising:
Binding task is created, and is the binding task allocation identification information, the identification information includes that load to be bound is equal
The information of container corresponding to the information of weighing apparatus and the newly-increased POD object；
According to the identification information, container corresponding to the load balancer and the newly-increased POD object to be bound is established
Binding relationship.
5. according to the method described in claim 4, it is characterized in that, the method also includes:
Corresponding unbundlings task is created for the binding task；
If also confiscate binding task identical with the identification information of the binding task at the end of heart beat cycle, basis
The unbundlings task unbinds container corresponding to the load balancer and the newly-increased POD object；
If receive binding task identical with the identification information of the binding task in heart beat cycle, the solution is updated
Tie up the execution time of task.
6. according to the method described in claim 5, the unbundlings load is equal it is characterized in that, described according to the unbundlings task
Container corresponding to weighing apparatus and the newly-increased POD object, comprising:
Determine that the corresponding unbundlings container of the unbundlings task whether there is；
If container is not present, unbundlings task is executed, unbinds the load balancer and the corresponding appearance of the newly-increased POD object
Device；
If container exists, and corresponding unbundlings task is received, then execute unbundlings task, unbinds the load balancer and described
Container corresponding to newly-increased POD object.
7. method according to claim 1 to 3, which is characterized in that the determining POD object updated is newly-increased POD
Object or POD object to be deleted, further includes:
Check whether automatic binding/unbundlings switch of container corresponding to the POD object of the update closes；
If the automatic binding/unbundlings switch is in the open state, it is determined that the POD object of update be newly-increased POD object or to
Delete POD object.
8. a kind of equipment of binding relationship management characterized by comprising
Oracle listener unit, it is every in the target collection for monitoring the update event of pea pods POD object in target collection
A POD object includes the description information that container is corresponded in container arranging system, and the container arranging system includes multiple containers, institute
Stating at least one of multiple containers and load balancer has binding relationship；
Program unit is determined, if the POD object for the oracle listener unit to listen in the target collection has occurred more
Newly, it is determined that the POD object of update is newly-increased POD object or POD object to be deleted；
Program unit is established, if determining that the POD object of the update is described newly-increased POD pairs for the determining program unit
As then establishing the binding relationship of container and the load balancer corresponding to the newly-increased POD object；
Program unit is unbinded, if determining that the POD object of the update is described POD pairs to be deleted for the determining program unit
As then releasing the binding relationship of container and the load balancer corresponding to the POD object to be deleted.
9. equipment according to claim 8, which is characterized in that
The determining program unit is used for:
Inquiring in database whether there is request relevant to the POD object of the update；
Request relevant to the POD object of the update if it exists, it is determined that the POD object of update be newly-increased POD object or to
Delete POD object.
10. equipment according to claim 8, which is characterized in that
The determining program unit is used for:
It whether determines in the POD object of the update comprising deleting mark information；
If comprising deleting mark information, it is determined that the POD object of the update is the POD object to be deleted；
If do not include delete mark information, and the POD object of the update include Internet protocol IP information, it is determined that it is described more
New POD object is the newly-increased POD object.
11. according to any equipment of claim 8-10, which is characterized in that
The program unit of establishing is used for:
Binding task is created, and is the binding task allocation identification information, the identification information includes that load to be bound is equal
The information of container corresponding to the information of weighing apparatus and the newly-increased POD object；
According to the identification information, container corresponding to the load balancer and the newly-increased POD object to be bound is established
Binding relationship.
12. equipment according to claim 11, which is characterized in that the equipment further includes updating program unit,
It is described to establish program unit, it is also used to create corresponding unbundlings task for the binding task；
The unbundlings program unit, if being also used to also confiscate the identification information with the binding task at the end of heart beat cycle
When identical binding task, then according to the unbundlings task, unbind corresponding to the load balancer and the newly-increased POD object
Container；
The update program unit, if for receiving tie up identical with the identification information of the binding task in heart beat cycle
When determining task, then the execution time of the unbundlings task is updated.
13. equipment according to claim 12, which is characterized in that
The unbundlings program unit is used for:
Determine that the corresponding unbundlings container of the unbundlings task whether there is；
If container is not present, unbundlings task is executed, unbinds the load balancer and the corresponding appearance of the newly-increased POD object
Device；
If container exists, and corresponding unbundlings task is received, then execute unbundlings task, unbinds the load balancer and described
Container corresponding to newly-increased POD object.
14. a kind of equipment of binding relationship management, which is characterized in that the equipment of the binding relationship management includes: input/output
(I/O) interface, processor and memory are stored with program instruction in the memory；
The processor executes method as claimed in claim 1 for executing the program instruction stored in memory.
15. a kind of computer readable storage medium, including instruction, which is characterized in that when described instruction is transported on a computing device
When row, so that the computer equipment executes such as method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810205327.0A CN110213309B (en) | 2018-03-13 | 2018-03-13 | Binding relationship management method, device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810205327.0A CN110213309B (en) | 2018-03-13 | 2018-03-13 | Binding relationship management method, device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110213309A true CN110213309A (en) | 2019-09-06 |
| CN110213309B CN110213309B (en) | 2022-02-01 |
Family
ID=67778778
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810205327.0A Active CN110213309B (en) | 2018-03-13 | 2018-03-13 | Binding relationship management method, device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110213309B (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112631727A (en) * | 2020-12-26 | 2021-04-09 | 中国农业银行股份有限公司 | Method and device for monitoring pod |
| CN113010385A (en) * | 2021-03-18 | 2021-06-22 | 山东英信计算机技术有限公司 | Task state updating method, device, equipment and medium |
| CN114938375A (en) * | 2022-05-16 | 2022-08-23 | 聚好看科技股份有限公司 | Container group updating equipment and container group updating method |
| CN115484231A (en) * | 2022-09-14 | 2022-12-16 | 浙江大华技术股份有限公司 | Pod IP allocation method and related device |
| CN116893834A (en) * | 2023-09-11 | 2023-10-17 | 中移(苏州)软件技术有限公司 | Load updating method, device, system, electronic equipment and readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170163479A1 (en) * | 2015-12-02 | 2017-06-08 | Le Holdings (Beijing) Co., Ltd. | Method, Device and System of Renewing Terminal Configuration In a Memcached System |
| CN107256178A (en) * | 2017-04-27 | 2017-10-17 | 北京数人科技有限公司 | Container management platform |
| CN107666525A (en) * | 2017-09-08 | 2018-02-06 | 北京京东尚科信息技术有限公司 | The method and apparatus of cluster container IP distribution |
| CN107707661A (en) * | 2017-10-16 | 2018-02-16 | 中国银联股份有限公司 | A kind of load balancing method for managing resource and device |
-
2018
- 2018-03-13 CN CN201810205327.0A patent/CN110213309B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170163479A1 (en) * | 2015-12-02 | 2017-06-08 | Le Holdings (Beijing) Co., Ltd. | Method, Device and System of Renewing Terminal Configuration In a Memcached System |
| CN107256178A (en) * | 2017-04-27 | 2017-10-17 | 北京数人科技有限公司 | Container management platform |
| CN107666525A (en) * | 2017-09-08 | 2018-02-06 | 北京京东尚科信息技术有限公司 | The method and apparatus of cluster container IP distribution |
| CN107707661A (en) * | 2017-10-16 | 2018-02-16 | 中国银联股份有限公司 | A kind of load balancing method for managing resource and device |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112631727A (en) * | 2020-12-26 | 2021-04-09 | 中国农业银行股份有限公司 | Method and device for monitoring pod |
| CN112631727B (en) * | 2020-12-26 | 2024-02-23 | 中国农业银行股份有限公司 | Monitoring method and device for pod group pod |
| CN113010385A (en) * | 2021-03-18 | 2021-06-22 | 山东英信计算机技术有限公司 | Task state updating method, device, equipment and medium |
| CN113010385B (en) * | 2021-03-18 | 2022-10-28 | 山东英信计算机技术有限公司 | Task state updating method, device, equipment and medium |
| US11915035B1 (en) | 2021-03-18 | 2024-02-27 | Shandong Yingxin Computer Technologies Co., Ltd. | Task state updating method and apparatus, device, and medium |
| CN114938375A (en) * | 2022-05-16 | 2022-08-23 | 聚好看科技股份有限公司 | Container group updating equipment and container group updating method |
| CN114938375B (en) * | 2022-05-16 | 2023-06-02 | 聚好看科技股份有限公司 | Container group updating equipment and container group updating method |
| CN115484231A (en) * | 2022-09-14 | 2022-12-16 | 浙江大华技术股份有限公司 | Pod IP allocation method and related device |
| CN116893834A (en) * | 2023-09-11 | 2023-10-17 | 中移(苏州)软件技术有限公司 | Load updating method, device, system, electronic equipment and readable storage medium |
| CN116893834B (en) * | 2023-09-11 | 2023-12-12 | 中移(苏州)软件技术有限公司 | Load updating method, device, system, electronic equipment and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110213309B (en) | 2022-02-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110213309A (en) | A kind of method, equipment and the storage medium of binding relationship management | |
| CN110290189B (en) | Container cluster management method, device and system | |
| US10691716B2 (en) | Dynamic partitioning techniques for data streams | |
| US10795905B2 (en) | Data stream ingestion and persistence techniques | |
| CN105245373B (en) | A kind of container cloud platform system is built and operation method | |
| US9794135B2 (en) | Managed service for acquisition, storage and consumption of large-scale data streams | |
| US10635644B2 (en) | Partition-based data stream processing framework | |
| US9639589B1 (en) | Chained replication techniques for large-scale data streams | |
| US9471585B1 (en) | Decentralized de-duplication techniques for largescale data streams | |
| CN104011701B (en) | Content transmission network system and the method that can be operated in content distribution network | |
| CN108683516A (en) | A kind of upgrade method of application example, device and system | |
| WO2016183545A1 (en) | Distributed and optimized garbage collection of remote and exported table handle links to update propagation graph nodes | |
| CN108804119A (en) | Configure update method, device, system, configuration center, application node and medium | |
| US20180165177A1 (en) | Debugging distributed web service requests | |
| CN103034540B (en) | Distributed information system and equipment thereof and coordination approach | |
| TW201312467A (en) | Method and system for distributed application stack deployment | |
| CN105653329A (en) | Application management method, apparatus and system | |
| US10469616B2 (en) | Data driven bin packing implementation for data centers with variable node capabilities | |
| CN103034541B (en) | A kind of distributed information system and equipment therein and method | |
| CN108369544A (en) | The server delayed in computing system restores | |
| CN108123851A (en) | The lifetime detection method and device of main and subordinate node synchronization link in distributed system | |
| US11294740B2 (en) | Event to serverless function workflow instance mapping mechanism | |
| CN109788024A (en) | The high-performance distributed remote meter reading acquisition server solution of High Availabitity high concurrent | |
| CN107666401A (en) | A kind of configuration information obtaining method and terminal | |
| CN109462507A (en) | Configure update method, device, system and electronic equipment |
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 |