CN111010454A - Load balancing method realized by dynamic routing architecture - Google Patents
Load balancing method realized by dynamic routing architecture Download PDFInfo
- Publication number
- CN111010454A CN111010454A CN201911407259.7A CN201911407259A CN111010454A CN 111010454 A CN111010454 A CN 111010454A CN 201911407259 A CN201911407259 A CN 201911407259A CN 111010454 A CN111010454 A CN 111010454A
- Authority
- CN
- China
- Prior art keywords
- application
- dynamic routing
- resource pool
- master
- application service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
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
- H04L67/1025—Dynamic adaptation of the criteria on which the server selection is based
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
- H04L43/103—Active monitoring, e.g. heartbeat, ping or trace-route with adaptive polling, i.e. dynamically adapting the polling rate
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
-
- 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/45—Network directories; Name-to-address mapping
- H04L61/4553—Object oriented directories, e.g. common object request broker architecture [CORBA] name server
-
- 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/59—Network arrangements, protocols or services for addressing or naming using proxies for addressing
-
- 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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1044—Group management mechanisms
Abstract
The invention discloses a load balancing method realized by a dynamic routing architecture, which comprises the following steps: the method comprises the following steps: the method comprises the steps that a cluster is built, cluster resources are divided, all application services are regarded as a resource pool, a plurality of application services in the resource pool are divided into a plurality of application service groups, and the application service groups are allocated to a master access category and a slave access category; setting a master-slave strategy for the application service; the method comprises the steps of adopting a dynamic routing framework, monitoring application services in a resource pool, and controlling the application services according to a master-slave strategy; the dynamic routing architecture provides an entry for accessing application services, and dynamically distributes user requests through a polling mechanism. The invention has the advantages that operation and maintenance personnel can allocate application service resources through the dynamic routing architecture without manually starting and stopping hot standby, and the operation is simple and is not easy to make mistakes. The application dynamic proxy can be implemented without changing the configuration of the server.
Description
Technical Field
The invention relates to a load balancing method realized by a dynamic routing architecture.
Background
Application service traffic has a size. No matter how much traffic is, and no matter how much access is, application services always crash for some unknown reasons, and once the system crashes, a certain loss is caused. To avoid excessive loss, the more important application services are generally structured into clusters. When one node application service in the cluster environment has a problem, only the service which is processed by the node application service is influenced, and other node applications are not influenced. However, in some application services with particularly large access volumes, when the access volume exceeds the cluster environment load, the whole application service cluster is crashed. For this situation, it is necessary to add a master-slave architecture on the basis of the cluster environment. When the primary application service cluster reaches a limit, the backup application service is started. Thereby relieving the pressure of the whole application service cluster.
Cluster architecture: the fault tolerance capability and the maximum access amount are multiplied relative to a single-node application service. But like single node applications, the cluster architecture also has its limits. The hardware configuration of the server is calculated during the erection process of the cluster architecture. The clustered environment is capable of satisfying normal business access under normal circumstances. However, once the second-killing activity is performed, the application service pressure is suddenly increased, and the whole cluster is easily crashed.
Cluster architecture plus master-slave architecture: compared with a cluster environment, the addition of the master-slave architecture application has a second life. When large-scale activity is carried out, the standby application service is started or the standby application is started when the application service is overloaded, so that the pressure of the large-scale activity on an application service cluster is relieved, and the application becomes relatively stable. However, this requires manual handling and human intervention. If the judgment is wrong or the standby application is not started in time, the application service still breaks down.
Disclosure of Invention
In order to solve the defects of the prior art, the invention provides a load balancing method realized by a dynamic routing architecture, which increases the fault tolerance rate of an application server. The maximum access amount of the application is increased, and the pressure of the sudden large access amount on the server is solved. And the problems of overload and breakdown of the application service are processed in time. And realizing dynamic load of the master-slave application service. The workload of the hot standby application service in expansion is simplified.
In order to achieve the above object, the present invention adopts the following technical solutions:
a load balancing method implemented in a dynamic routing architecture, comprising: the method comprises the following steps:
the method comprises the steps that a cluster is built, cluster resources are divided, all application services are regarded as a resource pool, a plurality of application services in the resource pool are divided into a plurality of application service groups, and the application service groups are allocated to a master access category and a slave access category;
setting a master-slave strategy for the application service;
the method comprises the steps of adopting a dynamic routing framework, monitoring application services in a resource pool, and controlling the application services according to a master-slave strategy;
the dynamic routing architecture provides an entry for accessing application services, and dynamically distributes user requests through a polling mechanism.
Further, the master-slave strategy comprises:
setting a standby application starting condition;
the standby application disables the condition setting.
Further, the master-slave strategy further comprises:
enabling application group number settings in the standby application;
starting the standby application at regular time;
the timed deactivation application is adjusted to a standby application.
Further, the method for monitoring the application service in the resource pool by adopting the dynamic routing architecture and controlling the application service according to the master-slave strategy comprises the following steps:
acquiring a master-slave strategy;
detecting an application service;
judging whether an application service stop condition is met according to a master-slave strategy;
if the judgment result is yes, stopping part of application services according to the master-slave strategy;
the set of routing addresses is reloaded.
Further, when the dynamic routing framework is initialized, a listener is created for monitoring whether the configuration is changed; and if the change occurs, refreshing the resource pool information and the configuration information in the local static variable and the redis.
Further, the resource pool generates a new version number during modification, and after the resource pool is successfully saved, the new version number and the resource pool information are loaded into a local static variable and a redis.
Further, by comparing the version number in the obtained static variable of the body with the version number in the redis, whether the resource pools in the local static variable and the redis are latest is judged; if the version number in the static variable of the body is smaller than the version number stored in the redis, inquiring and refreshing the resource pool information in the local static variable from the database; and if the version number stored in the redis is smaller than the static variable version number of the body, updating the redis.
Further, the resource pool information is stored in a local static variable and a redis; the poller acquires a resource with the least access amount from the redis each time a new request comes, and automatically increases the access amount 1 time after the acquisition is completed.
Further, the use of distributed locks avoids concurrency issues when acquiring application resources from the pollers and increasing access times.
Further, calculating an application service address of the agent through the poller; intercepting actual application access addresses and request parameters through a repeater; then, the application service address, the application access address and the request parameter are spliced into a complete request in the repeater; and finally, the request is forwarded to the actual application service through the repeater.
The invention has the advantages that operation and maintenance personnel can allocate application service resources through the dynamic routing architecture without manually starting and stopping hot standby, and the operation is simple and is not easy to make mistakes. The application dynamic proxy can be implemented without changing the configuration of the server.
The application resources may be dynamically allocated based on the results of the performance analysis of the application server.
The access of the service condition is provided, and the application resource can be dynamically allocated according to the service information of the application service.
The starting and stopping of the application service are convenient and quick, and a timing function is further provided.
The hot standby application service is convenient to expand.
Drawings
FIG. 1 is a schematic diagram of cluster resource partitioning of a load balancing method implemented by a dynamic routing architecture according to the present invention;
FIG. 2 is a flow diagram of monitoring and controlling application services for the load balancing methodology implemented in the dynamic routing architecture of FIG. 1;
fig. 3 is a flow chart of a dynamic proxy of a load balancing method implemented in a dynamic routing architecture according to the present invention.
Detailed Description
The invention is described in detail below with reference to the figures and the embodiments.
As shown in fig. 1 to 3, a load balancing method implemented in a dynamic routing architecture includes: the method comprises the following steps:
the method comprises the steps that a cluster is built, cluster resources are divided, all application services are regarded as a resource pool, a plurality of application services in the resource pool are divided into a plurality of application service groups, and the application service groups are allocated to a master access category and a slave access category;
setting a master-slave strategy for the application service;
the method comprises the steps of adopting a dynamic routing framework, monitoring application services in a resource pool, and controlling the application services according to a master-slave strategy;
the dynamic routing architecture provides an entry for accessing application services, and dynamically distributes user requests through a polling mechanism.
The processing efficiency of the system can be improved and the agent speed can be improved by adopting the clustering deployment. The agent work can be efficiently completed even when the access amount is too large.
Referring to fig. 1, all application service resources are integrated. All application services are treated as one resource pool. The application groups are then divided according to the actual situation, i.e. several applications are considered as a whole. Thus, the application services in the resource pool are divided into a plurality of application service groups. Next, the groups of application services are allocated according to the access volume and resource consumption of the production environment. The application groups are divided into A, B, C, D, E, 5 application groups as shown. Of these application groups, A, B is then assigned to the primary access category and C, D, E is assigned to the backup access category.
The master-slave strategy is adopted to manage and allocate the application service resource pool in a strategy manner. The resource pool resources (dynamic proxy) can be dynamically allocated according to the running condition of the server and the performance consumption condition of the server. In addition, the access of the service condition setting is provided, and the application service can set a master-slave strategy according to service factors such as the activity starting time, the activity ending time, the service volume, the access volume and the like.
Specifically, the method is described. The master-slave strategy comprises:
setting the starting condition of the standby application (the starting condition comprises alarm, overload, service condition and the like);
standby application deactivation condition settings (traffic conditions, such as end of activity, traffic volume, etc.);
enabling application group number settings in the standby application;
starting the standby application at regular time;
the timed deactivation application is adjusted to a standby application.
As a specific implementation manner, the method for monitoring the application service in the resource pool by adopting the dynamic routing architecture and controlling the application service according to the master-slave strategy comprises the following steps:
acquiring a master-slave strategy;
detecting an application service;
judging whether an application service stop condition is met according to a master-slave strategy;
if the judgment result is yes, stopping part of application services according to the master-slave strategy;
the set of routing addresses is reloaded.
In a production environment, a dynamic routing architecture requires real-time monitoring of cluster resources. The method comprises the steps of detecting the memory and the cpu of the server (remotely calling the linux command to acquire the running condition, analyzing and analyzing of the server). Therefore, a monitoring thread needs to be started to monitor and analyze the cluster resource operation condition all the time. And judging whether conditions for starting and stopping the resources in the resource pool are met or not according to the master-slave access strategy setting. The operation of the snoop thread also includes flushing resource pool information in the cache. Once the master-slave access policy changes, the listening thread needs to respond immediately. In the case of application alarm, the standby application service needs to be immediately enabled, which requires that the enabling policy of the standby application service is set in advance in the master-slave policy setting. When the service alarm problem is met, the problem is not passively processed, but is actively expanded, so that the application fault is prevented from bringing larger loss. Some application services may need to be disabled after the problem is resolved or the amount of access returns to normal. Part of application services can be manually set as standby applications, and some application services can be automatically set as inactive when the application services are normally accessed through master-slave policy setting. In addition, the dynamic routing architecture also provides monitoring of service processing conditions. The application service only needs to provide an interface of the service processing condition, the dynamic routing framework can call a remote interface in the monitoring thread to read the service processing condition, and the standby application is started or stopped when a specific condition is met.
Limited resources (application service clusters) are managed in the form of resource pools. And grouping and classifying the resources in the resource pool. And allocating the standby resources in the master-slave access strategy, and setting the starting and stopping conditions of the standby application. This is a preparation before the dynamic routing architecture is used. After the above work is completed, the dynamic routing framework provides an entrance for accessing the application service, and dynamically distributes the user request through a polling mechanism.
As a preferred embodiment, when the dynamic routing framework is initialized, a listener is created for monitoring whether the configuration is changed; and if the change occurs, refreshing the resource pool information and the configuration information in the local static variable and the redis.
In an actual production environment, racking and racking are very normal things. The access volume of the application system also has a certain volatility. It is normal to temporarily adjust application resources, which requires that the configuration be validated immediately after modification. Since the configuration is stored in the cache, the dynamic routing framework creates a listener at initialization in order to enable the modified configuration to take effect immediately. The listener is used to listen for changes in settings. If the change occurs, the resource pool information and configuration information in the local static variables and the redis are refreshed.
In a preferred embodiment, the resource pool generates a new version number during modification, and after successful saving, the new version number is loaded into the local static variable and the redis together with the resource pool information. Therefore, loading and updating of resource pool information in the redis are facilitated. Judging whether the resource pools in the local static variables and the redis are latest or not by comparing the version number in the obtained static variables with the version number in the redis; if the version number in the static variable of the body is smaller than the version number stored in the redis, inquiring and refreshing the resource pool information in the local static variable from the database; and if the version number stored in the redis is smaller than the static variable version number of the body, updating the redis.
The update operation may occur concurrently in a production environment. It is necessary to use distributed locks before updating the resource pool to prevent other nodes from updating at the same time during the update of redis. The same is true when the resource pool information changes, and when the listener finds that the resource pool version in the local cache is inconsistent with the version stored in the redis in the polling process, the resource pool information in the local static variable or the redis needs to be refreshed.
The core of the dynamic proxy consists of a poller and a repeater. The resource pool information is stored in local static variables and redis; the poller acquires a resource with the least access amount from the redis each time a new request comes, and automatically increases the access amount 1 time after the acquisition is completed. The use of distributed locks avoids concurrency issues when acquiring application resources from the pollers and increasing access times. Since the function of the poller is to acquire an application service resource. The acquired data needs to be provided for the repeater to use, so that excessive logic processing cannot be carried out. Where a distributed lock is used, the response time needs to be set to within 1 second to avoid impacting access to the application service.
As a specific implementation mode, calculating an application service address of the agent through a poller; intercepting actual application access addresses and request parameters through a repeater; then, the application service address, the application access address and the request parameter are spliced into a complete request in the repeater; and finally, the request is forwarded to the actual application service through the repeater.
The foregoing illustrates and describes the principles, general features, and advantages of the present invention. It should be understood by those skilled in the art that the above embodiments do not limit the present invention in any way, and all technical solutions obtained by using equivalent alternatives or equivalent variations fall within the scope of the present invention.
Claims (10)
1. A method for load balancing implemented in a dynamic routing architecture, comprising: the method comprises the following steps:
the method comprises the steps that a cluster is built, cluster resources are divided, all application services are regarded as a resource pool, a plurality of application services in the resource pool are divided into a plurality of application service groups, and the application service groups are allocated to a master access category and a slave access category;
setting a master-slave strategy for the application service;
the method comprises the steps of adopting a dynamic routing framework, monitoring application services in a resource pool, and controlling the application services according to a master-slave strategy;
the dynamic routing architecture provides an entry for accessing application services, and dynamically distributes user requests through a polling mechanism.
2. The method of claim 1, wherein the load balancing is performed by a dynamic routing architecture,
the master-slave strategy comprises:
setting a standby application starting condition;
the standby application disables the condition setting.
3. The method of claim 2, wherein the load balancing is performed by a dynamic routing architecture,
the master-slave strategy further comprises:
enabling application group number settings in the standby application;
starting the standby application at regular time;
the timed deactivation application is adjusted to a standby application.
4. The method of claim 1, wherein the load balancing is performed by a dynamic routing architecture,
the method for monitoring the application service in the resource pool by adopting the dynamic routing architecture and controlling the application service according to the master-slave strategy comprises the following steps:
acquiring a master-slave strategy;
detecting an application service;
judging whether an application service stop condition is met according to a master-slave strategy;
if the judgment result is yes, stopping part of application services according to the master-slave strategy;
the set of routing addresses is reloaded.
5. The method of claim 1, wherein the load balancing is performed by a dynamic routing architecture,
when the dynamic routing framework is initialized, a listener is established for monitoring whether the configuration is changed; and if the change occurs, refreshing the resource pool information and the configuration information in the local static variable and the redis.
6. The method of claim 1, wherein the load balancing is performed by a dynamic routing architecture,
and the resource pool generates a new version number during modification, and after the resource pool is successfully stored, the new version number and the resource pool information are loaded into a local static variable and a redis.
7. The method for load balancing implemented in a dynamic routing architecture of claim 6,
judging whether the resource pools in the local static variables and the redis are latest or not by comparing the version number in the obtained static variables with the version number in the redis; if the version number in the static variable of the body is smaller than the version number stored in the redis, inquiring and refreshing the resource pool information in the local static variable from the database; and if the version number stored in the redis is smaller than the static variable version number of the body, updating the redis.
8. The method of claim 1, wherein the load balancing is performed by a dynamic routing architecture,
the resource pool information is stored in local static variables and redis; the poller acquires a resource with the least access amount from the redis each time a new request comes, and automatically increases the access amount 1 time after the acquisition is completed.
9. The method of claim 8, wherein the load balancing is performed by a dynamic routing architecture,
the use of distributed locks avoids concurrency issues when acquiring application resources from the pollers and increasing access times.
10. The method of claim 1, wherein the load balancing is performed by a dynamic routing architecture,
calculating an application service address of the agent through a poller; intercepting actual application access addresses and request parameters through a repeater; then, the application service address, the application access address and the request parameter are spliced into a complete request in the repeater; and finally, the request is forwarded to the actual application service through the repeater.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911407259.7A CN111010454A (en) | 2019-12-31 | 2019-12-31 | Load balancing method realized by dynamic routing architecture |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911407259.7A CN111010454A (en) | 2019-12-31 | 2019-12-31 | Load balancing method realized by dynamic routing architecture |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111010454A true CN111010454A (en) | 2020-04-14 |
Family
ID=70119804
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911407259.7A Pending CN111010454A (en) | 2019-12-31 | 2019-12-31 | Load balancing method realized by dynamic routing architecture |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111010454A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111787063A (en) * | 2020-06-02 | 2020-10-16 | 深圳前海移联科技有限公司 | Channel route management method for business service |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6195680B1 (en) * | 1998-07-23 | 2001-02-27 | International Business Machines Corporation | Client-based dynamic switching of streaming servers for fault-tolerance and load balancing |
| CN106375342A (en) * | 2016-10-21 | 2017-02-01 | 用友网络科技股份有限公司 | Zookeeper-technology-based system cluster method and system |
| CN106599085A (en) * | 2016-11-25 | 2017-04-26 | 努比亚技术有限公司 | Automatic refreshing method and device for web system configuration file |
| CN107145393A (en) * | 2017-04-27 | 2017-09-08 | 努比亚技术有限公司 | A kind of load regulation method, equipment and computer-readable recording medium |
| CN108494868A (en) * | 2018-03-30 | 2018-09-04 | 三盟科技股份有限公司 | A kind of load-balancing method under the operation system based on cloud and system |
| CN109302498A (en) * | 2018-11-29 | 2019-02-01 | 杭州迪普科技股份有限公司 | A kind of network resource access method and device |
| CN109407980A (en) * | 2018-09-29 | 2019-03-01 | 武汉极意网络科技有限公司 | Data-storage system based on Redis cluster |
| CN110502580A (en) * | 2019-08-26 | 2019-11-26 | 江苏华库数据技术有限公司 | A kind of method of clustered database system resource control scheduling |
-
2019
- 2019-12-31 CN CN201911407259.7A patent/CN111010454A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6195680B1 (en) * | 1998-07-23 | 2001-02-27 | International Business Machines Corporation | Client-based dynamic switching of streaming servers for fault-tolerance and load balancing |
| CN106375342A (en) * | 2016-10-21 | 2017-02-01 | 用友网络科技股份有限公司 | Zookeeper-technology-based system cluster method and system |
| CN106599085A (en) * | 2016-11-25 | 2017-04-26 | 努比亚技术有限公司 | Automatic refreshing method and device for web system configuration file |
| CN107145393A (en) * | 2017-04-27 | 2017-09-08 | 努比亚技术有限公司 | A kind of load regulation method, equipment and computer-readable recording medium |
| CN108494868A (en) * | 2018-03-30 | 2018-09-04 | 三盟科技股份有限公司 | A kind of load-balancing method under the operation system based on cloud and system |
| CN109407980A (en) * | 2018-09-29 | 2019-03-01 | 武汉极意网络科技有限公司 | Data-storage system based on Redis cluster |
| CN109302498A (en) * | 2018-11-29 | 2019-02-01 | 杭州迪普科技股份有限公司 | A kind of network resource access method and device |
| CN110502580A (en) * | 2019-08-26 | 2019-11-26 | 江苏华库数据技术有限公司 | A kind of method of clustered database system resource control scheduling |
Non-Patent Citations (1)
| Title |
|---|
| 蒲宇: "《主机应用灾备系统的研究与实现》", 《中国优秀硕士学位论文全文数据库-信息科技辑》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111787063A (en) * | 2020-06-02 | 2020-10-16 | 深圳前海移联科技有限公司 | Channel route management method for business service |
| CN111787063B (en) * | 2020-06-02 | 2023-05-16 | 深圳前海移联科技有限公司 | Channel route management method for business service |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3335120B1 (en) | Method and system for resource scheduling | |
| US9229754B2 (en) | Dynamic scaling of management infrastructure in virtual environments | |
| CN110941481A (en) | Resource scheduling method, device and system | |
| CN108132837B (en) | Distributed cluster scheduling system and method | |
| CN108306955B (en) | Large-scale interconnection clustering method for vehicle-mounted terminals | |
| CN109857558A (en) | A kind of data flow processing method and system | |
| CN109358816B (en) | Flow control method and device of distributed storage system | |
| CN112104486A (en) | Kubernetes container-based network endpoint slicing method and system | |
| CN103593242A (en) | Resource sharing control system based on Yarn frame | |
| CN110990200B (en) | Flow switching method and device based on multiple active data centers | |
| CN110912972B (en) | Service processing method, system, electronic equipment and readable storage medium | |
| CN107453932B (en) | Distributed storage system management method and device | |
| WO2023115931A1 (en) | Big-data component parameter adjustment method and apparatus, and electronic device and storage medium | |
| CN113204353B (en) | Big data platform assembly deployment method and device | |
| EP4057139A1 (en) | Pod deployment method and device | |
| CN111858190B (en) | Method and system for improving availability of cluster | |
| CN114461668A (en) | MYSQL database query method and device based on thread pool | |
| CN114629883B (en) | Service request processing method and device, electronic equipment and storage medium | |
| CN111010454A (en) | Load balancing method realized by dynamic routing architecture | |
| CN109992415B (en) | Container dispatching method and dispatching system | |
| CN114531373A (en) | Node state detection method, node state detection device, equipment and medium | |
| WO2021139174A1 (en) | Faas distributed computing method and apparatus | |
| CN110865919A (en) | Java process-based monitoring method and device and computer equipment | |
| CN106453656B (en) | Cluster host selection method and device | |
| CN111767122A (en) | Distributed task scheduling management method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200414 |