CN113905048A - Method and device for scheduling engine instance by cluster manager and computer equipment - Google Patents
Method and device for scheduling engine instance by cluster manager and computer equipment Download PDFInfo
- Publication number
- CN113905048A CN113905048A CN202111162019.2A CN202111162019A CN113905048A CN 113905048 A CN113905048 A CN 113905048A CN 202111162019 A CN202111162019 A CN 202111162019A CN 113905048 A CN113905048 A CN 113905048A
- Authority
- CN
- China
- Prior art keywords
- engine
- message
- instance
- engine instance
- endpoint
- 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
- 238000000034 method Methods 0.000 title claims abstract description 43
- 238000012545 processing Methods 0.000 claims abstract description 29
- 230000003044 adaptive effect Effects 0.000 claims abstract description 7
- 238000004590 computer program Methods 0.000 claims description 10
- 230000001360 synchronised effect Effects 0.000 claims description 7
- 238000012423 maintenance Methods 0.000 claims description 3
- 230000008569 process Effects 0.000 description 13
- 230000003993 interaction Effects 0.000 description 6
- 230000010354 integration Effects 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 210000001503 joint Anatomy 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000002354 daily effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Hardware Redundancy (AREA)
Abstract
The embodiment of the invention discloses a method, a device and computer equipment for scheduling an engine instance by a cluster manager, which not only achieve the aim of load balancing of engine instance calling, but also ensure that messages are effectively processed and really play the role of a cluster. The cluster manager schedules engine instances that are only accessible by the cluster manager, the method comprising: receiving a message, wherein the message comprises Token information of an endpoint; identifying the endpoint identity according to the Token information, authenticating the endpoint identity, and judging whether the endpoint has the right to send the message; judging the available state of the current engine for the message passing the authentication; if an available engine exists at present, preliminarily distributing an adaptive engine instance according to the message type; and selecting an engine instance according to a load balancing algorithm, and sending the message to the engine instance for processing.
Description
Technical Field
The invention relates to the technical field of computer networks, in particular to a method for scheduling an engine instance by a cluster manager.
Background
For the information management system of enterprises and public institutions in the industries of medical treatment, education, military industry, real estate and the like, the number of involved internal and external business systems is usually many (possibly hundreds), and the interactive message amount among daily systems can reach tens of millions.
In order to solve the problem of point-to-point interaction of the service systems, an online information integration platform is considered, the service systems are only in butt joint with the integration platform as end points, the integration platform completes the butt joint process with other service systems, decoupling and interaction configurability of interaction between the service systems are realized, and tracking monitoring and alarming of the interaction process between the service systems are realized.
The integrated platform is used as a load central point, and a clustering operation mode is hopefully adopted to improve the reliability and the processing speed and avoid the large-range influence caused by single-point failure. The cluster manager needs to effectively schedule a plurality of running processing instances (hereinafter referred to as engine instances) in the cluster running process, and needs to not only achieve the purpose of load balancing of engine instance calling, but also ensure that messages are effectively processed, thereby really playing the role of a cluster. Currently, no mechanism has been proposed in the prior art for a cluster manager to schedule engine instances.
Disclosure of Invention
The embodiment of the invention provides a method and a device for scheduling an engine instance by a cluster manager and computer equipment, aiming at achieving the aim of load balancing of engine instance calling, ensuring that messages are effectively processed and really playing the role of a cluster.
In order to achieve the above object, the embodiments of the present invention provide the following technical solutions:
in a first aspect, a method for a cluster manager to schedule an engine instance, said engine instance being accessible only to the cluster manager, is characterized in that the method comprises:
receiving a message, wherein the message comprises Token information of an endpoint;
identifying the endpoint identity according to the Token information, authenticating the endpoint identity, and judging whether the endpoint has the right to send the message;
judging the available state of the current engine for the message passing the authentication;
if an available engine exists at present, preliminarily distributing an adaptive engine instance according to the message type;
and selecting an engine instance according to a load balancing algorithm, and sending the message to the engine instance for processing.
Optionally, the authentication of the identity specifically determines whether the endpoint has the right to send the message according to the IP address and the access right of the endpoint.
Optionally, the engine available state is marked in the following way:
judging whether the address of the engine instance can be accessed, if the access is overtime, the available state of the engine is 0;
judging whether the engine instance can be connected with the log database, if the engine instance cannot be connected with the log database, the available state of the engine is equal to 0;
judging an engine instance heartbeat value, and if the heartbeat value is equal to 0, setting the engine available state to be 0;
otherwise, the engine available state is 1, indicating that there is currently an available engine.
Optionally, when there is an available engine currently and before the engine adapted according to the message type is allocated, it is determined whether there is a message-oriented processing engine instance in the attribute of the message, and when there is the attribute, the message is directly sent to the specified engine instance for processing.
Optionally, the engine that is adapted according to the message type assignment specifically includes: if the message type is synchronous message, sending the message to a conventional engine or super engine; if the message type is an asynchronous message, the message is sent to either the MQ private engine or the super engine.
Optionally, the selecting an engine instance according to a load balancing algorithm specifically includes: and sequentially judging the running state of each engine instance according to a load balancing algorithm: whether the engine instance is in a maintenance state, whether the engine instance has reached a full load running state; if the above conditions are met, sending the message to the engine instance for processing; and if the unsatisfied condition exists, judging the running states of other engine instances in the range, and sending the message to the engine instances meeting the condition for processing.
Optionally, the receiving message may specifically be a message sent by a direct receiving endpoint, or may also be a message distributed via a unified interface Nginx.
In a second aspect, an apparatus for a cluster manager scheduler engine instance is characterized by comprising:
the message receiving module is used for receiving a message, wherein the message comprises Token information of an endpoint;
the authentication module is used for identifying the endpoint identity according to the Token information, authenticating the endpoint identity and judging whether the endpoint has the right to send the message;
the engine state identification module is used for judging the available state of the current engine under the condition that the message authentication is passed;
the engine matching module is used for preliminarily distributing the adaptive engine instances according to the message types under the condition that the available engines exist at present;
and the load balancing processing module is used for selecting an engine instance according to a load balancing algorithm and sending the message to the engine instance for processing.
In a third aspect, a computer device for a cluster manager comprises a memory and a processor, wherein the memory stores a computer program, and is characterized in that the processor implements the steps of the method when executing the computer program.
In a fourth aspect, a computer-readable storage medium, on which a computer program is stored, is characterized in that the computer program realizes the steps of the above-mentioned method when being executed by a processor.
The invention has at least the following beneficial effects:
the invention finally determines the running state of the engine instance to process the message by the endpoint identity authentication, the judgment of the engine real available state, the adaptation of the engine instance type and the algorithm of load balancing according to the running state of the engine instance in turn, thereby not only achieving the aim of the engine instance calling load balancing, but also ensuring that the message is effectively processed and really playing the role of the cluster.
Drawings
In order to more clearly illustrate the prior art and the present invention, the drawings which are needed to be used in the description of the prior art and the embodiments of the present invention will be briefly described. It should be apparent that the drawings in the following description are merely exemplary, and that other drawings may be derived from the provided drawings by those of ordinary skill in the art without inventive effort.
Fig. 1 is a schematic diagram of a cluster deployment architecture according to an embodiment of the present invention.
FIG. 2 is a flowchart illustrating a method for a cluster manager to schedule an instance of an engine according to an embodiment of the present invention.
FIG. 3 is a diagram illustrating the query and update engine availability status, according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The method for scheduling an engine instance by a cluster manager according to an embodiment of the present application is applicable to the cluster deployment architecture shown in fig. 1. From the aspect of deployment architecture, a third party Nginx realizes centralized access as an optional item, and an endpoint sends a message to the Nginx, and the Nginx distributes the message to the manager. The centralization can be carried out, the end points send messages to any cluster manager in a clustering mode, the processing performance is improved, single-point holes do not exist, the reliability of platform operation is improved, and the overall operation cannot be influenced by the fault of a certain server.
Endpoints can only access the cluster manager and engine instances can only be accessed by the cluster manager.
From the perspective of the engine instance, the types of the engine instance can be subdivided and can be respectively deployed, the working efficiency of the engine can be fully exerted, wherein the conventional type engine can be used for only processing synchronous messages, the MQ special engine can be used for only processing asynchronous messages, and the hybrid engine can process both synchronous messages and asynchronous messages. The cluster manager can determine which type of engine to invoke based on the type of message sent.
Table 1 two-dimensional table for call engine instance judgment mechanism
In one embodiment, as shown in FIG. 2, there is provided a method for a cluster manager to schedule an engine instance, comprising the steps of:
s1: receiving a message, wherein the message comprises Token information of an endpoint;
s2: identifying the endpoint identity according to the Token information, authenticating the endpoint identity, and judging whether the endpoint has the right to send the message;
s3: judging the available state of the current engine for the message passing the authentication;
s4: if an available engine exists at present, preliminarily distributing an adaptive engine instance according to the message type;
s5: and selecting an engine instance according to a load balancing algorithm, and sending the message to the engine instance for processing.
Before S4, it may also be determined whether there is a message-oriented processing engine instance in the attribute of the message, and when there is the attribute, the message is directly sent to the specified engine instance for processing.
Therefore, the running state of the engine instance is sequentially determined by the endpoint identity authentication, the judgment of the engine real available state, the adaptation of the engine instance type and the algorithm of load balancing to finally determine the engine instance to process the message, so that the aim of invoking load balancing by the engine instance can be achieved, the message can be guaranteed to be effectively processed, and the cluster effect is really exerted.
In one embodiment, the access logic of the cluster manager to the engine instance is specified as follows:
judging the priority level 1: cluster manager authentication prior to engine real availability status determination
The cluster manager is responsible for receiving a message, wherein the message contains Token information of a sender (hereinafter referred to as an endpoint), and the cluster manager can identify the identity of the endpoint according to the Token information and authenticate the identity (including the IP address and the access authority of the endpoint). That is, the message contains the code of the message to send, and the cluster manager can make a determination as to whether the endpoint is authorized to send the message.
Judging the priority 2: engine instance availability status priority is higher than engine instance orientation dimension
As shown in fig. 3, after the message passes the authentication of the cluster manager, the cluster manager searches for an engine instance with an engine available status of 1, and the cluster manager only calls the engine instance with the engine available status of 1.
Judgment of engine available state:
(1) if the engine instance address is accessible, access timeout, engine available status 0
(2) If the engine instance can be connected with the log database, if the log database cannot be connected, the available state of the engine is 0
(3) Engine instance heartbeat value, heartbeat value is 0, engine available state is 0
For item (1), the cluster manager directly determines that for items (2) and (3), the cluster manager can implement the obtaining of the status value through the getProcessorStatus method provided by the engine instance.
Judging the priority 3: engine instance orientation dimension having a higher priority than engine instance type dimension
The cluster pipe cluster device finds the engine instance with the engine available state equal to 1, and then judges whether a message oriented processing engine instance (optional item) exists in the attribute of the message, and when the attribute exists, the message can only be sent to the specified engine instance for processing.
Judging the priority 4: engine instance type dimension priority over engine instance running state
The cluster manager determines the type of the message, and if the message type is synchronous, the cluster manager needs to send the message to the regular engine or super engine (or called hybrid engine), and if the message type is asynchronous, the rights manager needs to send the message to the MQ special engine or super engine (or called hybrid engine).
The number of the engine instances can be configured, theoretically, there is no limitation on the number, and the engine type can be set for each engine instance.
Judging the priority 5: the engine instance running state determines which engine instance the final manager can access
On the basis of the previous judgment steps, the cluster manager also needs to sequentially judge the running state of the engine instance according to a load balancing algorithm, determine whether the engine instance is in a maintenance state, determine whether the engine instance has reached a full-load running state, if the engine instance does not meet the full-load running state, the cluster manager needs to determine the running states of other engine instances within the range, and if the engine instance meets the conditions, the cluster manager sends a message to the engine instance for processing.
Engine instance load state mechanism: when the cluster manager sends the cluster manager to the engine instance, the engine instance adds judgment before executing the integration project, and the specific algorithm is as follows:
number of tokens available for an engine instance not to be exceeded (parameter set number)
Can process messages
The number of possible Token instances for the engine is exceeded (parameter set number)
Returning failure information, the rights manager attempts to access another engine instance
The Cluster manager cycles through all regular engines or super engines a set number of times (PARA _ TOKEN _ RETRY _ NUM), still over-limit
Cluster manager returns information to caller (in a format like 310 before)
077: the engine instance is busy, please try again later
·PARA_TOKEN_IF_USE＝1
One message request, engine instance determines TOKEN consumption +1> maximum load parameter
Failure to stand
TOKEN consumption number +1
Allow request
After the message is executed, the TOKEN consumption number is equal to TOKEN consumption number-1, and the minimum value is 0
Is established
Reject the request
For the purpose of achieving the load balancing of the engine instance call, and ensuring that the message is effectively processed, the function of the cluster is really exerted, the embodiment makes full consideration, for example:
if the engine instance is in an unavailable state, the cluster manager cannot process the engine instance even if the engine instance is sent to the cluster manager, and interaction between the business systems is influenced.
If the engine instance is busy, the cluster manager needs to wait even if sending to the engine instance, which affects the interaction between the business systems.
Taking an enterprise and public institution information management system in the medical industry as an example, based on the scheme provided by the embodiment, the engine examples can be deployed in a targeted manner according to the actual scene of a hospital by classifying the engine examples:
if the hospital is large in scale, more synchronous messages are generated every day, the concurrency is large, a plurality of high-configuration servers can be used for deploying conventional engines to specially process the synchronous messages, and a plurality of low-configuration servers can be used for deploying MQ special engines to specially process the asynchronous messages, so that the server resources can be utilized to the maximum extent, and the message processing efficiency can be improved.
If the hospital is small in size and the message size is not large, a plurality of hybrid engines can be deployed, so that the hardware investment cost of the hospital can be saved.
In one embodiment, there is also provided an apparatus for a cluster manager scheduler engine instance, comprising the program modules to:
the message receiving module is used for receiving a message, wherein the message comprises Token information of an endpoint;
the authentication module is used for identifying the endpoint identity according to the Token information, authenticating the endpoint identity and judging whether the endpoint has the right to send the message;
the engine state identification module is used for judging the available state of the current engine under the condition that the message authentication is passed;
the engine matching module is used for preliminarily distributing the adaptive engine instances according to the message types under the condition that the available engines exist at present;
and the load balancing processing module is used for selecting an engine instance according to a load balancing algorithm and sending the message to the engine instance for processing.
For the specific limitations of the above apparatus, reference may be made to the above limitations of the method for the cluster manager scheduling engine example, and details are not described here. The modules in the above device can be all realized by software. The modules can be stored in a memory of a computer device in a software form, so that a processor can call and execute the corresponding operations of the modules.
In one embodiment, a computer device applied to a cluster manager is further provided, and includes a memory and a processor, where the memory stores a computer program, and all or part of the procedures in the method of the above embodiment are involved.
In one embodiment, a computer-readable storage medium having a computer program stored thereon is provided, which relates to all or part of the processes of the method of the above embodiments.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include at least one of non-volatile and volatile memory. Non-volatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. A method for a cluster manager to schedule an engine instance, the engine instance being accessible only by the cluster manager, the method comprising:
receiving a message, wherein the message comprises Token information of an endpoint;
identifying the endpoint identity according to the Token information, authenticating the endpoint identity, and judging whether the endpoint has the right to send the message;
judging the available state of the current engine for the message passing the authentication;
if an available engine exists at present, preliminarily distributing an adaptive engine instance according to the message type;
and selecting an engine instance according to a load balancing algorithm, and sending the message to the engine instance for processing.
2. The method of claim 1, wherein authenticating the identity is based on the IP address and access rights of the endpoint to determine whether the endpoint is authorized to send the message.
3. The method of claim 1, wherein the engine available state is marked as follows:
judging whether the address of the engine instance can be accessed, if the access is overtime, the available state of the engine is 0;
judging whether the engine instance can be connected with the log database, if the engine instance cannot be connected with the log database, the available state of the engine is equal to 0;
judging an engine instance heartbeat value, and if the heartbeat value is equal to 0, setting the engine available state to be 0;
otherwise, the engine available state is 1, indicating that there is currently an available engine.
4. The method of claim 1, wherein when there is an available engine currently and before the engine adapted according to the message type is assigned, it is determined whether there is a message-oriented processing engine instance in the attribute of the message, and when there is the attribute, the message is directly sent to the specified engine instance for processing.
5. The method according to claim 1, wherein said assigning the adapted engines according to message type is in particular: if the message type is synchronous message, sending the message to a conventional engine or super engine; if the message type is an asynchronous message, the message is sent to either the MQ private engine or the super engine.
6. The method of claim 1, wherein the engine instance is selected according to a load balancing algorithm, specifically:
and sequentially judging the running state of each engine instance according to a load balancing algorithm: whether the engine instance is in a maintenance state, whether the engine instance has reached a full load running state; if the above conditions are met, sending the message to the engine instance for processing; and if the unsatisfied condition exists, judging the running states of other engine instances in the range, and sending the message to the engine instances meeting the condition for processing.
7. Method according to claim 1, characterized in that said receiving a message, in particular a message sent directly by an endpoint, or a message distributed via a unified interface Nginx is received.
8. An apparatus for a cluster manager to schedule an engine instance, comprising:
the message receiving module is used for receiving a message, wherein the message comprises Token information of an endpoint;
the authentication module is used for identifying the endpoint identity according to the Token information, authenticating the endpoint identity and judging whether the endpoint has the right to send the message;
the engine state identification module is used for judging the available state of the current engine under the condition that the message authentication is passed;
the engine matching module is used for preliminarily distributing the adaptive engine instances according to the message types under the condition that the available engines exist at present;
and the load balancing processing module is used for selecting an engine instance according to a load balancing algorithm and sending the message to the engine instance for processing.
9. A computer device for application to a cluster manager, comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method according to any of claims 1 to 7 when executing the computer program.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111162019.2A CN113905048A (en) | 2021-09-30 | 2021-09-30 | Method and device for scheduling engine instance by cluster manager and computer equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111162019.2A CN113905048A (en) | 2021-09-30 | 2021-09-30 | Method and device for scheduling engine instance by cluster manager and computer equipment |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113905048A true CN113905048A (en) | 2022-01-07 |
Family
ID=79189969
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111162019.2A Pending CN113905048A (en) | 2021-09-30 | 2021-09-30 | Method and device for scheduling engine instance by cluster manager and computer equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113905048A (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130219412A1 (en) * | 2012-02-22 | 2013-08-22 | Oracle International Corporation | System and method to provide bpel support for correlation aggregation |
| US20170289084A1 (en) * | 2016-04-01 | 2017-10-05 | International Business Machines Corporation | Messaging forwarding system and method |
| CN111614701A (en) * | 2019-02-22 | 2020-09-01 | 杭州海康威视数字技术股份有限公司 | Distributed cluster and container state switching method and device |
| CN112149142A (en) * | 2019-06-29 | 2020-12-29 | 华为技术有限公司 | Database access method and apparatus, computing device and computer program product |
| CN112612588A (en) * | 2020-12-25 | 2021-04-06 | 北京知因智慧科技有限公司 | Task processing method, device, equipment and storage medium |
| CN112765639A (en) * | 2021-01-27 | 2021-05-07 | 武汉大学 | Security micro-service architecture based on zero trust access strategy and implementation method |
-
2021
- 2021-09-30 CN CN202111162019.2A patent/CN113905048A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20130219412A1 (en) * | 2012-02-22 | 2013-08-22 | Oracle International Corporation | System and method to provide bpel support for correlation aggregation |
| US20170289084A1 (en) * | 2016-04-01 | 2017-10-05 | International Business Machines Corporation | Messaging forwarding system and method |
| CN111614701A (en) * | 2019-02-22 | 2020-09-01 | 杭州海康威视数字技术股份有限公司 | Distributed cluster and container state switching method and device |
| CN112149142A (en) * | 2019-06-29 | 2020-12-29 | 华为技术有限公司 | Database access method and apparatus, computing device and computer program product |
| CN112612588A (en) * | 2020-12-25 | 2021-04-06 | 北京知因智慧科技有限公司 | Task processing method, device, equipment and storage medium |
| CN112765639A (en) * | 2021-01-27 | 2021-05-07 | 武汉大学 | Security micro-service architecture based on zero trust access strategy and implementation method |
Non-Patent Citations (2)
| Title |
|---|
| 任涛: "《云计算技术与应用 第1版》", 31 December 2020, 东北大学出版社, pages: 25 - 26 * |
| 张靓裔隽: "《企业迁云之路》", 31 October 2019, 机械工业出版社, pages: 195 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8898680B2 (en) | System and method for supporting asynchronous message processing in a distributed data grid | |
| US8447881B2 (en) | Load balancing for services | |
| CN106817408B (en) | Distributed server cluster scheduling method and device | |
| US20030126196A1 (en) | System for optimizing the invocation of computer-based services deployed in a distributed computing environment | |
| CN109995842B (en) | Grouping method and device for distributed server cluster | |
| CN106936925A (en) | Load-balancing method and system | |
| KR102558330B1 (en) | Apparatus and method for distributing and storing data | |
| CN105933408A (en) | Implementation method and device of Redis universal middleware | |
| CN107423942B (en) | Service transfer method and device | |
| CN111711526A (en) | Consensus method and system for block chain nodes | |
| CN114189525B (en) | Service request method and device and electronic equipment | |
| CN106533961B (en) | Flow control method and device | |
| CN103577251A (en) | Event based Internet computing processing system and method | |
| CN113032431A (en) | High-availability client load balancing method based on database middleware cluster | |
| CN112433863A (en) | Micro-service calling method and device, terminal equipment and storage medium | |
| CN111245887B (en) | Hbase connection dynamic holding method, Hbase connection dynamic holding equipment, Hbase connection dynamic storage medium and Hbase connection dynamic storage system | |
| CN110838987B (en) | Queue current limiting method and storage medium | |
| CN114268667B (en) | Data forwarding method, device, computer equipment and storage medium | |
| CN115757611A (en) | Big data cluster switching method and device, electronic equipment and storage medium | |
| CN117319212B (en) | Multi-tenant isolated password resource automatic scheduling system and method in cloud environment | |
| CN114500546A (en) | Communication message sending method, device and equipment based on load balancing cluster | |
| CN112054919B (en) | Method, device, storage medium and system for generating ID (identity) of container cluster under stateless condition | |
| CN112631756A (en) | Distributed regulation and control method and device applied to space flight measurement and control software | |
| CN113905048A (en) | Method and device for scheduling engine instance by cluster manager and computer equipment | |
| CN112001800B (en) | Method and device for processing business in block chain system |
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 |