CN106790595A - A kind of Docker containers active load balancer and method - Google Patents
A kind of Docker containers active load balancer and method Download PDFInfo
- Publication number
- CN106790595A CN106790595A CN201611241839.XA CN201611241839A CN106790595A CN 106790595 A CN106790595 A CN 106790595A CN 201611241839 A CN201611241839 A CN 201611241839A CN 106790595 A CN106790595 A CN 106790595A
- Authority
- CN
- China
- Prior art keywords
- application
- docker
- module
- distributed coordination
- pending application
- 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
- 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
-
- 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/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- 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/56—Provisioning of proxy services
Abstract
The invention discloses a kind of Docker containers active load balancer and method, the method comprises the following steps：Pending application file is received, pending application details are preset；The pending application file is converted into Docker mirror images；Perform in the Docker mirror images and order using starting；Registration request is sent, the application is registered to distributed coordination server；The log-on message is obtained from distributed coordination server, obtain the delta data of application example correspondence container, and parsed the data, by configuration template, more new configuration file is to Universal load balanced device, the present invention is realized and is actively discovered and login mechanism in real time, and uses general load equalizer, for Docker container clusters provide service.
Description
Technical field
The present invention is on Internet technical field, more particularly to a kind of Docker containers active load balancer and side
Method.
Background technology
Docker is an application container engine increased income, and single example operation Docker containers cannot meet production needs,
Typically service can be externally provided using the pattern of Docker clusters in industry, it is more at present to be using increase income container cluster management
System such as kubernetes, mesos, swarm simultaneously combine basic network solution such as flannel, weave, pipework etc.,
Docker cluster Problems are solved, but the load balancing of Docker container clusters fails have perfect solution always.
Docker containers find that target is that the service that would fit snugly within inside Docker containers shows, and reduce or eliminate
Communicate barrier between Docker containers.
Docker container cluster load balance purposes are to find to unify the container of normal operation to lead to by Docker containers
Overload balanced device is forwarded, container transparent unaware of the caller to load equalizer rear end.A kind of Docker containers are actively negative
Carry balanced purpose be when Docker containers start successfully the information such as Apply Names, Docker containers IP address, application port oneself
It is dynamic to push, and Docker container instances are mounted to load equalizer, so that the Docker container instances provide service energy
Power, whole process does not need manual intervention.Caller is comprehended rear end Docker container operation details and is included can completely dispense with
Docker containers number, ip and port, also include whether to be run under physical machine or virtual machine, as long as there is a normal fortune
Capable container, just can externally provide service, fully transparent to user.Simultaneously for abnormal service, whole system will in time
Response is processed, and abnormal Docker examples are picked out from load equalizer list.
At present, a kind of load balancing scheme such as kubernetes of common Docker clusters is provided with the negative of Three models
Carry balanced：1st, using the mode of host IP+PORT, this mode needs for the IP of host to be exposed to caller, particularly
After host delays machine, in addition it is also necessary to which caller is switched to other hosts；2nd, using the primary Service for carrying mode and with
Private IP externally provide service, and this mode needs the caller must also in kubernetes cluster internals, otherwise
PrivateIP cannot be accessed；3rd, using special load balancing under the IaaS environment such as GCE, AWS, this mode most enterprises are all
Do not possess, it is all these can not all meet production to High Availabitity the need for.
It should be evident that tending to rely on cluster management system based on common Docker cluster load balance schemes, collect
The change or upgrading of cluster management system can cause former methodical failure；Or to there is multiple delay performance relatively low, not only monitor
The information such as startup, the stopping change of Docker containers, also refresh load equalizer by synchronizing information；Or due to using special negative
Balanced device is carried, it is higher to study, maintenance cost requirement, it is not suitable for technology precipitation, increase entreprise cost；Or when service operation is various
If Docker environment, vmware, kvm or independent operating are in host environment under environment, it is impossible to the need for meeting isomerous environment.
The content of the invention
To overcome the shortcomings of that above-mentioned prior art is present, the purpose of the present invention is to provide a kind of Docker containers actively to bear
Balancer and method are carried, to realize being actively discovered and login mechanism in real time, and general load equalizer is used, is Docker
Container cluster provides service, it is ensured that to application without intrusion, facilitate system to carry out containerization transformation.
It is that, up to above and other purpose, the present invention proposes a kind of Docker containers active load balancer, including：
Mirror image modular converter, for providing the Docker foundation images comprising application manager and being converted to pending application
Docker mirror images；
Application manager, for starting the Docker mirror images, and according to default application message, parses and performs the pending application
Startup order, and send registration request, the application is registered to distributed coordination server；
Distributed coordination server, for disposing distributed coordination service；
Detector, for monitoring the application situation of change on the distributed coordination server, will send out using situation of change
Deliver to load balancing proxy server；
Load balancing proxy server, by the application situation of change is according to the configuration data of configuration template conversion certain format and holds
OK, and it is configured to Universal load balanced device；
Universal load balanced device, for disposing Universal load balancing service.
Further, the mirror image modular converter includes：
Foundation image, the Docker that the basic environment needed for depositing the application manager and pending application in advance builds
Mirror image, and using this mirror image as the foundation image of pending application, and it is stored in mirror image warehouse；
Order receiver module, the identification information for receiving the pending application；
Mirror image builds module, builds pending application mirror image by Dockerfile, and be uploaded to mirror image warehouse.
Further, the application manager includes：
Parameter analysis of electrochemical module, for parsing default application message；
Command execution module, order is performed for receiving the application that the Parameter analysis of electrochemical module is parsed, and is performed this and is ordered and obtain
Command execution results, if if implementing result is normal, calling and applying Registering modules；
Using Registering modules, for the state letter for obtaining the Parameter analysis of electrochemical module data for parsing and obtaining pending application
Cease, and interim conversation is set up with the distributed coordination server and link, the status details of the application are registered to distribution association
Adjust server；
Health examination module, for the health condition according to default health examination order poll application, and result is notified to be somebody's turn to do
Using Registering modules.
Further, when the Docker containers are registered to the distributed coordination server by this using Registering modules,
Judge the distributed coordination server directory whether there is this using corresponding catalogue, if nothing, in distributed coordination server wound
Build new catalogue and simultaneously in one new node of the directory creating.
Further, the detector includes：
Module is monitored, for monitoring the application situation of change on the distributed coordination server, if using corresponding
Docker container instance states change, and trigger the first sending module；
First sending module, for that will be sent to load balancing proxy server using situation of change.
Further, the load balancing proxy server includes：
First receiver module, is attached with first sending module and maintains heartbeat, first receiver module receive this first
The instruction that sending module is sent, and call data resolution module；
Data resolution module, the format analysis instruction according to configuration template module now, and incoming second order performs mould
Block；
Configuration template module, its masterplate data are different according to the load equalizer that load balancing proxy server is acted on behalf of；
Second command execution module, writes data into the Universal load equalizer configuration file directory, performs the Universal load equal
The reset command of weighing apparatus.
To reach above-mentioned purpose, the present invention also provides a kind of Docker containers active load equalization methods, including following step
Suddenly：
Step one, receives pending application file, presets pending application details；
Step 2, Docker mirror images are converted to by the pending application file；
Step 3, orders in the execution Docker mirror images using startup；
Step 4, sends registration request, and the application is registered into distributed coordination server；
Step 5, obtains the log-on message from distributed coordination server, obtains the change number of application example correspondence container
According to, and the data are parsed, by configuration template, more new configuration file to Universal load balanced device.
Further, step 5 is further included：
The directory node in distributed coordination device is applied in monitoring, and the change information of directory node is sent into load balancing agency
Device；
Change information is synchronized to by Universal load balanced device according to configuration template.
Further, in step 2, the identification information of the pending application file is write according to specification
Dockerfile, pending application mirror image is built by pending application foundation mirror image with pending application by Dockerfile.
Further, in step 4, the Docker containers of the pending application are maintained with the distributed coordination server
Interim conversation, when application is abnormal, disconnection immediately is linked with the distributed coordination server, and is automatically exited from.
Compared with prior art, a kind of Docker containers active load balancer of the invention and method, are managed by application
Reason device initiates to connect and carry out to register application container information to distributed coordination server, and real-time to application container health and fitness information
Monitoring, and active synchronization feeds back to distributed coordination server, using detector according to the information master of distributed coordination server
It is dynamic to update to load equalizer, Docker containers are successfully mounted to load equalizer, make full use of Universal load balanced device
Ripe production and O＆M experience, for tradition application Docker containerization transformations, are effectively reduced improvement cost, the present invention by
Container actively initiates to connect and registered to load equalizer, and using mature and stable load equalizer, the process is without pre-
First configure equilibrium allocation file and load equalizer need not be restarted, be automatically obtained load balancing, overcome current container
Middle load-balancing method is difficult in adapt to be used to provide asking for back-end services, dynamic change container cluster in cloud computing system
Topic.
Brief description of the drawings
Fig. 1 is a kind of system architecture diagram of Docker containers active load balancer of first embodiment of the invention；
Fig. 2 is a kind of system architecture diagram of Docker containers active load balancer of second embodiment of the invention；
The step of Fig. 3 is a kind of Docker containers active load equalization methods of third embodiment of the invention flow chart；
A kind of flow chart of Docker containers active load equalization methods that Fig. 4 is provided for the specific embodiment of the invention.
Specific embodiment
Below by way of specific instantiation and embodiments of the present invention are described with reference to the drawings, those skilled in the art can
Further advantage of the invention and effect are understood by content disclosed in the present specification easily.The present invention also can be different by other
Instantiation implemented or applied, the various details in this specification also can based on different viewpoints with application, without departing substantially from
Various modifications and change are carried out under spirit of the invention.
Fig. 1 is a kind of system architecture diagram of Docker containers active load balancer of first embodiment of the invention.Such as
Shown in Fig. 1, a kind of Docker containers active load balancer of the invention, including：Mirror image modular converter 101, application manager
102nd, distributed coordination server 103, detector 104, load balancing proxy server 105 and Universal load balanced device 106.
Mirror image modular converter 101, for providing the Docker foundation images comprising application manager and by pending application
Be converted to Docker mirror images.
Specifically, mirror image modular converter 101 is the Docker environment of deployment success, it include foundation image 301,
Order receiver module 302 and mirror image build module 303, and application manager has been housed in advance with pending application in the module
The Docker mirror images that the basic environment of needs builds, and using this mirror image as pending application foundation image 301, while also depositing
It is placed on mirror image warehouse.Pending application will be stored in mirror image conversion equipment using modes such as ftp, tftp, scp, wget corresponding
Catalogue.Order receiver module 302 receives user input by the identification information of pending application, and the mark of the pending application is believed
Breath including application name, using starting, cease and desist order, port, using information such as additional information and health examination orders, and parse
With the local Dockerfile masterplates that prestore, new Dockerfile is formed, mirror image is built module 303 and built by Dockerfile
Pending application mirror image, and mirror image warehouse is uploaded to, now this at least includes application manager, pending application using mirror image
And corresponding parameter.
Application manager 102, for starting the Docker mirror images, and according to default application message, parses pending answering
Startup order, and the order is performed, and registration request is sent, the application is registered to distributed coordination server.
Specifically, application manager 102 is including Parameter analysis of electrochemical module 311, command execution module 312, using Registering modules
313rd, health examination module 314.Wherein Parameter analysis of electrochemical module 311 is responsible for the default application message of parsing, the default application letter
Breath includes：Application name, using starting, cease and desist order, port, using additional information etc., will include that application be opened using order is performed
It is dynamic to order, command execution module 312 is passed to using ceasing and desisting order；Command execution module 312, for receiving Parameter analysis of electrochemical module
311 applications for parsing perform order, perform this and order and obtain command execution results, if if implementing result is normal, calling
Using Registering modules 313；Got parms the data and obtain pending that parsing module 311 parses using Registering modules 313
The status information of application, and set up interim conversation with distributed coordination server 103 and link, by the status details of the application：Hold
Device status information, container IP, port, application name, distributed coordination server 103 is registered to using additional information, when find should
With the abnormal phenomenons such as machine of such as delaying, automatic disconnection links with distributed coordination server 103.Wherein, when the Docker should
During with starting, the Parameter analysis of electrochemical module 312 parses the presupposed information of acted on behalf of application, call instruction performing module 312
Perform application and start order, and the distributed coordination server 103 is notified by application Registering modules 313, in the file mesh
Record is lower to be created and the corresponding file of the pending application.After a Docker container for performing application starts successfully,
Using Registering modules 313 will using application message be registered to distributed coordination server 103 correspondence application under file as
Application node example.
In detail, when Docker containers are registered to distributed coordination server 103 by application Registering modules 313, sentence
The disconnected catalogue of distributed coordination server 103 whether there is this using corresponding catalogue, if nothing, in distributed coordination server 103
Create new catalogue and simultaneously in one new node of the directory creating, the IP and application port of container are the name of the node
Claim.When the application has new Docker examples to produce, new Docker examples will be all registered under the catalogue.When the application certain
Individual Docker examples are delayed machine, then application Registering modules 313 disconnect the connection with distributed coordination server 103, same time-division automatically
Cloth coordination service device 103 deletes the log-on message of the Docker examples.
Health examination module 314 is main and according to the health condition of default health examination order poll application, and will knot
Fruit notifies to apply Registering modules 313.Health examination module 314 mainly checks for the container that fails, and failure container can be
Finger can not provide the container of normal service.For example, when the detection container of health examination module 314 there occurs abnormal such as container and health
Check module 314 can not healthy heartbeat, container process phenomenon, the i.e. container such as surprisingly stop service can not being provided, now can be with
Think that the container is failure container.Optionally, for any one container, the container and health examination module 314 can be monitored
Communication connection whether disconnect, if health examination module 314 monitor the container for failure container.Health examination module 314 is led to
Know using Registering modules 313 will automatically with the break link of distributed coordination server 103 so that distributed coordination server
103 delete the failure container node.
Distributed coordination server 103, for disposing distributed coordination service.In the specific embodiment of the invention, distribution
Formula coordination service device 103 can have one or more, when there is multiple distributed coordination servers 103, the plurality of distributed association
Adjusting server 103 is used to form distributed coordination service group, and can be selected from the plurality of distributed coordination server 103
One leader (leader), wherein, distributed coordination server 103 is used to dispose distributed coordination service.In the present embodiment
Zookeeper is used as distributed coordination server for deployment, and zookeeper is a distributed coordination server increased income.It is
One software that Consistency service is provided for Distributed Application, there is provided function include：Configuring maintenance, domain name service, distribution
Synchronous, group service etc..It is specifically intended that when the modification of the data stored in zookeeper directory nodes, child node catalogue
Change etc., once change can notify to set the client for monitoring, this function is zookeeper most important for application
Characteristic, the function that can be realized by this characteristic includes the centralized management of configuration, cluster management, distributed lock etc..Herein,
Main configuring maintenance and distributed synchronization this two functions of having used in zookeeper, wherein, in distributed coordination clothes
A file directory is safeguarded in business device 103, is existed and the multiple application corresponding file of difference in this document catalogue.That is,
There are multiple files under this document catalogue, each file correspondence one is applied, at least one node under each file,
Each node one Docker container instance of correspondence.Such that it is able to manage application by the file and node of zookeeper
And the Docker examples of application, it is possible to realize to Docker container state change managements, that is, realize to Docker containers
It was found that.
For example, default/apps/catalog is the parent directory of all applications, if using entitled in presupposed information
Helloworld, port is 8080, application one Docker example of correspondence, and container IP is 172.17.0.2, then should
Catalogue with correspondence zookeeper is /apps/catalog/helloworld, the corresponding zookeeper sections of the Docker examples
Point is /apps/catalog/helloworld/172.17.0.2：8080, if this application again increase newly a Docker example and
Docker containers IP is 172.17.0.3, then this is /apps/catalog/helloworld/ using zookeeper nodal directories
172.17.0.2：8080 and/apps/catalog/helloworld/172.17.0.3：8080.If the IP is
172.17.0.3 Docker containers are delayed machine, then this is changed into/apps/catalog/helloworld/ using corresponding node
172.17.0.2：8080.By means of the file directory and node and application and the corresponding relation of Docker examples of zookeeper,
Application one catalogue of correspondence, Docker containers one corresponding relation for directory node of correspondence can be realized.
Detector 104, for corresponding all application file folders in monitoring distributed coordination service device 103.This document is pressed from both sides
Folder Name correspondence Apply Names, unique one file with the entitled Folder Name of application of correspondence of each application.
Detector 104 includes monitoring the sending module of module 331 and first, in this specific embodiment, is starting pending application
After Docker examples, the Docker example details can be registered to the distributed coordination server 103, monitor module 331 and examine
Measure and there occurs change using catalogue/apps/catalog, and read using the node details of catalogue/apps/catalog, by
First sending module 332 sends corresponding instruction notification load balancing proxy server 105 and increases an application example information newly, to general
Load equalizer 106 updates configuration.Alternatively, when one of Docker examples of pending application stop or machine of delaying, health
Check that module 314 detects the example and exception occurs, notify that application Registering modules 313 disconnect and distributed coordination server 103
Link, distributed coordination server 103 deletes this directory node information, now monitors module 331 and is immediately detected and applies mesh
Record/apps/catalog catalogues there occurs change, and notification payload equilibrium proxy server 105 deletes one, to Universal load balanced device
106 update configuration.
Load balancing proxy server 105, for by configuration template, more new configuration file to Universal load balanced device 106.
Specifically, load balancing proxy server 105 includes the first receiver module 341, data resolution module 342, configuration template
Module 343, the second command execution module 344.Load balancing proxy server 105 and the deployment 106 of Universal load balanced device are in same clothes
Business device.First receiver module 341 is attached and maintains heartbeat by Transmission Control Protocol and the first sending module 332, and first receives mould
Block 341 receives the instruction that the first sending module 332 is sent, and calls data resolution module 342.The basis of data resolution module 342
The format analysis of the configuration template module 343 now instructions, masterplate data are according to load balancing generation in configuration template module 343
The load equalizer acted on behalf of of reason device 105 is different, and masterplate data are had nothing in common with each other, such as nginx applicable configuration and lvs,
Keepalived applicable configuration is different, and data resolution module 342 press masterplate data and will be successfully put into and face after instruction parses
When region of memory, call the second command execution module 344.Second command execution module 344 is preset Universal load balanced device 106 and is matched somebody with somebody
Put file path, startup, stopping, reset command and assign the control authority of execution Universal load balanced device 106, when data parse mould
After incoming second command execution module 344 of data that block 342 will be parsed, the second command execution module 344 reads above-mentioned interim
Region of memory writes data into the configuration file catalogue of Universal load balanced device 106, and perform Universal load balanced device 106 restarts life
Order.
Universal load balanced device 106, for disposing Universal load balancing service.In the present embodiment, Universal load is balanced
Device 106 may be located in independent server, it is also possible in the server cluster being made up of some servers.Such as
Nginx and lvs are the soft load equalizers increased income, and current industry has accumulated more knowhow, research and development, fortune for enterprise
Dimension and learning cost are substantially reduced.Nginx and lvs differences, lvs have when four laminar flow amounts is processed significant performance but
Higher to network requirement, nginx is usually used in seven layers of load balancing, relatively low to network environment requirement.Because Universal load is balanced
Device 106 is familiar to the person skilled in the art, be will not be repeated here.
In the present invention, application manager can also operate in non-Docker containers environment with pending application, or hold
The load balancing of application cluster is realized under device environment together.A kind of Docker for being illustrated in figure 2 second embodiment of the invention holds
The system architecture diagram of device active load device in a balanced way, wherein, application manager 203 pre-sets application message：Application name, should
With starting, cease and desist order, port, using additional information etc., after application manager 203 starts, should by the parsing of Parameter analysis of electrochemical module
With details, and start it is pending apply 204, after pending application 204 starts successfully, will be using reality by application manager 203
The status information of example, host IP, port, application name, distributed coordination server 205 is registered to using additional information.It is different
Be：1st, application example becomes host IP by container IP, and 2, the application example port of same host operation can not be identical,
The processing procedure of each module is basically identical with first embodiment afterwards, repeats no more.
The step of Fig. 3 is a kind of Docker containers active load equalization methods of third embodiment of the invention flow chart.Such as
Shown in Fig. 3, a kind of Docker containers active load equalization methods of the invention comprise the following steps：
Step 301, receives pending application file, presets pending application details.Wherein described pending application details include
Using start order, cease and desist order, Apply Names, version number, using additional information（TCP/HTTP）, and application end message
Breath.
Step 302, Docker mirror images are converted to by the pending application file.Specifically, by pending application file
Identification information, such as Apply Names, using start order, cease and desist order, port, using additional information and health examination life
Order etc. writes Dockerfile according to specification, and pending application foundation mirror image is built with pending application by Dockerfile
Pending application mirror image, i.e. Docker mirror images.
Step 303, orders in the execution Docker mirror images using startup.That is, when pending application has succeeded
When being configured to Docker mirror images, start the mirror image, and according to default application message, parse the startup order of pending application,
And perform the order.
Step 304, sends registration request, and the application is registered into distributed coordination server.Taken in the registration request
With the container IP of application message in the Docker containers, application port information, Apply Names, using additional information etc..
In the specific embodiment of the invention, now distributed coordination server creates a catalogue with application name as title, and in the mesh
Record is lower to create a node, the wherein entitled container IP of the node and port, such as 172.17.0.2:8080, other information is as answered
Stored in the node with additional information.The Docker containers of pending application remain interim with distributed coordination server
Session sessions, when application is abnormal, disconnection immediately is linked with distributed coordination server, and is automatically exited from.Due to point
Cloth coordination service uses interim session sessions, the interim conversation once disconnecting, and distributed coordination server is simultaneously deleted at once
Except all information of the node.
Step 305, obtains the log-on message, the i.e. change of application example correspondence container from distributed coordination server
Data, and the data are parsed, by configuration template, more new configuration file to load equalizer.Specifically, step 305
Further include：
The directory node in distributed coordination device is applied in step S1, monitoring, and the change information of node is sent into load balancing
Proxy server.Learnt according to above-mentioned steps S304, it is a catalogue that newly-increased application has succeeded in distributed coordination server registration, main
The dynamic nodal information read under the catalogue, once having newly-increased Node registry under detecting the catalogue, sends instructions to downstream module i.e.
Load balancing proxy server, the instruction carries directory name（That is to say application name）, all nodenames under the catalogue（That is to say section
Point instance address）And additional information；
Step S2, load equalizer, such as nginx, lvs are synchronized to according to configuration template by change information.According to above-mentioned steps S1
Learn, the instruction that load equalizer proxy server receiving step S1 sends is included applies lower all nodal informations, then load balancing
Proxy server is the parameter for being converted into load equalizer identification according to configuration template relevant parameter, and writes corresponding configuration file,
Wherein load balancing proxy server should preset load equalizer configuration file path, startup, stopping, reset command.Have in the present invention
In body embodiment, the configuration template respectively has difference according to the load equalizer selected.
A kind of flow chart of Docker containers active load equalization methods that Fig. 4 is provided for the specific embodiment of the invention, such as
Shown in Fig. 4, the method can include：
Step S401, presets application message, is a new mirror image by pending application build.Specifically, by pending application
Identification information：Application name, using starting, cease and desist order, port, using additional information and health examination order according to specification
Write-in Dockerfile, pending application mirror is built by pending application foundation mirror image with pending application by Dockerfile
Picture.
Step S402, disposes distributed coordination server, such as zookeeper in distributed coordination server.It is distributed
Coordination service device can be single node or cluster mode.Especially, when such as catalogue, son once occurs in distributed coordination server
Node, data etc. change, and can monitor client with proactive notification, can realize occurring when application example node by this characteristic
Change can immediately notify that downstream module is processed in time.
Step S403, described in above-mentioned steps S401, pending application is successfully configured to Docker mirror images, starts the mirror
Picture, and according to default application message, the startup order of pending application is parsed, and the order is performed, then answered according to default
Inspected periodically with health examination sentence and apply health degree.
Step S404, after pending application success starts, the status details of the application is included：Container state information,
Container IP, port, application name, distributed coordination service that above-mentioned steps S402 deployment success is registered to using additional information
Device, now distributed coordination server creates a catalogue with application name as title, and a node is created under the catalogue, its
In the node entitled container IP and port, such as 172.17.0.2:8080, other information such as application additional information storage is at this
In node.The Docker containers of pending application maintain interim session sessions with distributed coordination server, when application is different
Chang Shi, immediately disconnection is linked with distributed coordination server, and is automatically exited from.Due to using interim with distributed coordination service
Session sessions, once disconnecting, distributed coordination server simultaneously deletes all information of the node to the interim conversation at once.
Step S405, in the deployment load balancing service of Universal load balanced device such as nginx, lvs.Load equalizer and each
Node, each node container network ensure interconnect, the network plan based on container intercommunication can using port mapping, directly
Path or the mode of overlay network, the network plan is familiar to the person skilled in the art, be will not be repeated here.
The directory node in distributed coordination device is applied in step S406, monitoring, and the change information of node is sent to negative
Carry balanced proxy server.Learnt according to above-mentioned steps S404, it is one that newly-increased application has succeeded in distributed coordination server registration
Catalogue, actively reads the nodal information under the catalogue, once having newly-increased Node registry under detecting the catalogue, sends instructions to downstream
Module is load balancing proxy server, and the instruction carries directory name（That is to say application name）, all nodenames under the catalogue（
It is node instance address）And additional information.
Step S407, load equalizer such as nginx, lvs are synchronized to according to configuration template by change information.According to above-mentioned step
Rapid S406 learns that the instruction that load equalizer proxy server receiving step S406 sends is included applies lower all nodal informations, then
Load balancing proxy server is to be converted into the parameter that load equalizer is recognized according to configuration template relevant parameter, and write-in is matched somebody with somebody accordingly
Put file.Wherein load balancing proxy server should preset load equalizer configuration file path, startup, stopping, reset command.
The above method makes to apply the ruuning situation moment under Docker environment to feed back on SiteServer LBS, by adopting
With the mechanism of general load equalizer and Active Registration, so as to by application call person from changeable, complicated Docker containers ground
Location is converted to and accesses fixed load equalizer address, whole-process automatic discovery, automatic registration, to caller unaware, Er Qieying
Can also apply equally applicable under host or virtual machine environment with pending simultaneously with manager.
Relative and above-described embodiment, further, in the present embodiment in S401 in the device in advance by Program Manager
With pending application need basic environment be configured to new Docker mirror images as pending application foundation image step it
It is preceding also to include：The basic environment that pending application needs is obtained from mirror image warehouse.Specifically, mirror image warehouse is used for memory image
File, including basic environment, the foundation image of pending application, the pending application mirror image that pending application needs are new to build
Mirror image is unifiedly stored to mirror image warehouse.In the present embodiment, mirror image conversion equipment, each node are connected with the communication of mirror image Warehouse Establishing.
In sum, a kind of Docker containers active load balancer of the invention and method, using application manager master
It is dynamic to register container change information, while interim conversation mechanism is used using detector and distributed coordination server, without logical
Heartbeat mode is crossed in real time to monitor distributed coordination server, once container finds change, by using load balancing generation
The change information of the container is write Universal load balanced device by reason device, application containerization transformation is present invention can be suitably applied to, to existing
Have using without constraint and limitation；Container situation of change can in time be monitored without using heartbeat mechanism, so as to avoid heartbeat
The timeout issue for causing；From the soft load equalizer of universal industrialization, to study, relatively low using the cost requirement of, O＆M, save
The research and development of enterprise and O＆M cost, also illustrate under non-container environment in the embodiment of the present invention, will be treated by application manager
The situation of change for performing application is synchronized on load equalizer, and satisfaction is applied the need for isomerous environment is run.
The above-described embodiments merely illustrate the principles and effects of the present invention, not for the limitation present invention.Any
Art personnel can be modified above-described embodiment and are changed under without prejudice to spirit and scope of the invention.Therefore,
The scope of the present invention, should be as listed by claims.
Claims (10)
1. a kind of Docker containers active load balancer, including：
Mirror image modular converter, for providing the Docker foundation images comprising application manager and being converted to pending application
Docker mirror images；
Application manager, for starting the Docker mirror images, and according to default application message, parses and performs the pending application
Startup order, and the application is registered to distributed coordination server；
Distributed coordination server, for disposing distributed coordination service；
Detector, for monitoring the application situation of change on the distributed coordination server, will send out using situation of change
Deliver to load balancing proxy server；
Load balancing proxy server, by the application situation of change is according to the configuration data of configuration template conversion certain format and holds
OK, and it is configured to Universal load balanced device；
Universal load balanced device, for disposing Universal load balancing service.
2. a kind of Docker containers active load balancer as claimed in claim 1, it is characterised in that the mirror image modulus of conversion
Block includes：
Foundation image, the Docker that the basic environment needed for depositing the application manager and pending application in advance builds
Mirror image, and using this mirror image as the foundation image of pending application, and it is stored in mirror image warehouse；
Order receiver module, the identification information for receiving the pending application；
Mirror image builds module, builds pending application mirror image by Dockerfile, and be uploaded to mirror image warehouse.
3. a kind of Docker containers active load balancer as claimed in claim 2, it is characterised in that the application manager
Including：
Parameter analysis of electrochemical module, for parsing default application message；
Command execution module, order is performed for receiving the application that the Parameter analysis of electrochemical module is parsed, and is performed this and is ordered and obtain
Command execution results, if if implementing result is normal, calling and applying Registering modules；
Using Registering modules, for the state letter for obtaining the Parameter analysis of electrochemical module data for parsing and obtaining pending application
Cease, and interim conversation is set up with the distributed coordination server and link, the status details of the application are registered to distribution association
Adjust server；
Health examination module, for the health condition according to default health examination order poll application, and result is notified to be somebody's turn to do
Using Registering modules.
4. a kind of Docker containers active load balancer as claimed in claim 3, it is characterised in that：When the Docker holds
When device is registered to the distributed coordination server by this using Registering modules, judge the distributed coordination server directory whether there is
This applies corresponding catalogue, if nothing, new catalogue is created and simultaneously in the directory creating one in distributed coordination server
New node.
5. a kind of Docker containers active load balancer as claimed in claim 3, it is characterised in that the detector bag
Include：
Module is monitored, for monitoring the application situation of change on the distributed coordination server, if using corresponding
Docker container instance states change, and trigger the first sending module；
First sending module, for that will be sent to load balancing proxy server using situation of change.
6. a kind of Docker containers active load balancer as claimed in claim 5, it is characterised in that the load balancing generation
Reason device includes：
First receiver module, is attached with first sending module and maintains heartbeat, first receiver module receive this first
The instruction that sending module is sent, and call data resolution module；
Data resolution module, the format analysis instruction according to configuration template module now, and incoming second order performs mould
Block；
Configuration template module, its masterplate data are different according to the load equalizer that load balancing proxy server is acted on behalf of；
Second command execution module, writes data into the Universal load equalizer configuration file directory, performs the Universal load equal
The reset command of weighing apparatus.
7. a kind of Docker containers active load equalization methods, comprise the following steps：
Step one, receives pending application file, presets pending application details；
Step 2, Docker mirror images are converted to by the pending application file；
Step 3, orders in the execution Docker mirror images using startup；
Step 4, sends registration request, and the application is registered into distributed coordination server；
Step 5, obtains the log-on message from distributed coordination server, obtains the change number of application example correspondence container
According to, and the data are parsed, by configuration template, more new configuration file to Universal load balanced device.
8. a kind of Docker containers active load equalization methods as claimed in claim 7, it is characterised in that：Step 5 is further
Including：
The directory node in distributed coordination device is applied in monitoring, and the change information of directory node is sent into load balancing agency
Device；
Change information is synchronized to by Universal load balanced device according to configuration template.
9. a kind of Docker containers active load equalization methods as claimed in claim 8, it is characterised in that：In step 2,
By the identification information of the pending application file according to specification write Dockerfile, by pending application foundation mirror image with wait to hold
Row application builds pending application mirror image by Dockerfile.
10. a kind of Docker containers active load equalization methods as claimed in claim 8, it is characterised in that：In step 4,
The Docker containers of the pending application maintain interim conversation with the distributed coordination server, when application is abnormal, break immediately
Open and linked with the distributed coordination server, and automatically exit from.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611241839.XA CN106790595B (en) | 2016-12-29 | 2016-12-29 | Docker container active load balancing device and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611241839.XA CN106790595B (en) | 2016-12-29 | 2016-12-29 | Docker container active load balancing device and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106790595A true CN106790595A (en) | 2017-05-31 |
| CN106790595B CN106790595B (en) | 2020-12-22 |
Family
ID=58923590
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611241839.XA Active CN106790595B (en) | 2016-12-29 | 2016-12-29 | Docker container active load balancing device and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106790595B (en) |
Cited By (35)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107248986A (en) * | 2017-06-08 | 2017-10-13 | 医惠科技有限公司 | A kind of service tray method |
| CN107294785A (en) * | 2017-07-11 | 2017-10-24 | 上海帝联信息科技股份有限公司 | The automatic deployment method and device, computer-readable recording medium of CDN node service |
| CN107360018A (en) * | 2017-06-05 | 2017-11-17 | 小草数语（北京）科技有限公司 | Config update method and device |
| CN107635002A (en) * | 2017-09-21 | 2018-01-26 | 浪潮软件股份有限公司 | A kind of access method and device of containerization application |
| CN107766052A (en) * | 2017-09-18 | 2018-03-06 | 网宿科技股份有限公司 | A kind of method and apparatus for building mirror image |
| CN107885547A (en) * | 2017-11-08 | 2018-04-06 | 江苏国泰新点软件有限公司 | A kind of collocation method of application program, device, configuration equipment and storage medium |
| CN108021428A (en) * | 2017-12-05 | 2018-05-11 | 华迪计算机集团有限公司 | A kind of method and system that network target range is realized based on Docker |
| CN108446326A (en) * | 2018-02-11 | 2018-08-24 | 江苏微锐超算科技有限公司 | A kind of isomeric data management method and system based on container |
| CN108551488A (en) * | 2018-05-03 | 2018-09-18 | 山东汇贸电子口岸有限公司 | Distributed container cluster load balancing method based on domestic CPU and OS |
| CN108616599A (en) * | 2018-05-11 | 2018-10-02 | 北京辰森世纪科技股份有限公司 | Application service registration, newer method and device |
| CN108874549A (en) * | 2018-07-19 | 2018-11-23 | 北京百度网讯科技有限公司 | resource multiplexing method, device, terminal and computer readable storage medium |
| CN108920153A (en) * | 2018-05-29 | 2018-11-30 | 华南理工大学 | A kind of Docker container dynamic dispatching method based on load estimation |
| CN109120481A (en) * | 2018-09-27 | 2019-01-01 | 上海新炬网络信息技术股份有限公司 | Method based on Zabbix open source monitor component DCOS container and bosom part |
| CN109309693A (en) * | 2017-07-26 | 2019-02-05 | 财付通支付科技有限公司 | Services system, dispositions method and device, equipment and storage medium based on docker |
| CN109343963A (en) * | 2018-10-30 | 2019-02-15 | 杭州数梦工场科技有限公司 | A kind of the application access method, apparatus and relevant device of container cluster |
| CN109451065A (en) * | 2018-12-26 | 2019-03-08 | 中电福富信息科技有限公司 | A kind of soft load balancing shunts automated system and its operation method |
| CN110087107A (en) * | 2019-04-25 | 2019-08-02 | 视联动力信息技术股份有限公司 | A kind of method and view networked system of raising system self-adaption ability |
| CN110134455A (en) * | 2019-04-12 | 2019-08-16 | 平安医疗健康管理股份有限公司 | A kind of application management system and method |
| CN110224860A (en) * | 2019-05-17 | 2019-09-10 | 平安科技（深圳）有限公司 | Load balancing application creation method, device, computer equipment and storage medium |
| CN110569056A (en) * | 2019-09-11 | 2019-12-13 | 北京奇艺世纪科技有限公司 | Method and device for updating rule service information |
| CN110618821A (en) * | 2018-06-19 | 2019-12-27 | 普天信息技术有限公司 | Container cluster system based on Docker and rapid building method |
| CN110750592A (en) * | 2019-09-06 | 2020-02-04 | 中国平安财产保险股份有限公司 | Data synchronization method, device and terminal equipment |
| CN110764875A (en) * | 2019-10-25 | 2020-02-07 | 北京威晟艾德尔科技有限公司 | Docker container creating method based on competition mechanism |
| CN110830289A (en) * | 2019-10-21 | 2020-02-21 | 华中科技大学 | Container abnormity monitoring method and monitoring system |
| CN110830574A (en) * | 2019-11-05 | 2020-02-21 | 浪潮云信息技术有限公司 | Method for realizing intranet load balance based on docker container |
| CN110912953A (en) * | 2018-09-17 | 2020-03-24 | 深圳市优必选科技有限公司 | File storage system and method |
| CN111163122A (en) * | 2019-11-21 | 2020-05-15 | 江苏艾佳家居用品有限公司 | TCP configuration method based on Nginx self-research extension module and for automatically pulling service registration center |
| CN112099915A (en) * | 2020-09-07 | 2020-12-18 | 紫光云(南京)数字技术有限公司 | Soft load balancing dynamic issuing configuration method and system |
| CN112527319A (en) * | 2020-12-16 | 2021-03-19 | 浙江大学德清先进技术与产业研究院 | Management method of Docker-based remote sensing intelligent processing algorithm |
| CN112764825A (en) * | 2020-12-30 | 2021-05-07 | 望海康信(北京)科技股份公司 | Service integration system, corresponding device and storage medium |
| CN113127145A (en) * | 2020-01-15 | 2021-07-16 | 中移(苏州)软件技术有限公司 | Information processing method, device and storage medium |
| CN113127435A (en) * | 2021-03-30 | 2021-07-16 | 杭州当虹科技股份有限公司 | Intelligent synchronization method and system for files of main and standby systems |
| CN113778613A (en) * | 2021-07-15 | 2021-12-10 | 上海浦东发展银行股份有限公司 | Unified management method for multi-data center double-stack container cloud platform |
| CN114640633A (en) * | 2022-03-29 | 2022-06-17 | 京东科技信息技术有限公司 | Load balancer, implementation method thereof, load balancing method and gateway system |
| CN115190015A (en) * | 2022-07-12 | 2022-10-14 | 中国工商银行股份有限公司 | Soft load system configuration method and device, computer equipment and storage medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140149489A1 (en) * | 2012-11-26 | 2014-05-29 | Facebook. Inc. | On-demand session upgrade in a coordination service |
| CN104503882A (en) * | 2014-12-25 | 2015-04-08 | 北京京东尚科信息技术有限公司 | Container management method and device |
| US20150256481A1 (en) * | 2014-03-06 | 2015-09-10 | Jisto Inc. | Elastic Compute Cloud Based On Underutilized Server Resources Using A Distributed Container System |
| CN105187499A (en) * | 2015-08-07 | 2015-12-23 | 北京思特奇信息技术股份有限公司 | Distributed scheduling method and system based on zookeeper biplanar data architecture |
| CN105376303A (en) * | 2015-10-23 | 2016-03-02 | 深圳前海达闼云端智能科技有限公司 | Docker implementation system and communication method thereof |
| CN105389243A (en) * | 2015-10-26 | 2016-03-09 | 华为技术有限公司 | Container monitoring method and apparatus |
| CN105610972A (en) * | 2016-02-01 | 2016-05-25 | 中博信息技术研究院有限公司 | Clustered task dispatching system |
| CN105824614A (en) * | 2015-12-15 | 2016-08-03 | 广东亿迅科技有限公司 | Building method and device for distributed development environment based on Docker |
| CN105979009A (en) * | 2016-07-06 | 2016-09-28 | 乾云众创（北京）信息科技研究院有限公司 | Method for automatically balancing increased load of cloud application container |
-
2016
- 2016-12-29 CN CN201611241839.XA patent/CN106790595B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140149489A1 (en) * | 2012-11-26 | 2014-05-29 | Facebook. Inc. | On-demand session upgrade in a coordination service |
| US20150256481A1 (en) * | 2014-03-06 | 2015-09-10 | Jisto Inc. | Elastic Compute Cloud Based On Underutilized Server Resources Using A Distributed Container System |
| CN104503882A (en) * | 2014-12-25 | 2015-04-08 | 北京京东尚科信息技术有限公司 | Container management method and device |
| CN105187499A (en) * | 2015-08-07 | 2015-12-23 | 北京思特奇信息技术股份有限公司 | Distributed scheduling method and system based on zookeeper biplanar data architecture |
| CN105376303A (en) * | 2015-10-23 | 2016-03-02 | 深圳前海达闼云端智能科技有限公司 | Docker implementation system and communication method thereof |
| CN105389243A (en) * | 2015-10-26 | 2016-03-09 | 华为技术有限公司 | Container monitoring method and apparatus |
| CN105824614A (en) * | 2015-12-15 | 2016-08-03 | 广东亿迅科技有限公司 | Building method and device for distributed development environment based on Docker |
| CN105610972A (en) * | 2016-02-01 | 2016-05-25 | 中博信息技术研究院有限公司 | Clustered task dispatching system |
| CN105979009A (en) * | 2016-07-06 | 2016-09-28 | 乾云众创（北京）信息科技研究院有限公司 | Method for automatically balancing increased load of cloud application container |
Cited By (50)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107360018A (en) * | 2017-06-05 | 2017-11-17 | 小草数语（北京）科技有限公司 | Config update method and device |
| CN107248986A (en) * | 2017-06-08 | 2017-10-13 | 医惠科技有限公司 | A kind of service tray method |
| CN107294785A (en) * | 2017-07-11 | 2017-10-24 | 上海帝联信息科技股份有限公司 | The automatic deployment method and device, computer-readable recording medium of CDN node service |
| CN107294785B (en) * | 2017-07-11 | 2020-07-28 | 上海帝联信息科技股份有限公司 | Automatic deployment method and device for CDN node service and computer readable storage medium |
| CN109309693A (en) * | 2017-07-26 | 2019-02-05 | 财付通支付科技有限公司 | Services system, dispositions method and device, equipment and storage medium based on docker |
| CN109309693B (en) * | 2017-07-26 | 2022-04-29 | 财付通支付科技有限公司 | Multi-service system based on docker, deployment method, device, equipment and storage medium |
| CN107766052A (en) * | 2017-09-18 | 2018-03-06 | 网宿科技股份有限公司 | A kind of method and apparatus for building mirror image |
| CN107766052B (en) * | 2017-09-18 | 2020-09-25 | 网宿科技股份有限公司 | Method and device for constructing container mirror image |
| CN107635002A (en) * | 2017-09-21 | 2018-01-26 | 浪潮软件股份有限公司 | A kind of access method and device of containerization application |
| CN107885547A (en) * | 2017-11-08 | 2018-04-06 | 江苏国泰新点软件有限公司 | A kind of collocation method of application program, device, configuration equipment and storage medium |
| CN108021428A (en) * | 2017-12-05 | 2018-05-11 | 华迪计算机集团有限公司 | A kind of method and system that network target range is realized based on Docker |
| CN108446326B (en) * | 2018-02-11 | 2019-01-29 | 江苏微锐超算科技有限公司 | A kind of isomeric data management method and system based on container |
| CN108446326A (en) * | 2018-02-11 | 2018-08-24 | 江苏微锐超算科技有限公司 | A kind of isomeric data management method and system based on container |
| CN108551488A (en) * | 2018-05-03 | 2018-09-18 | 山东汇贸电子口岸有限公司 | Distributed container cluster load balancing method based on domestic CPU and OS |
| CN108616599A (en) * | 2018-05-11 | 2018-10-02 | 北京辰森世纪科技股份有限公司 | Application service registration, newer method and device |
| CN108616599B (en) * | 2018-05-11 | 2021-10-29 | 北京辰森世纪科技股份有限公司 | Method and device for registering and updating application service |
| CN108920153A (en) * | 2018-05-29 | 2018-11-30 | 华南理工大学 | A kind of Docker container dynamic dispatching method based on load estimation |
| CN108920153B (en) * | 2018-05-29 | 2022-04-22 | 华南理工大学 | Docker container dynamic scheduling method based on load prediction |
| CN110618821A (en) * | 2018-06-19 | 2019-12-27 | 普天信息技术有限公司 | Container cluster system based on Docker and rapid building method |
| CN108874549A (en) * | 2018-07-19 | 2018-11-23 | 北京百度网讯科技有限公司 | resource multiplexing method, device, terminal and computer readable storage medium |
| CN110912953A (en) * | 2018-09-17 | 2020-03-24 | 深圳市优必选科技有限公司 | File storage system and method |
| CN109120481A (en) * | 2018-09-27 | 2019-01-01 | 上海新炬网络信息技术股份有限公司 | Method based on Zabbix open source monitor component DCOS container and bosom part |
| CN109120481B (en) * | 2018-09-27 | 2021-06-04 | 上海新炬网络信息技术股份有限公司 | Method for monitoring DCOS container and internal middleware based on Zabbix open source component |
| CN109343963B (en) * | 2018-10-30 | 2021-12-07 | 杭州数梦工场科技有限公司 | Application access method and device for container cluster and related equipment |
| CN109343963A (en) * | 2018-10-30 | 2019-02-15 | 杭州数梦工场科技有限公司 | A kind of the application access method, apparatus and relevant device of container cluster |
| CN109451065A (en) * | 2018-12-26 | 2019-03-08 | 中电福富信息科技有限公司 | A kind of soft load balancing shunts automated system and its operation method |
| CN110134455A (en) * | 2019-04-12 | 2019-08-16 | 平安医疗健康管理股份有限公司 | A kind of application management system and method |
| CN110087107A (en) * | 2019-04-25 | 2019-08-02 | 视联动力信息技术股份有限公司 | A kind of method and view networked system of raising system self-adaption ability |
| CN110224860A (en) * | 2019-05-17 | 2019-09-10 | 平安科技（深圳）有限公司 | Load balancing application creation method, device, computer equipment and storage medium |
| CN110750592B (en) * | 2019-09-06 | 2023-10-20 | 中国平安财产保险股份有限公司 | Data synchronization method, device and terminal equipment |
| CN110750592A (en) * | 2019-09-06 | 2020-02-04 | 中国平安财产保险股份有限公司 | Data synchronization method, device and terminal equipment |
| CN110569056A (en) * | 2019-09-11 | 2019-12-13 | 北京奇艺世纪科技有限公司 | Method and device for updating rule service information |
| CN110830289A (en) * | 2019-10-21 | 2020-02-21 | 华中科技大学 | Container abnormity monitoring method and monitoring system |
| CN110830289B (en) * | 2019-10-21 | 2021-06-11 | 华中科技大学 | Container abnormity monitoring method and monitoring system |
| CN110764875A (en) * | 2019-10-25 | 2020-02-07 | 北京威晟艾德尔科技有限公司 | Docker container creating method based on competition mechanism |
| CN110830574A (en) * | 2019-11-05 | 2020-02-21 | 浪潮云信息技术有限公司 | Method for realizing intranet load balance based on docker container |
| CN111163122A (en) * | 2019-11-21 | 2020-05-15 | 江苏艾佳家居用品有限公司 | TCP configuration method based on Nginx self-research extension module and for automatically pulling service registration center |
| CN113127145B (en) * | 2020-01-15 | 2022-12-13 | 中移(苏州)软件技术有限公司 | Information processing method, device and storage medium |
| CN113127145A (en) * | 2020-01-15 | 2021-07-16 | 中移(苏州)软件技术有限公司 | Information processing method, device and storage medium |
| CN112099915A (en) * | 2020-09-07 | 2020-12-18 | 紫光云(南京)数字技术有限公司 | Soft load balancing dynamic issuing configuration method and system |
| CN112527319A (en) * | 2020-12-16 | 2021-03-19 | 浙江大学德清先进技术与产业研究院 | Management method of Docker-based remote sensing intelligent processing algorithm |
| CN112764825A (en) * | 2020-12-30 | 2021-05-07 | 望海康信(北京)科技股份公司 | Service integration system, corresponding device and storage medium |
| CN112764825B (en) * | 2020-12-30 | 2023-12-29 | 望海康信(北京)科技股份公司 | Service integration system, corresponding device and storage medium |
| CN113127435A (en) * | 2021-03-30 | 2021-07-16 | 杭州当虹科技股份有限公司 | Intelligent synchronization method and system for files of main and standby systems |
| CN113778613A (en) * | 2021-07-15 | 2021-12-10 | 上海浦东发展银行股份有限公司 | Unified management method for multi-data center double-stack container cloud platform |
| CN113778613B (en) * | 2021-07-15 | 2024-04-26 | 上海浦东发展银行股份有限公司 | Unified management method for dual-stack container cloud platform of multiple data centers |
| CN114640633A (en) * | 2022-03-29 | 2022-06-17 | 京东科技信息技术有限公司 | Load balancer, implementation method thereof, load balancing method and gateway system |
| WO2023184925A1 (en) * | 2022-03-29 | 2023-10-05 | 京东科技信息技术有限公司 | Load balancer and implementation method therefor, load balancing method, and gateway system |
| CN114640633B (en) * | 2022-03-29 | 2024-04-05 | 京东科技信息技术有限公司 | Load balancer, realization method thereof, load balancing method and gateway system |
| CN115190015A (en) * | 2022-07-12 | 2022-10-14 | 中国工商银行股份有限公司 | Soft load system configuration method and device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106790595B (en) | 2020-12-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106790595A (en) | A kind of Docker containers active load balancer and method | |
| US11706102B2 (en) | Dynamically deployable self configuring distributed network management system | |
| CN105245373B (en) | A kind of container cloud platform system is built and operation method | |
| CN104380693B (en) | System and method for dynamic routing in the cluster | |
| US10547693B2 (en) | Security device capability discovery and device selection | |
| JP4616159B2 (en) | Cluster system, load balancer, node transfer method, and node transfer program | |
| CN109274707A (en) | A kind of load dispatching method and device | |
| CN104811476B (en) | A kind of High Availabitity deployment implementation method of application-oriented service | |
| KR20050084802A (en) | Remote dynamic configuration of a web server to provide capacity on demand | |
| WO2013090699A1 (en) | Content delivery network | |
| CN108551488A (en) | Distributed container cluster load balancing method based on domestic CPU and OS | |
| CN113961303A (en) | Data center resource monitoring for managing message load balancing with reordering considerations | |
| CN112698838B (en) | Multi-cloud container deployment system and container deployment method thereof | |
| CN112134866A (en) | Service access control method, device, system and computer readable storage medium | |
| CN107707644A (en) | Processing method, device, storage medium, processor and the terminal of request message | |
| Lee et al. | High-performance software load balancer for cloud-native architecture | |
| US20240089352A1 (en) | Udp message distribution method, udp message distribution apparatus, electronic device and computer readable storage medium | |
| CN116633993B (en) | Cross-network micro-service calling method, device, equipment and storage medium | |
| US9804907B2 (en) | Remote procedure call for a distributed system | |
| CN115242882A (en) | Method and device for accessing k8s container environment based on transport layer route | |
| CN107395766A (en) | Decentralization communication system and implementation method based on HazelCast | |
| CN114615320A (en) | Service governance method, service governance device, electronic equipment and computer-readable storage medium | |
| CN115242791A (en) | Service platform access method, device, equipment and storage medium | |
| EP1130873A2 (en) | A method of setting up data communication with a communication means and furthermore program modules and means therefor | |
| CN115086176B (en) | System for realizing dynamic issuing of service administration strategy based on spring cloud micro-service technology |
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 |