CN113992680B - Scheduling method, device, equipment and medium applied to distributed multi-activity system - Google Patents
Scheduling method, device, equipment and medium applied to distributed multi-activity system Download PDFInfo
- Publication number
- CN113992680B CN113992680B CN202111329926.1A CN202111329926A CN113992680B CN 113992680 B CN113992680 B CN 113992680B CN 202111329926 A CN202111329926 A CN 202111329926A CN 113992680 B CN113992680 B CN 113992680B
- Authority
- CN
- China
- Prior art keywords
- service
- configuration information
- information
- micro
- distributed multi
- 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.)
- Active
Links
- 230000000694 effects Effects 0.000 title claims abstract description 62
- 238000000034 method Methods 0.000 title claims abstract description 51
- 238000003860 storage Methods 0.000 claims abstract description 17
- 230000015654 memory Effects 0.000 claims description 12
- 230000008859 change Effects 0.000 claims description 5
- 238000012544 monitoring process Methods 0.000 claims description 5
- 238000004590 computer program Methods 0.000 description 17
- 238000010586 diagram Methods 0.000 description 15
- 230000014509 gene expression Effects 0.000 description 12
- 230000006870 function Effects 0.000 description 11
- 238000012545 processing Methods 0.000 description 10
- 235000014510 cooky Nutrition 0.000 description 7
- 238000012986 modification Methods 0.000 description 7
- 230000004048 modification Effects 0.000 description 7
- 238000011084 recovery Methods 0.000 description 7
- 238000004891 communication Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000008901 benefit Effects 0.000 description 3
- 238000010276 construction Methods 0.000 description 3
- 238000009826 distribution Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000002688 persistence Effects 0.000 description 3
- 238000010200 validation analysis Methods 0.000 description 3
- 238000013500 data storage Methods 0.000 description 2
- 229910003460 diamond Inorganic materials 0.000 description 2
- 239000010432 diamond Substances 0.000 description 2
- 239000003999 initiator Substances 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 238000012216 screening Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000032683 aging Effects 0.000 description 1
- 238000013475 authorization Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000004806 packaging method and process Methods 0.000 description 1
- 230000004044 response Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 239000012089 stop solution Substances 0.000 description 1
- 239000000758 substrate Substances 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
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
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- 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/26—Route discovery packet
Abstract
The invention provides a scheduling method applied to a distributed multi-activity system, which can be applied to the technical field of information security. The scheduling method comprises the following steps: collecting information of each micro-service cluster in an operation state in the distributed multi-activity system, wherein the information of each micro-service cluster in the operation state comprises information of a data center to which each micro-service cluster belongs; configuring routing packet marking configuration information, wherein the routing packet marking configuration information comprises configuration information for scheduling service requests accessing the distributed multi-active system in the M data centers; and scheduling the service request to one of the M data centers based on the routing packet label configuration information and the information of each micro service cluster in an operation state. The present disclosure also provides a scheduling apparatus, device, storage medium and program product for use in a distributed multi-activity system.
Description
Technical Field
The present disclosure relates to the field of information security, and more particularly, to a scheduling method, apparatus, device, medium, and program product for use in a distributed multi-active system.
Background
Enterprises typically deal with disasters through disaster recovery arrangements of multiple data centers. However, in the disaster recovery mode, a primary-secondary relationship exists between the plurality of data centers, that is, a difference exists between service deployment priorities. This results in very long response and switching cycles for disasters, failure of the recovery time objective (recovery time Object, RTO) and recovery point objective (Recovery Point Object, RPO) to achieve zero disruption of traffic, low resource utilization, and failure to expect return on investment.
Thus, more and more businesses are beginning to divert points of interest to the construction of "distributed multiple active data centers" (distributive data active/Active Data Centers). The distributed multi-activity data center distributes the service to a plurality of data centers, provides services for clients in parallel, and the distributed multi-activity data center comprises two key characteristics, namely distributed and multi-activity, so that a new thought of resource scheduling utilization and service deployment flexibility of enterprise-level users in the process of constructing and using the data centers is embodied. In the data center construction of a distributed multi-activity data center, infrastructure architecture changes, and new requirements are put on application architecture planning, technical platform supporting capability and scheduling use.
Disclosure of Invention
In view of the foregoing, embodiments of the present disclosure provide a scheduling method, apparatus, device, medium, and program product for a distributed multi-active system.
In a first aspect of the disclosed embodiments, a scheduling method applied to a distributed multi-activity system is provided, where the distributed multi-activity system includes M data centers, where M is an integer greater than or equal to 2, and any one business service in the distributed multi-activity system is provided in parallel by at least two data centers in the M data centers, where each data center provides a service through a micro-service cluster deployed therein. The scheduling method comprises the following steps: collecting information of each micro-service cluster in an operation state in the distributed multi-activity system, wherein the information of each micro-service cluster in the operation state comprises information of a data center to which each micro-service cluster belongs; configuring routing packet label configuration information, wherein the routing packet label configuration information includes configuration information for scheduling service requests in the M data centers for access to the distributed multi-active system; and scheduling the service request to one of the M data centers based on the routing packet label configuration information and the information of each micro service cluster in an operation state.
According to an embodiment of the disclosure, the collecting information of each micro service cluster in an operating state in the distributed multi-active system includes: and when each micro service cluster in the distributed multi-activity system is started, registering information of a data center to which the micro service cluster belongs.
According to an embodiment of the present disclosure, the configuring the routing packet label configuration information includes monitoring variation information of the routing packet label configuration information, and updating the routing packet label configuration information when the variation information is monitored.
According to an embodiment of the present disclosure, the routing packet label configuration information includes priority access configuration information and default access configuration information. The priority access configuration information is used for specifying a data center which is accessed preferentially during scheduling, and the default access configuration information is used for specifying an alternative data center when the data center which is accessed preferentially cannot provide service.
According to an embodiment of the present disclosure, the scheduling the service request to one of the M data centers based on the routing packet label configuration information and the information of each micro service cluster in an operating state includes: when a user logs in, marking a label of a data center to which a micro service cluster providing micro service for the user belongs in a user session according to user login information and the routing grouping marking configuration information; and when the service request sent by the user is received, scheduling the service request to a corresponding data center based on a tag carried by the service request and coming from the data center in the user session.
According to an embodiment of the disclosure, the routing packet label configuration information further includes configuration information that schedules call requests between micro service nodes inside the distributed multi-active system among the M data centers. The method further comprises the steps of: and scheduling the call request to one of the M data centers based on the routing packet label configuration information and the information of each micro service cluster in the running state.
According to an embodiment of the present disclosure, the scheduling the call request to one of the M data centers based on the routing packet label configuration information and the information of each micro service cluster in the running state includes: judging key fields in the call request based on the routing packet label configuration information; determining a data center of the micro service called by the call request based on the key field and the information of each micro service cluster in the running state; and dispatching the calling request to a data center where the called micro service is located.
According to an embodiment of the present disclosure, before the scheduling of the call request to one of the M data centers based on the routing packet label configuration information and the information of the respective micro-service clusters in the running state, the method further includes publishing the information of the respective micro-service clusters in the running state to all micro-service clusters in the distributed multi-active system.
In a second aspect of the disclosed embodiments, a scheduling apparatus applied to a distributed multi-activity system is provided, where the distributed multi-activity system includes M data centers, where M is an integer greater than or equal to 2, and any one business service in the distributed multi-activity system is provided in parallel by at least two data centers of the M data centers, where each data center provides a service through a micro-service cluster deployed therein. The scheduling device comprises a service discovery module, a configuration center and a routing service module. The service discovery module is used for collecting information of each micro-service cluster in an operation state in the distributed multi-activity system, and the information of each micro-service cluster in the operation state comprises information of a data center to which each micro-service cluster belongs. The configuration center is configured to configure routing packet label configuration information, wherein the routing packet label configuration information includes configuration information for scheduling service requests in the M data centers for access to the distributed multi-active system. The routing service module is used for scheduling the service request to one of the M data centers based on the routing packet label configuration information and the information of each micro service cluster in the running state.
According to an embodiment of the present disclosure, the routing packet label configuration information configured by the configuration center further includes configuration information for scheduling call requests between micro service nodes inside the distributed multi-active system among the M data centers. The routing service module is further configured to schedule the call request to one of the M data centers based on the routing packet label configuration information and the information of each micro service cluster in an operational state.
According to an embodiment of the present disclosure, the service discovery module is further configured to publish information of each micro service cluster in the running state to all micro service clusters in the distributed multi-active system.
A third aspect of the disclosed embodiments provides an electronic device. The electronic device includes one or more processors and one or more memories. The one or more memories are used to store one or more programs. Wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to perform the above-described method.
A fourth aspect of the disclosed embodiments also provides a computer-readable storage medium having stored thereon executable instructions that, when executed by a processor, cause the processor to perform the above-described method.
A fifth aspect of the disclosed embodiments also provides a computer program product comprising a computer program which, when executed by a processor, implements the above method.
One or more of the above embodiments have the following advantages or benefits: the routing grouping mark configuration information can be configured through flexible operation, dynamic routing grouping mark configuration information adjustment is realized, and the request is scheduled among different data centers according to the routing grouping mark configuration information, so that the services of the different data centers are isolated, the convenience and the flexibility of the multi-version micro-service release system are improved, and the operation and the maintenance are convenient.
Drawings
The foregoing and other objects, features and advantages of the disclosure will be more apparent from the following description of embodiments of the disclosure with reference to the accompanying drawings, in which:
FIG. 1 schematically illustrates an application scenario diagram of a scheduling method, apparatus, device, medium and program product applied to a distributed multi-living system according to an embodiment of the present disclosure;
FIG. 2 schematically illustrates a block diagram of a scheduling apparatus applied to a distributed multi-activity system according to an embodiment of the present disclosure;
FIG. 3 schematically illustrates a deployment diagram of a distributed multi-activity system according to another embodiment of the present disclosure;
FIG. 4 schematically illustrates a flow chart of a scheduling method applied to a distributed multi-active system in accordance with an embodiment of the present disclosure;
FIG. 5 schematically illustrates a flow chart of a scheduling method applied to a distributed multi-active system in accordance with another embodiment of the present disclosure;
FIG. 6 schematically illustrates a setup flow diagram of routing packet label configuration information and service discovery in a distributed multi-active system in a scheduling method according to an embodiment of the disclosure;
FIG. 7 schematically illustrates a flow chart of a scheduling method applied to a distributed multi-active system in accordance with another embodiment of the present disclosure; and
fig. 8 schematically illustrates a block diagram of an electronic device adapted to implement a scheduling method applied to a distributed multi-activity system according to an embodiment of the present disclosure.
Detailed Description
Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is only exemplary and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the present disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. In addition, in the following description, descriptions of well-known structures and techniques are omitted so as not to unnecessarily obscure the concepts of the present disclosure.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and/or the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components.
All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It should be noted that the terms used herein should be construed to have meanings consistent with the context of the present specification and should not be construed in an idealized or overly formal manner.
Where expressions like at least one of "A, B and C, etc. are used, the expressions should generally be interpreted in accordance with the meaning as commonly understood by those skilled in the art (e.g.," a system having at least one of A, B and C "shall include, but not be limited to, a system having a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).
In this document, it should be understood that any number of elements in the specification and drawings are for example, not limitation, and that any naming (e.g., first, second) is used for distinguishing only, and not for any limiting sense.
In an embodiment of the present disclosure, a distributed multi-activity system includes M data centers, M being an integer greater than or equal to 2. Any business service in the distributed multi-activity system is provided by at least two data centers in the M data centers in parallel, so that the multi-activity characteristic is reflected, namely, different data centers can provide services in parallel in daily operation. Compared with the traditional disaster recovery mode, when a certain business service provided by a certain data center is abnormal in the distributed multi-activity system, the request for the business service can be scheduled to other data centers for providing the business service without interruption, and the continuity of the business is effectively improved.
In the M data centers, each data center provides a service through a micro service cluster deployed therein. In particular, each data center may deploy one or more micro service clusters. Different micro service clusters provide different business services. And a plurality of micro service nodes for providing the same micro service can be deployed in each micro service cluster, and the micro service is provided in parallel through the plurality of micro service nodes, so that the high availability performance of the micro service clusters is ensured.
Based on the architecture of the distributed multi-activity system, the embodiments of the present disclosure provide a scheduling method, apparatus, device, medium and program product applied to the distributed multi-activity system, which can associate a service request for accessing the distributed multi-activity system with a certain data center by routing tag packet configuration information, thereby scheduling the service request to the associated data center. In other embodiments of the present disclosure, the association of the call request between the micro service nodes and the data center may also be identified according to the route tag packet configuration information, and the inter-call of the micro service nodes may be implemented between the data centers. The routing mark grouping configuration information can be configured or modified and adjusted according to actual needs and takes effect in real time, so that the resource deployment flexibility and access convenience of the distributed multi-activity system are improved.
It should be noted that, the scheduling method, apparatus, device, medium and program product applied to the distributed multi-activity system according to the embodiments of the present disclosure may be used in the financial field, and may also be used in any field other than the financial field, and the application field is not limited in this disclosure.
Fig. 1 schematically illustrates an application scenario diagram of a scheduling method, apparatus, device, medium and program product applied to a distributed multi-activity system according to an embodiment of the present disclosure.
As shown in fig. 1, the application scenario is a set of dynamic publishing deployment examples of micro-service deployment and routing grouping marking configuration information which can actually land under two places and three centers based on Spring Cloud (a one-stop solution of a micro-service system architecture). The two-place three centers are specifically a production data center (A park) and a same city disaster recovery center (B park) which are deployed in the A market, and a different-place disaster recovery center (C park) which is deployed in the B market. It can be seen from the figure that the micro-service clusters in the various data centers (a-park, B-park, and C-park) can share the same set of scheduling means (including service discovery module 9100, configuration center 9200, and routing service module 9300). The operation of the scheduling apparatus may be described with reference to the example of fig. 2.
It should be noted that fig. 1 illustrates only an example of an application scenario in which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments, or scenarios.
Fig. 2 schematically illustrates a block diagram of a scheduling apparatus 900 applied to a distributed multi-activity system according to an embodiment of the present disclosure.
As shown in fig. 2, the scheduling apparatus 900 according to the embodiment of the present disclosure includes a service discovery module 9100, a configuration center 9200, and a routing service module 9300.
The service discovery module 9100 is configured to collect information of each micro service cluster in an operating state in the distributed multi-active system. The information of each micro service cluster in the running state comprises information of a data center to which each micro service cluster belongs.
In some embodiments, the service discovery module 9100 is further configured to publish information of each micro service cluster in an operating state to all micro service clusters in the distributed multi-active system, so as to facilitate mutual invocation between micro service nodes in the distributed multi-active system.
The configuration center 9200 is configured to configure routing packet label configuration information, where the routing packet label configuration information includes configuration information (e.g., scheduling rules, scheduling selection basis or policies, or scheduling manners, etc.) for scheduling service requests in the M data centers for accessing the distributed multi-active system. In other embodiments, the routing packet label configuration information configured by configuration center 9200 further includes configuration information (e.g., scheduling rules, scheduling selection basis or policies, or scheduling modes, etc.) that schedules call requests between micro-service nodes within the distributed multi-active system among the M data centers. The routing packet marking configuration information can mark the service request according to the account information of the user, a certain field (such as an IP address, login time, or client version) in the request, or a preset principle in the area of the initiator of the request, so as to indicate the data center which can be accessed by the service request.
The routing service module 9300 is configured to schedule a service request to one of the M data centers based on the routing packet label configuration information and information of each micro service cluster in an operating state. For example, the service request may be scheduled to a data center closest to the data center according to a generic principle based on an IP address in the service request, or the service request may be scheduled to a data center having access rights according to a guest identity authorization request by a different data center based on user identity information in the service request, or the service request with high real-time requirements may be scheduled to a data center where a master database is deployed based on real-time properties of content requested by the service request, for example.
In other embodiments, the routing service module 9300 is further configured to schedule a call request between micro services in the distributed multi-active system to one of the M data centers based on the routing packet label configuration information and information of each micro service cluster in an operational state.
According to an embodiment of the present disclosure, after receiving a service request sent by a user, the routing service module 9300 marks a data center tag on the received service request according to routing packet marking configuration information, and issues the service request to a micro service node of the data center according to the tag for processing. When the micro service nodes call each other, the routing service module 9300 can also select the micro service node of the data center to process according to the data center label in the call request. Enabling simultaneous deployment of multiple versions of micro-services in a distributed multi-active system and collection and discovery of these micro-services through a set of service discovery modules 9100. Meanwhile, the routing service module 9300 analyzes the request according to the routing packet marking configuration information, and selects the executed data center, wherein the routing packet marking configuration information can be issued to the routing service module 9300 and each micro service node by the configuration center 9200, so that dynamic configuration is realized. Therefore, the distributed multi-activity system is stable as a whole, problems can be found and adjusted in advance, and the influence range is controllable. The user is not felt, and the transition is smooth.
Fig. 3 schematically illustrates a deployment diagram of a distributed multi-activity system according to another embodiment of the present disclosure.
A scheduler 900 is deployed in the distributed multi-active system illustrated in fig. 3. Specifically, fig. 3 is a schematic diagram of deployment of a multi-active multi-data center in different places based on micro-services, and a two-place three-center construction scheme is adopted. Wherein in the example of fig. 3, a routing service module 9300 and a service discovery module 9100 are deployed at the ABC park, respectively, while the ABC park may share a configuration center 9200. The micro-service clusters 9400 in the distributed multi-activity system include micro-service clusters 9410, 9420, and 9430, respectively, for each campus. Database 9500 may be any database system known in the art.
The routing service module 9300 accepts user registration and each service request. When a user logs in, the data center label for providing micro services for the user can be marked in the user session according to the route grouping marking configuration information and a cookie (data stored on a local terminal of the user) is recorded; and then after receiving each service request sent by the user, loading each service request to the micro service cluster 9400 of the corresponding data center according to the data center label in the service request cookie. The routing packet label configuration information may be dynamically modified and validated in real time at the configuration center 9200 according to the service logic processing result to perform traffic switching in accordance with the service logic processing result.
The routing service module 9300 may include one or more routing service nodes, each of which may monitor configuration changes of the configuration center 9200 in order to facilitate instant validation of routing packet label configuration information. The routing service module 9300 may be implemented by a micro service component such as a micro service gateway Gateway, zuul, netfilix, or by a load component such as nginnx (a high performance HTTP and reverse proxy web server).
The service discovery module 9100 is mainly responsible for recording and distributing data center labels to which each micro service cluster 9410, 9420, 9430 belongs, and distributing information of each micro service cluster in an operating state (for example, a service function of each micro service cluster, a label of a data center to which each micro service cluster belongs, a node in each micro service cluster, etc.) to all the micro service nodes and the routing service module 9300. Thus, the routing service module 9300 may schedule a service request of a user or a call request between micro service nodes according to the latest information of the micro service cluster acquired from the service discovery module 9100 and according to the latest routing packet label configuration information.
Specifically, the service discovery module 9100 may register the micro service clusters 9410, 9420, 9430 and their data center labels to the service discovery module 9100 together when the micro service clusters 9410, 9420, 9430 are started, and the service discovery module 9100 periodically acquires information of all other micro service clusters. The service discovery module 9100 can be implemented by Eureka (a service discovery framework), zookeeper (a distributed application coordination service), nacos (an open source configuration center), and the like.
The configuration center 9200 is mainly responsible for storing and distributing routing packet label configuration information, and is provided with configuration and distribution interfaces. The system administrator may configure or modify the routing packet label configuration information for the service request at configuration center 9200 via the configuration interface. The routing service module 9300 and the versions of the micro service clusters 9410, 9420, 9430 can obtain and update routing packet label configuration information via the distribution interfaces. The configuration and modification of the routing packet label configuration information may be a dynamic modification that takes effect on the fly (or as real-time validation) so that the configuration can be validated without restarting the system. And at the same time, the configuration center 9200 acquires the latest routing packet label configuration information and distributes the latest routing packet label configuration information to the routing service module 9300 and takes effect in real time. The configuration center 9200 may be implemented by an open source-based distributed configuration center (e.g., apollo, diamond, disconf, etc.), or may be implemented by a zookeeper, database, cache, etc.
The routing packet label configuration information can be matched with any field in a user account or service request through Spring expression language (Spring Expression Language, spEL) grammar, and can also be realized through codes in a common program.
Each version of the micro service cluster 9400 can implement various business logics by using the tag of the data center (for example, A, B, C) to which the micro service belongs as a flag for distinguishing each micro service cluster 9410, 9420, 9430. When the micro service cluster is started, the micro service cluster and the data center label are registered to the service discovery module 9100 together, and the service discovery module 9100 acquires information of all other micro service clusters at regular time. And the configuration center 9200 acquires the latest routing packet label configuration information at a fixed time and takes effect in real time.
When calling among the micro service nodes, judging key fields in the calling request through the routing packet marking configuration information and calling the corresponding version of micro service in the corresponding data center. Wherein the versions of the microservice provided in different data centers to handle the same business logic may be different to provide services for different user groups or different areas or to suit the database system performance of each data center. For example, the distribution area coverage of the logistics service of the a-park or the logistics service of the C-park may be different, and the two services belong to different versions of micro-services, however, in an emergency, the two services may be replaced with each other, so as to ensure service continuity and avoid service interruption.
In the embodiment of the disclosure, the micro-service may be implemented by a service interface such as Spring Cloud, dubbo (an open source distributed service framework), or may be implemented by an http service such as servlets or service connectors (Server Applet, servlet), or may be implemented by other languages such as python, c++, etc.
The database 9500 is mainly used as a data persistence layer, is only responsible for data storage of a system, does not contain any business processing codes, and has a data table structure for supporting all versions in the micro service cluster. The data persistence layer may be implemented by any product that has data storage capabilities, including, but not limited to, structured databases, unstructured databases, distributed file systems, distributed search engines, and the like.
Fig. 4 schematically illustrates a flow chart of a scheduling method applied to a distributed multi-active system according to an embodiment of the present disclosure.
As shown in fig. 4, the scheduling method may include operations S410 to S430 according to an embodiment of the present disclosure.
In operation S410, the service discovery module 9100 collects information of each micro service cluster in an operating state in the distributed multi-active system. Wherein the information of each micro service cluster in the running state includes information of a data center to which each micro service cluster belongs (for example, a tag of the data center to which each micro service cluster belongs).
For example, when each micro service cluster in the distributed multi-activity system is started, information of a data center to which the micro service cluster belongs may be registered. Alternatively, information of each micro-service cluster in the running state in the distributed multi-activity system can be collected and collected regularly.
The configuration center 9200 configures routing packet label configuration information including configuration information for scheduling service requests for access to the distributed multi-active system in the M data centers in operation S420. The routing packet marking configuration information can mark the label of the data center for the service request according to the key field in the service request, so that the service request can be scheduled according to the label. The key field in the service request can be account information of the user, a certain field in the service request or an IP address of an initiator of the request, and the rule of the tag label can be a affiliated rule, a rule of a range to which the service belongs, a rule of role identity authority or the like.
According to embodiments of the present disclosure, routing packet label configuration information may be dynamically configured and validated on-the-fly. For example, the configuration center 9200 modifies and stores routing packet label configuration information and distributes it to the routing service module 9300 in time. Alternatively, the routing service module 9300 monitors the configuration center 9200 for changes in time and updates the routing packet label configuration information when changes are detected.
According to the embodiment of the disclosure, when the routing packet label configuration information is configured, the priority access configuration information and the default access configuration information can be configured for the same business service. Wherein the priority access configuration information is used to designate a data center that is to be accessed preferentially at the time of scheduling, and the default access configuration information is used to designate an alternative data center when the data center that is to be accessed preferentially cannot provide service. Therefore, when an emergency situation or sudden disaster occurs, the system can be seamlessly switched to the alternative data center, so that the stability and the safe operation of the service are realized.
In operation S430, the routing service module 9300 may schedule the service request to one of the M data centers based on the routing packet tag configuration information and information of each micro service cluster in an operation state.
For example, at least two data centers that can provide services are selected from the data centers based on matching of the content of the service requested by the service request with the services provided by each data center in the distributed multi-activity system (of course, this step may be omitted if all the data centers provide the same service function), and then the data center that can currently provide services may be selected from the at least two data centers according to the preset rule (for example, the generic rule, the aging rule, the authority control rule, the priority rule, etc.) in the routing packet label configuration information according to the key field in the service request according to the routing packet label configuration information, and the label of the data center is labeled to the service request. The routing service module 9300 can then schedule the service request to the data center indicated by the label, with the service processing logic provided by the micro service nodes in the corresponding micro service cluster in the data center.
In this way, the efficiency and stability of acquiring the target application when the user accesses the distributed multi-activity system are improved, the whole process is not perceived by the user, and the application experience of the user is improved.
Fig. 5 schematically illustrates a flow chart of a scheduling method applied to a distributed multi-active system according to another embodiment of the present disclosure.
As shown in fig. 5, the scheduling method according to the embodiment may include operation S410, operation S520, operation S530, and operation S541 and/or operation S542.
In operation S410, the service discovery module 9100 collects information of each micro service cluster in an operating state in the distributed multi-active system. The information of each micro service cluster in the running state includes information of a data center to which each micro service cluster belongs. With specific reference to the above description, no further description is provided herein.
The service discovery module 9100 then publishes information of each micro service cluster in an operational state to all micro service clusters in the distributed multi-active system in operation S520. After being released to all the micro service clusters, each micro service cluster can know the states of other micro service clusters in the distributed multi-activity system and the data center to which the micro service clusters belong, so that the micro service nodes crossing the data center can be conveniently called. When the micro service node is started, the service and the data center label thereof are registered to the service discovery module 9100, and the service discovery module 9100 sends the service and the data center label information of the total nodes to the routing service module 9300 and each micro service cluster.
Next, in operation S530, the configuration center 9200 configures routing packet label configuration information including configuration information for scheduling service requests accessing the distributed multi-active system in the M data centers and configuration information for scheduling call requests among micro service nodes inside the distributed multi-active system among the M data centers.
Then, when the routing service module 9300 receives the service request for access to the distributed multi-active system, the service request is scheduled to one of the M data centers based on the routing packet tag configuration information and the information of each micro service cluster in an operation state in operation S541. Reference is made in particular to the description above with respect to operation S430.
Alternatively, when the routing service module 9300 receives a call request between micro service nodes inside the distributed multi-active system, the call request is scheduled to one of M data centers based on the routing packet flag configuration information and information of each micro service cluster in an operation state in operation S542. Specifically, a key field (for example, information such as IP, a client mobile phone number, a client version, etc.) in the call request may be determined based on the routing packet label configuration information, and a data center where the micro service called by the call request is located may be determined according to a rule preset in the routing packet label configuration information (for example, a generic rule, a version correspondence rule, or a priority rule) based on the key field and information of each micro service cluster in an operating state, and then the call request is dispatched to the data center where the micro service called by the call request is located. In this way, the distributed micro-service resource scheduling utilization and service deployment flexibility can be improved.
The embodiment of the disclosure designs a multi-activity deployment scheme in different places by utilizing the operation characteristics of service discovery, routing and configuration centers in a micro-service framework. Dynamic routing grouping marking configuration information adjustment can be realized by flexibly operating the routing grouping marking configuration information in the configuration center 9200, services of different data centers are isolated, the services of the different data centers are not affected, the convenience and flexibility of the multi-version release system are improved, and the operation and maintenance are convenient.
Fig. 6 schematically illustrates a setup flow diagram of routing packet label configuration information and service discovery in a distributed multi-active system in a scheduling method according to an embodiment of the disclosure.
As shown in fig. 6, the configuration and service discovery of the routing packet label configuration information according to the embodiment of the present disclosure may include steps S601 to S603.
Step S601: the configuration center 9200 configures and distributes routing packet label configuration information. Specifically, the system administrator implements configuration or modification of routing packet label configuration information for service requests through the configuration interface of configuration center 9200. The configuration and modification of the routing packet label configuration information may be a dynamic modification that takes effect on the fly (or as real-time validation) so that the configuration can be validated without restarting the system. The configuration center 9200 may be implemented by an open source-based distributed configuration center (e.g., apollo, diamond, disconf, etc.), or may be implemented by a database or cache, etc.
Step S602: when the micro service cluster is started, the data center label of the micro service is registered to the service discovery module 9100, and the routing service module 9300 and each micro service cluster acquire the service of the full-quantity node and the data center label information of the micro service from the service discovery module 9100 at regular time.
Step S603: the routing service module 9300 and each micro-service cluster periodically obtain routing packet label configuration information from the configuration center 9200 and take effect in real time.
Fig. 7 schematically illustrates a flow chart of a scheduling method applied to a distributed multi-active system according to another embodiment of the present disclosure.
Step S701: when a user logs in, before generating a session, the routing service module 9300 marks the session of the user according to the routing packet mark configuration information, and marks a cookie. Specifically, the routing service module 9300 screens keywords in the user condition according to the routing packet label configuration information, labels the data center label to which the micro service belongs in the user session, and records the data center label to which the micro service belongs in the cookie. When a user logs in, the labels of the data centers of the micro service clusters which provide micro services for the user are marked in the user session according to the user login information and the routing grouping marking configuration information;
Step S702: the user initiates a service request through the front end, and the routing service module 9300 reads the cookie in the request and loads the service request to the micro service cluster of the corresponding data center according to the mark. Therefore, when the service request sent by the user is received, the service request is scheduled to the corresponding data center based on the label carried by the service request and coming from the data center in the user session.
Step S703: when the micro services are mutually called, the key field in the request is judged by the routing grouping mark configuration information of the local cache, the data center label of the called micro service is selected according to the key field, and then the micro service node is selected from the micro service node information of the local cache to call the micro service node in the appointed data center.
The key field in the screening of the data center label of the micro service can use any field in the service request message. Including but not limited to, the fields in the business request and the element information such as the area where the transaction is located, IP, client phone number, client version, etc., thus realizing flexible configuration according to the transaction scenario.
The field value extracted from the key field may be only the service request processed by a specific service logic, or may be only the corresponding tag matching field range configured for all the service logics. When the target value matched with the mark in the received service request is in the range of the mark matching field, the service request mark can be corresponding to the data center label of the micro service, otherwise, marking is not carried out. Thus, when distributing, if a service request is marked with a data center label, the service request is indicated to be processed by a micro service cluster of a designated data center; if a service request is not marked with the data center label, the service request is indicated to designate the micro service cluster logic processing of the default data center.
Any of the service discovery module 9100, the configuration center 9200, and the routing service module 9300 may be combined in one module to be implemented, or any of the modules may be split into a plurality of modules according to an embodiment of the present disclosure. Alternatively, at least some of the functionality of one or more of the modules may be combined with at least some of the functionality of other modules and implemented in one module. At least one of the service discovery module 9100, the configuration center 9200, and the routing service module 9300 may be implemented, at least in part, as hardware circuitry, such as a Field Programmable Gate Array (FPGA), a Programmable Logic Array (PLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or by hardware or firmware, such as any other reasonable way of integrating or packaging the circuitry, or in any one of or a suitable combination of three of software, hardware, and firmware, according to embodiments of the present disclosure. Alternatively, at least one of the service discovery module 9100, the configuration center 9200, and the routing service module 9300 may be at least partially implemented as a computer program module, which when executed, may perform corresponding functions.
In one embodiment, for example, in the micro service deployment scheme shown in fig. 1, the service discovery module 9100, the configuration center 9200, and the routing service module 9300 may be implemented in the following manner.
Service discovery module 9100: spring Cloud Eureka clusters may be employed, which may be deployed in any one or more campuses of a triple-play, with the micro-service only needing to register with one of the Eureka services due to the nature of the Eureka clusters. Registration information received by each service is synchronized between Eureka clusters through a background process. The reason Spring Cloud Euraka is used in the project is that it can utilize other components in Spring Cloud Netfilix, such as Zuul et al, because Euraka is of Netfilix (netflix, usa).
Routing service module 9300: netfilix Zuul may be employed, all traffic requests will go through Zuul to the back-end Spring Cloud application. As an application of a boundary nature, zuul may provide dynamic routing, monitoring, elastic loading and security functions. Through the filter configuration of Zuul, the functions of authentication and security, performance monitoring, dynamic routing, pressure testing, load unloading, static resource processing and the like can be realized. In this example, session management and dynamic routing functions are implemented mainly by Zuul, and the configuration center periodically obtains the latest routing packet label configuration information. When a user creates a session, any field in account information or a request of the user can be matched through the SpEL expression and the regular expression, a matching result is marked into the session and fed back to the foreground, and a data center label is recorded in a cookie. When a service request is received, a server screening mechanism based on Zuul and Feign (a micro-service remote call framework) is realized by inheriting ZoneAvoidamageRule class, and the service to be processed next is selected through a data center flag bit in a Cookie in the request.
Configuration center 9200: a Zookeeper cluster may be employed, one of which is a configuration center of the distributed system in a main application scenario of the Zookeeper. The configuration file is built by building a root node in the Zookeeper. Storing information in the configuration file as a child node of the root node, for example, a configuration item area=shanghai, is shown in a Zookeeper as: the node content is shanghai. And then, integrating the nodes of all the routing service modules and the business service modules by using the application machines which use the configuration information to integrate the Zookeeper and monitor/configure the state, and once the configuration information, namely the child nodes, change, each application machine can receive the notification of the ZK, and then acquire new configuration information from the ZK and apply the new configuration information to the system.
Service node 9400: the service discovery module 9100 is registered with own service and data center information as an example of Sping Cloud Eureka Client, so that the routing service module 9300 can find out.
SpEL expression: i.e., spring expression language (Spring Expression Language), is a more powerful expression language than the EL expression (Expression Language) of Java Server Pages (JSP). The SpEL is summarized because it can query and manipulate data, especially array list type data, at runtime, thus reducing the amount of code and optimizing the code structure. And because it can be stored as a string in the persistence layer, it can be used as a base language for dynamic configuration condition matching.
Examples of java are as follows:
ExpressionParser parse＝new SpelExpressionParser()；
EvaluationContext context＝new StandardEvaluationContext()；
boolean result＝parse.parseExpression(″user.email matches
′[a-zA-Z0-9._％+-]+@[a-zA-Z0-9.-]+.[a-zA-Z]{2,4}′}″).getValue(boolean.class).
feign: spring Cloud Feign components may be employed to primarily enable invocation between micro services and micro services.
Fig. 8 schematically illustrates a block diagram of an electronic device adapted to implement a scheduling method applied to a distributed multi-activity system according to an embodiment of the present disclosure.
As shown in fig. 8, an electronic device 800 according to an embodiment of the present disclosure includes a processor 801 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. The processor 801 may include, for example, a general purpose microprocessor (e.g., a CPU), an instruction set processor and/or an associated chipset and/or a special purpose microprocessor (e.g., an Application Specific Integrated Circuit (ASIC)), or the like. The processor 801 may also include on-board memory for caching purposes. The processor 801 may include a single processing unit or multiple processing units for performing the different actions of the method flows according to embodiments of the disclosure.
In the RAM 803, various programs and data required for the operation of the electronic device 800 are stored. The processor 801, the ROM 802, and the RAM 803 are connected to each other by a bus 804. The processor 801 performs various operations of the method flow according to the embodiments of the present disclosure by executing programs in the ROM 802 and/or the RAM 803. Note that the program may be stored in one or more memories other than the ROM 802 and the RAM 803. The processor 801 may also perform various operations of the method flows according to embodiments of the present disclosure by executing programs stored in the one or more memories.
According to an embodiment of the present disclosure, the electronic device 800 may also include an input/output (I/O) interface 805, the input/output (I/O) interface 805 also being connected to the bus 804. The electronic device 800 may also include one or more of the following components connected to the I/O interface 805: an input portion 806 including a keyboard, mouse, etc.; an output portion 807 including a display such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and a speaker; a storage section 808 including a hard disk or the like; and a communication section 809 including a network interface card such as a LAN card, a modem, or the like. The communication section 809 performs communication processing via a network such as the internet. The drive 810 is also connected to the I/O interface 805 as needed. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as needed so that a computer program read out therefrom is mounted into the storage section 808 as needed.
The present disclosure also provides a computer-readable storage medium that may be embodied in the apparatus/device/system described in the above embodiments; or may exist alone without being assembled into the apparatus/device/system. The computer-readable storage medium carries one or more programs which, when executed, implement methods in accordance with embodiments of the present disclosure.
According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example, but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, the computer-readable storage medium may include ROM 802 and/or RAM 803 and/or one or more memories other than ROM 802 and RAM 803 described above.
Embodiments of the present disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowcharts. The program code, when executed in a computer system, causes the computer system to perform the methods provided by embodiments of the present disclosure.
The above-described functions defined in the system/apparatus of the embodiments of the present disclosure are performed when the computer program is executed by the processor 801. The systems, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.
In one embodiment, the computer program may be based on a tangible storage medium such as an optical storage device, a magnetic storage device, or the like. In another embodiment, the computer program may also be transmitted, distributed, and downloaded and installed in the form of a signal on a network medium, and/or from a removable medium 811 via a communication portion 809. The computer program may include program code that may be transmitted using any appropriate network medium, including but not limited to: wireless, wired, etc., or any suitable combination of the foregoing.
In such an embodiment, the computer program may be downloaded and installed from a network via the communication section 809, and/or installed from the removable media 811. The above-described functions defined in the system of the embodiments of the present disclosure are performed when the computer program is executed by the processor 801. The systems, devices, apparatus, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the disclosure.
According to embodiments of the present disclosure, program code for performing computer programs provided by embodiments of the present disclosure may be written in any combination of one or more programming languages, and in particular, such computer programs may be implemented in high-level procedural and/or object-oriented programming languages, and/or assembly/machine languages. Programming languages include, but are not limited to, such as Java, c++, python, "C" or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Those skilled in the art will appreciate that the features recited in the various embodiments of the disclosure and/or in the claims may be provided in a variety of combinations and/or combinations, even if such combinations or combinations are not explicitly recited in the disclosure. In particular, the features recited in the various embodiments of the present disclosure and/or the claims may be variously combined and/or combined without departing from the spirit and teachings of the present disclosure. All such combinations and/or combinations fall within the scope of the present disclosure.
The embodiments of the present disclosure are described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described above separately, this does not mean that the measures in the embodiments cannot be used advantageously in combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be made by those skilled in the art without departing from the scope of the disclosure, and such alternatives and modifications are intended to fall within the scope of the disclosure.
Claims (7)
1. A scheduling method applied to a distributed multi-activity system, wherein the distributed multi-activity system comprises M data centers, M is an integer greater than or equal to 2, any one business service in the distributed multi-activity system is provided in parallel by at least two data centers of the M data centers, wherein each data center provides a service through a micro-service cluster deployed therein, the scheduling method comprising:
Collecting information of each micro service cluster in an operation state in the distributed multi-activity system, wherein the information comprises the following steps: the information of each micro-service cluster in the running state in the distributed multi-activity system is collected at fixed time; the information of each micro service cluster in the running state comprises information of a data center to which each micro service cluster belongs;
configuring routing packet label configuration information, comprising: monitoring change information of the routing packet label configuration information, and updating configuration of the routing packet label configuration information when the change information is monitored; wherein the routing packet label configuration information includes configuration information for scheduling service requests in the M data centers for access to the distributed multi-active system;
scheduling a service request to one of the M data centers based on the routing packet label configuration information and the information of each micro service cluster in an operational state, including: selecting at least two data centers from the distributed multi-activity system based on the matching of the content of the business service requested by the business request and the service provided by each data center in the distributed multi-activity system; selecting a data center capable of providing service currently from the at least two data centers according to the routing packet marking configuration information;
The routing packet marking configuration information comprises priority access configuration information and default access configuration information; the priority access configuration information is used for specifying a data center which is accessed preferentially during scheduling, and the default access configuration information is used for specifying an alternative data center when the data center which is accessed preferentially cannot provide service;
wherein the routing packet label configuration information further includes configuration information that schedules call requests between micro service nodes within the distributed multi-active system among the M data centers, the method further comprising:
scheduling the call request to one of the M data centers based on the routing packet label configuration information and the information of each micro service cluster in an operational state;
wherein the scheduling the call request to one of the M data centers based on the routing packet label configuration information and the information of each micro service cluster in the running state includes:
judging key fields in the call request based on the routing packet label configuration information;
determining a data center of the micro service called by the call request based on the key field and the information of each micro service cluster in the running state; and
And dispatching the calling request to a data center where the called micro service is located.
2. The method of claim 1, wherein the collecting information of each micro-service cluster in an operational state in the distributed multi-active system further comprises:
and when each micro service cluster in the distributed multi-activity system is started, registering information of a data center to which the micro service cluster belongs.
3. The method of claim 1, wherein the scheduling the service request to one of the M data centers based on the routing packet label configuration information and the information of the respective micro service clusters in an operational state comprises:
when a user logs in, marking a label of a data center to which a micro service cluster providing micro service for the user belongs in a user session according to user login information and the routing grouping marking configuration information; and
and when the service request sent by the user is received, scheduling the service request to a corresponding data center based on a tag carried by the service request and coming from the data center in the user session.
4. The method of claim 1, wherein prior to said scheduling the call request to one of the M data centers based on the routing packet label configuration information and the information of the respective micro service clusters in an operational state, the method further comprises:
And publishing the information of each micro-service cluster in the running state to all the micro-service clusters in the distributed multi-activity system.
5. A scheduler for a distributed multi-active system, wherein the distributed multi-active system comprises M data centers, M being an integer greater than or equal to 2, any one of the business services in the distributed multi-active system being provided in parallel by at least two of the M data centers, wherein each data center is served by a micro-service cluster deployed therein, the scheduler comprising:
the service discovery module is used for collecting information of each micro service cluster in an operation state in the distributed multi-activity system, and comprises the following steps: the information of each micro-service cluster in the running state in the distributed multi-activity system is collected at fixed time; the information of each micro service cluster in the running state comprises information of a data center to which each micro service cluster belongs;
a configuration center for configuring routing packet label configuration information, comprising: monitoring change information of the routing packet label configuration information, and updating configuration of the routing packet label configuration information when the change information is monitored; wherein the routing packet label configuration information includes configuration information for scheduling service requests in the M data centers for access to the distributed multi-active system;
A routing service module, configured to schedule the service request to one of the M data centers based on the routing packet label configuration information and the information of each micro service cluster in an operating state, including: selecting at least two data centers from the distributed multi-activity system based on the matching of the content of the business service requested by the business request and the service provided by each data center in the distributed multi-activity system; selecting a data center capable of providing service currently from the at least two data centers according to the routing packet marking configuration information;
the routing packet marking configuration information comprises priority access configuration information and default access configuration information; the priority access configuration information is used for specifying a data center which is accessed preferentially during scheduling, and the default access configuration information is used for specifying an alternative data center when the data center which is accessed preferentially cannot provide service;
the routing packet marking configuration information further comprises configuration information for scheduling call requests among micro service nodes inside the distributed multi-activity system among the M data centers;
The routing service module is further configured to schedule the call request to one of the M data centers based on the routing packet label configuration information and the information of each micro service cluster in the running state, and includes: judging key fields in the call request based on the routing packet label configuration information; determining a data center of the micro service called by the call request based on the key field and the information of each micro service cluster in the running state; and dispatching the calling request to a data center where the called micro service is located.
6. An electronic device, comprising:
one or more memories storing executable instructions; and
one or more processors executing the executable instructions to implement the method of any of claims 1-4.
7. A computer readable storage medium having stored thereon executable instructions which, when executed by a processor, cause the processor to perform the method according to any of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111329926.1A CN113992680B (en) | 2021-11-10 | 2021-11-10 | Scheduling method, device, equipment and medium applied to distributed multi-activity system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111329926.1A CN113992680B (en) | 2021-11-10 | 2021-11-10 | Scheduling method, device, equipment and medium applied to distributed multi-activity system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113992680A CN113992680A (en) | 2022-01-28 |
| CN113992680B true CN113992680B (en) | 2024-02-02 |
Family
ID=79747823
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111329926.1A Active CN113992680B (en) | 2021-11-10 | 2021-11-10 | Scheduling method, device, equipment and medium applied to distributed multi-activity system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113992680B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115292280A (en) * | 2022-07-28 | 2022-11-04 | 天翼云科技有限公司 | Cross-region data scheduling method, device, equipment and storage medium |
| CN115396302B (en) * | 2022-08-11 | 2024-01-30 | 臻乐尔科技服务(上海)有限公司 | Multi-node high-availability configuration distribution system and working method thereof |
| CN115391215B (en) * | 2022-08-31 | 2023-11-17 | 江苏安超云软件有限公司 | Method and application for full link debugging under micro-service architecture |
| CN117453150B (en) * | 2023-12-25 | 2024-04-05 | 杭州阿启视科技有限公司 | Method for implementing multiple instances of video storage scheduling service |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104506614A (en) * | 2014-12-22 | 2015-04-08 | 国家电网公司 | Design method for distributed multi-activity data center based on cloud computing |
| CN106980625A (en) * | 2016-01-18 | 2017-07-25 | 阿里巴巴集团控股有限公司 | A kind of method of data synchronization, apparatus and system |
| CN111953780A (en) * | 2020-08-13 | 2020-11-17 | 中国工商银行股份有限公司 | Micro-service gray level publishing method, device, equipment, system and storage medium |
| CN112671882A (en) * | 2020-12-18 | 2021-04-16 | 上海安畅网络科技股份有限公司 | Same-city double-activity system and method based on micro-service |
| CN113190625A (en) * | 2021-05-25 | 2021-07-30 | 中国工商银行股份有限公司 | Request processing method, device, electronic equipment, medium and program product |
| WO2021197432A1 (en) * | 2020-04-02 | 2021-10-07 | 北京京东振世信息技术有限公司 | Routing method and apparatus for database cluster |
-
2021
- 2021-11-10 CN CN202111329926.1A patent/CN113992680B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104506614A (en) * | 2014-12-22 | 2015-04-08 | 国家电网公司 | Design method for distributed multi-activity data center based on cloud computing |
| CN106980625A (en) * | 2016-01-18 | 2017-07-25 | 阿里巴巴集团控股有限公司 | A kind of method of data synchronization, apparatus and system |
| WO2021197432A1 (en) * | 2020-04-02 | 2021-10-07 | 北京京东振世信息技术有限公司 | Routing method and apparatus for database cluster |
| CN111953780A (en) * | 2020-08-13 | 2020-11-17 | 中国工商银行股份有限公司 | Micro-service gray level publishing method, device, equipment, system and storage medium |
| CN112671882A (en) * | 2020-12-18 | 2021-04-16 | 上海安畅网络科技股份有限公司 | Same-city double-activity system and method based on micro-service |
| CN113190625A (en) * | 2021-05-25 | 2021-07-30 | 中国工商银行股份有限公司 | Request processing method, device, electronic equipment, medium and program product |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113992680A (en) | 2022-01-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN113992680B (en) | Scheduling method, device, equipment and medium applied to distributed multi-activity system | |
| US20200136921A1 (en) | Methods, system, articles of manufacture, and apparatus to manage telemetry data in an edge environment | |
| US10001821B2 (en) | Cloud management with power management support | |
| US8862720B2 (en) | Flexible cloud management including external clouds | |
| US9450783B2 (en) | Abstracting cloud management | |
| US20160328258A1 (en) | Management system, overall management node, and management method | |
| US20190065234A1 (en) | Network function virtualization management and orchestration apparatus, method, and program | |
| US20180075152A1 (en) | Containerization of network services | |
| Kumar et al. | Distributed stream management using utility-driven self-adaptive middleware | |
| Cheng et al. | Geelytics: Geo-distributed edge analytics for large scale iot systems based on dynamic topology | |
| CN112035213B (en) | Multi-tenant network car booking system and dynamic isolation method | |
| AU2014209611B2 (en) | Instance host configuration | |
| US20110055377A1 (en) | Methods and systems for automated migration of cloud processes to external clouds | |
| EP3915022A1 (en) | Transformation configuration in instance data replication with bi-directional replication support | |
| CN107534570A (en) | Virtualize network function monitoring | |
| US20150244769A1 (en) | Content delivery system | |
| US11005718B2 (en) | Determining capabilities of cognitive entities in a distributed network based on application of cognitive protocols | |
| CN112035214B (en) | Multi-tenant isolated driver and passenger matching method and system | |
| US10826842B2 (en) | Third-party network computing resource management | |
| CN114189425A (en) | Intent-based distributed alert service | |
| US20180227241A1 (en) | Dynamically adaptive cloud computing infrastructure | |
| US10614018B2 (en) | Managing a set of compute nodes which have different configurations in a stream computing environment | |
| US20140068042A1 (en) | Method and Apparatus for Accelerated Virtual Image Provisioning in Distributed Cloud Environments | |
| US20200259714A1 (en) | Third-party network computational resource utilization | |
| Rocha et al. | CNS-AOM: design, implementation and integration of an architecture for orchestration and management of cloud-network slices |
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 |