CN111045802A - Redis cluster component scheduling system and method and platform device - Google Patents
Redis cluster component scheduling system and method and platform device Download PDFInfo
- Publication number
- CN111045802A CN111045802A CN201911152645.6A CN201911152645A CN111045802A CN 111045802 A CN111045802 A CN 111045802A CN 201911152645 A CN201911152645 A CN 201911152645A CN 111045802 A CN111045802 A CN 111045802A
- Authority
- CN
- China
- Prior art keywords
- tenant
- scheduling
- redis
- component
- layer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 84
- 230000008569 process Effects 0.000 claims abstract description 51
- 230000015654 memory Effects 0.000 claims description 21
- 238000012544 monitoring process Methods 0.000 claims description 11
- 238000002955 isolation Methods 0.000 claims description 9
- 238000007726 management method Methods 0.000 abstract description 18
- 238000012423 maintenance Methods 0.000 abstract description 7
- 230000000694 effects Effects 0.000 abstract description 4
- 238000013468 resource allocation Methods 0.000 abstract description 4
- 238000013461 design Methods 0.000 description 8
- 238000010586 diagram Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 6
- 230000005291 magnetic effect Effects 0.000 description 4
- 238000004891 communication Methods 0.000 description 3
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- 238000013523 data management Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
Abstract
The embodiment of the invention provides a Redis cluster component scheduling system, a Redis cluster component scheduling method and platform equipment, wherein the Redis cluster component management system comprises: the system comprises a component database, a tenant layer, a tenant scheduling framework, a resource scheduling framework and a resource layer. Firstly, a tenant layer acquires a Redis component from the component database; then the tenant scheduling framework pulls up the scheduling process according to the tenant identification of the tenant layer; finally, the resource scheduling framework calls the tenant resources of the resource layer according to the tenant roles corresponding to the tenant identifications, the tenant resources are allocated to the scheduling process to deploy Redis components, fine-grained dynamic resources of the tenants can be allocated, flexible resource allocation can be achieved, and the effects of saving resources and improving operation and maintenance efficiency can be achieved.
Description
Technical Field
The embodiment of the invention relates to the technical field of communication, in particular to a Redis cluster component scheduling system, a Redis cluster component scheduling method and platform equipment.
Background
Redis is a storage database of open sources, supporting networks and key values based on internal memories, supports various data types and operations, has a strong function of managing data, and is widely applied to business scenes such as cache, message queues and leaderboard. As the importance of data increases, the requirements for data management, maintenance and security become more and more important, and how to efficiently and safely manage Redis is urgently needed.
In the existing platform technical scheme, the management function of the Redis cluster is already realized.
However, the existing platform lacks support for multi-tenant capability of the Redis cluster, and one node of the existing Redis cluster occupies one host, which causes serious problems of resource waste and low operation and maintenance efficiency.
Disclosure of Invention
The embodiment of the invention provides a Redis cluster component scheduling system and method and platform equipment, and aims to solve the problems that in the prior art, one node of a Redis cluster occupies one host, so that serious resource waste and low operation and maintenance efficiency are caused.
In a first aspect, an embodiment of the present invention provides a system for scheduling a Redis cluster component, including:
the system comprises a component database, a tenant layer, a tenant scheduling framework, a resource scheduling framework and a resource layer;
the tenant layer acquires a Redis component from the component database;
the tenant scheduling framework pulls up a scheduling process according to the tenant identification of the tenant layer;
and the resource scheduling framework calls the tenant resources of the resource layer according to the tenant roles corresponding to the tenant identifications and allocates the tenant resources to the scheduling process for deploying the Redis component.
In one possible design, the tenant scheduling framework includes a plurality of Redis components pull scheduling processes;
the tenant scheduling framework pulls up a scheduling process according to the tenant identification of the tenant layer, and the method comprises the following steps:
and the tenant scheduling framework acquires the corresponding Redis component pull-up scheduling process according to the tenant identification of the tenant layer, and pulls up the scheduling process according to the Redis component pull-up scheduling process so as to ensure service isolation between tenants.
In one possible design, the tenant layer uploads a Redis main backup version specialized component and a Redis cluster version specialized component to a component database, so that the component database stores the Redis main backup version specialized component and the Redis cluster version specialized component.
In one possible design, the tenant layer includes: the system comprises three functional modules of instance operation, instance monitoring and user management.
In one possible design, the tenant scheduling framework is a Marathon scheduling framework, and the resource scheduling framework is a messs scheduling framework.
In a second aspect, an embodiment of the present invention provides a method for scheduling a Redis cluster component, which is applied to a Redis cluster component management system, where the system includes a component database, a tenant layer, a tenant scheduling framework, a resource scheduling framework, and a resource layer;
the method comprises the following steps:
the tenant layer acquires a Redis component from the component database;
the tenant scheduling framework pulls up a scheduling process according to the tenant identification of the tenant layer;
and the resource scheduling framework calls the tenant resources of the resource layer according to the tenant roles corresponding to the tenant identifications and allocates the tenant resources to the scheduling process for deploying the Redis component.
In one possible design, the tenant scheduling framework includes a plurality of Redis components pull scheduling processes;
the tenant scheduling framework pulls up a scheduling process according to the tenant identification of the tenant layer, and the method comprises the following steps:
and the tenant scheduling framework acquires the corresponding Redis component pull-up scheduling process according to the tenant identification of the tenant layer, and pulls up the scheduling process according to the Redis component pull-up scheduling process so as to ensure service isolation between tenants.
In one possible design, the tenant layer uploads a Redis main backup version specialized component and a Redis cluster version specialized component to a component database, so that the component database stores the Redis main backup version specialized component and the Redis cluster version specialized component.
In one possible design, the tenant layer includes: the system comprises three functional modules of instance operation, instance monitoring and user management.
In one possible design, the tenant scheduling framework is a Marathon scheduling framework, and the resource scheduling framework is a messs scheduling framework.
In a third aspect, an embodiment of the present invention provides a platform device, including: at least one processor and memory;
the memory stores computer-executable instructions;
the at least one processor executing the memory-stored computer-executable instructions causes the at least one processor to perform the Redis cluster component scheduling method of any of the second aspect and the second aspect.
The Redis cluster component management system comprises a component database, a tenant layer, a tenant scheduling framework, a resource scheduling framework and a resource layer. Firstly, a tenant layer acquires a Redis component from the component database; then the tenant scheduling framework pulls up the scheduling process according to the tenant identification of the tenant layer; finally, the resource scheduling framework calls the tenant resources of the resource layer according to the tenant roles corresponding to the tenant identifications, the tenant resources are allocated to the scheduling process to deploy Redis components, fine-grained dynamic resources of the tenants can be allocated, flexible resource allocation can be achieved, and the effects of saving resources and improving operation and maintenance efficiency can be achieved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a schematic architecture diagram of a Redis cluster component scheduling system according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a Redis cluster component management system according to an embodiment of the present invention;
fig. 3 is a schematic flowchart of a method for scheduling a Redis cluster component according to an embodiment of the present invention;
fig. 4 is a schematic diagram of a hardware structure of a platform device according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, but not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Referring to fig. 1, fig. 1 is a schematic structural diagram of a Redis cluster component scheduling system according to an embodiment of the present invention. As shown in fig. 1, the system provided by the present embodiment includes:
a component database 101, a tenant layer 102, a tenant scheduling framework 103, a resource scheduling framework 104, and a resource layer 105.
The tenant layer 102 obtains the Redis component from the component database 101.
The tenant scheduling framework 103 pulls up the scheduling process according to the tenant identification of the tenant layer 102.
The resource scheduling framework 104 calls the tenant resources of the resource layer 1056 according to the tenant roles corresponding to the tenant identities, and allocates the tenant resources to the scheduling process to deploy the Redis component.
In this embodiment, the component database 101 may be referred to as a component repository for encapsulating Redis programs. Specifically, the Redis main and standby version program and the Redis cluster version program are respectively packaged into a Redis main and standby version specialized component and a Redis cluster version specialized component.
In this embodiment, the tenant layer 102 may be configured to manage a plurality of corresponding Redis tenants isolated from each other, and acquire a corresponding Redis component from the component database 101 according to a user instruction.
In this embodiment, the tenant scheduling framework 103 may be a Marathon scheduling framework. The resource scheduling framework 104 may be a Mesos scheduling framework.
In this embodiment, the resource layer 105 includes physical machines and virtual machines, including network, storage, and processing performance parameters of the physical machines and the virtual machines.
As can be known from the description of the foregoing embodiment, the Redis cluster component management system provided in this embodiment includes a component database, a tenant layer, a tenant scheduling framework, a resource scheduling framework, and a resource layer. Firstly, a tenant layer acquires a Redis component from the component database; then the tenant scheduling framework pulls up the scheduling process according to the tenant identification of the tenant layer; finally, the resource scheduling framework calls the tenant resources of the resource layer according to the tenant roles corresponding to the tenant identifications, the tenant resources are allocated to the scheduling process to deploy Redis components, fine-grained dynamic resources of the tenants can be allocated, flexible resource allocation can be achieved, and the effects of saving resources and improving operation and maintenance efficiency can be achieved.
In one embodiment of the invention, the tenant scheduling framework comprises a plurality of Redis components pull scheduling processes;
the tenant scheduling framework pulls up a scheduling process according to the tenant identification of the tenant layer, and the method comprises the following steps:
and the tenant scheduling framework acquires the corresponding Redis component pull-up scheduling process according to the tenant identification of the tenant layer, and pulls up the scheduling process according to the Redis component pull-up scheduling process so as to ensure service isolation between tenants.
In this embodiment, the tenant scheduling framework may be a Marathon scheduling framework.
Service isolation between tenants can be realized through the Marathon scheduling framework, and the safety and the service isolation of data between the tenants are ensured.
In an embodiment of the present invention, a user of a tenant layer may upload a Redis master backup specialized component and a Redis cluster backup specialized component to a component database, so that the component database stores the Redis master backup specialized component and the Redis cluster backup specialized component.
The Redis main and standby version specialized components and the Redis cluster version specialized components are uploaded and stored in the component database, so that the fire rate of the deployed components can be obtained, and the complicated operation process of manually creating the components is avoided.
Referring to fig. 2, fig. 2 is a schematic structural diagram of a Redis cluster component management system according to an embodiment of the present invention.
In one embodiment of the invention, a Redis cluster component management system comprises: a user layer 201, a Redis tenant layer 202, and a DC/OS (data center operating system) layer 203.
The DC/OS layer is the bottom layer, the DC/OS is used as a data center operating system with the functions of resource sharing, data sharing, service administration and arrangement and application monitoring, two-stage fine-grained scheduling is carried out on hardware resources of the data center by using the facilities, service arrangement and management are carried out through the Marathon, load balancing of services is achieved through the Marathon-lb, the Redis specialized component is stored in the component warehouse, and rapid one-key deployment is conveniently achieved. The DC/OS layer provides basic resources such as CPU, network and storage in a mode of distribution as required, dynamic scheduling and elastic expansion, provides an interface for an upper Redis tenant layer to apply for the resources, and realizes unified scheduling management of components, containers and the like.
The Redis tenant layer mainly provides various operations of Redis components, the function module of Redis service is arranged at the top layer, the Redis components are operated through instance operation, instance monitoring and user management modules, resource sharing and data isolation among tenants are achieved through a DCOS, a scheduling framework and an ETCD are information storage modules of the Redis tenant layer, the operations performed by the Redis service are stored into the ETCD through the scheduling framework, and the tenants can conveniently perform data information query.
And the user layer is used for realizing tenant authentication and authority distribution by calling an interface of the Redis tenant layer. Redis is provided in a component form, one-key deployment can be realized, application use efficiency is improved, and personalized application environment deployment is better supported.
The functions that the Redis tenant layer can realize include three major modules as follows:
instance operations, instance monitoring, and user management.
The instance operation module mainly covers functions of one-key deployment of instances, instance deletion, instance expansion, resource modification, instance details, data backup, parameter configuration and Keys statistics.
The example monitoring module mainly comprises a monitoring panel, example monitoring, an operation log and slow log display query
And the user management module correspondingly creates a user, deletes the user, distributes the authority and logs in the user.
Referring to fig. 3, fig. 3 is a schematic flowchart of a method for scheduling a Redis cluster component according to an embodiment of the present invention. The Redis cluster component scheduling method is applied to an edis cluster component management system, and the system comprises a component database, a tenant layer, a tenant scheduling framework, a resource scheduling framework and a resource layer;
the method comprises the following steps:
s301: and the tenant layer acquires the Redis component from the component database.
S302: and the tenant scheduling framework pulls up a scheduling process according to the tenant identification of the tenant layer.
S303: and the resource scheduling framework calls the tenant resources of the resource layer according to the tenant roles corresponding to the tenant identifications and allocates the tenant resources to the scheduling process for deploying the Redis component.
As can be known from the description of the foregoing embodiment, the Redis cluster component management system provided in this embodiment includes a component database, a tenant layer, a tenant scheduling framework, a resource scheduling framework, and a resource layer. Firstly, a tenant layer acquires a Redis component from the component database; then the tenant scheduling framework pulls up the scheduling process according to the tenant identification of the tenant layer; finally, the resource scheduling framework calls the tenant resources of the resource layer according to the tenant roles corresponding to the tenant identifications, the tenant resources are allocated to the scheduling process to deploy Redis components, fine-grained dynamic resources of the tenants can be allocated, flexible resource allocation can be achieved, and the effects of saving resources and improving operation and maintenance efficiency can be achieved.
In one embodiment of the invention, the tenant scheduling framework comprises a plurality of Redis components pull scheduling processes;
the tenant scheduling framework pulls up a scheduling process according to the tenant identification of the tenant layer, and the method comprises the following steps:
and the tenant scheduling framework acquires the corresponding Redis component pull-up scheduling process according to the tenant identification of the tenant layer, and pulls up the scheduling process according to the Redis component pull-up scheduling process so as to ensure service isolation between tenants.
In an embodiment of the present invention, the tenant layer uploads a Redis master backup specialized component and a Redis cluster backup specialized component to a component database, so that the component database stores the Redis master backup specialized component and the Redis cluster backup specialized component.
In one embodiment of the present invention, the tenant layer comprises: the system comprises three functional modules of instance operation, instance monitoring and user management.
In one embodiment of the invention, the tenant scheduling framework is a Marathon scheduling framework, and the resource scheduling framework is a meso scheduling framework.
Referring to fig. 4, fig. 4 is a schematic diagram of a hardware structure of a platform device according to an embodiment of the present invention. As shown in fig. 4, the stage device 40 of the present embodiment includes: a processor 401 and a memory 402; wherein
A memory 402 for storing computer-executable instructions;
Alternatively, the memory 402 may be separate or integrated with the processor 401.
When the memory 402 is provided separately, the platform device further includes a bus 403 for connecting the memory 402 and the processor 401.
An embodiment of the present invention further provides a computer-readable storage medium, where a computer execution instruction is stored in the computer-readable storage medium, and when a processor executes the computer execution instruction, the method for scheduling a Redis cluster component as described above is implemented.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules is only one logical division, and other divisions may be realized in practice, for example, a plurality of modules may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to implement the solution of the present embodiment.
In addition, functional modules in the embodiments of the present invention may be integrated into one processing unit, or each module may exist alone physically, or two or more modules are integrated into one unit. The unit formed by the modules can be realized in a hardware form, and can also be realized in a form of hardware and a software functional unit.
The integrated module implemented in the form of a software functional module may be stored in a computer-readable storage medium. The software functional module is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) or a processor to execute some steps of the methods described in the embodiments of the present application.
It should be understood that the Processor may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), etc. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present invention may be embodied directly in a hardware processor, or in a combination of the hardware and software modules within the processor.
The memory may comprise a high-speed RAM memory, and may further comprise a non-volatile storage NVM, such as at least one disk memory, and may also be a usb disk, a removable hard disk, a read-only memory, a magnetic or optical disk, etc.
The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (Extended Industry Standard Architecture) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, the buses in the figures of the present application are not limited to only one bus or one type of bus.
The storage medium may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.
An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. Of course, the storage medium may also be integral to the processor. The processor and the storage medium may reside in an Application Specific Integrated Circuits (ASIC). Of course, the processor and the storage medium may reside as discrete components in an electronic device or host device.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The program may be stored in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Finally, it should be noted that: the above embodiments are only used to illustrate the technical solution of the present invention, and not to limit the same; while the invention has been described in detail and with reference to the foregoing embodiments, it will be understood by those skilled in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present invention.
Claims (11)
1. A Redis cluster component scheduling system, comprising:
the system comprises a component database, a tenant layer, a tenant scheduling framework, a resource scheduling framework and a resource layer;
the tenant layer acquires a Redis component from the component database;
the tenant scheduling framework pulls up a scheduling process according to the tenant identification of the tenant layer;
and the resource scheduling framework calls the tenant resources of the resource layer according to the tenant roles corresponding to the tenant identifications and allocates the tenant resources to the scheduling process for deploying the Redis component.
2. The system in accordance with claim 1, wherein the tenant scheduling framework comprises a plurality of Redis component pull scheduling processes;
the tenant scheduling framework pulls up a scheduling process according to the tenant identification of the tenant layer, and the method comprises the following steps:
and the tenant scheduling framework acquires the corresponding Redis component pull-up scheduling process according to the tenant identification of the tenant layer, and pulls up the scheduling process according to the Redis component pull-up scheduling process so as to ensure service isolation between tenants.
3. The system of claim 1,
and uploading Redis main and standby version specialized components and Redis cluster version specialized components to a component database by the tenant layer, so that the component database stores the Redis main and standby version specialized components and the Redis cluster version specialized components.
4. The system of claim 1, wherein the tenant layer comprises: the system comprises three functional modules of instance operation, instance monitoring and user management.
5. The system according to any one of claims 1 to 4, wherein the tenant scheduling framework is a Marathon scheduling framework, and the resource scheduling framework is a Mesos scheduling framework.
6. A Redis cluster component scheduling method is characterized by being applied to a Redis cluster component management system, wherein the system comprises a component database, a tenant layer, a tenant scheduling framework, a resource scheduling framework and a resource layer;
the method comprises the following steps:
the tenant layer acquires a Redis component from the component database;
the tenant scheduling framework pulls up a scheduling process according to the tenant identification of the tenant layer;
and the resource scheduling framework calls the tenant resources of the resource layer according to the tenant roles corresponding to the tenant identifications and allocates the tenant resources to the scheduling process for deploying the Redis component.
7. The method in accordance with claim 6, wherein the tenant scheduling framework comprises a plurality of Redis component pull scheduling processes;
the tenant scheduling framework pulls up a scheduling process according to the tenant identification of the tenant layer, and the method comprises the following steps:
and the tenant scheduling framework acquires the corresponding Redis component pull-up scheduling process according to the tenant identification of the tenant layer, and pulls up the scheduling process according to the Redis component pull-up scheduling process so as to ensure service isolation between tenants.
8. The method of claim 6, further comprising:
and uploading Redis main and standby version specialized components and Redis cluster version specialized components to a component database by the tenant layer, so that the component database stores the Redis main and standby version specialized components and the Redis cluster version specialized components.
9. The method of claim 6, wherein the tenant layer comprises: the system comprises three functional modules of instance operation, instance monitoring and user management.
10. The method according to any one of claims 6 to 9, wherein the tenant scheduling framework is a Marathon scheduling framework and the resource scheduling framework is a mess scheduling framework.
11. A platform apparatus, comprising: at least one processor and memory;
the memory stores computer-executable instructions;
the at least one processor executing the memory-stored computer-executable instructions cause the at least one processor to perform the Redis cluster component scheduling method of any of claims 6 to 10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911152645.6A CN111045802B (en) | 2019-11-22 | 2019-11-22 | Redis cluster component scheduling system and method and platform equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911152645.6A CN111045802B (en) | 2019-11-22 | 2019-11-22 | Redis cluster component scheduling system and method and platform equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111045802A true CN111045802A (en) | 2020-04-21 |
| CN111045802B CN111045802B (en) | 2024-01-26 |
Family
ID=70231920
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911152645.6A Active CN111045802B (en) | 2019-11-22 | 2019-11-22 | Redis cluster component scheduling system and method and platform equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111045802B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112463828A (en) * | 2020-11-02 | 2021-03-09 | 马上消费金融股份有限公司 | Data processing method, device, equipment, system and readable storage medium |
| CN112783611A (en) * | 2021-01-29 | 2021-05-11 | 紫光云技术有限公司 | Universal configurable method for preparing cloud database Redis instance resources |
| CN114567555A (en) * | 2022-03-04 | 2022-05-31 | 浪潮云信息技术股份公司 | Cloud-based method and system for automatically acquiring slow logs by Redis cluster |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101652787A (en) * | 2007-03-30 | 2010-02-17 | 微软公司 | In-memory caching of shared customizable multi-tenant data |
| CN103077024A (en) * | 2012-12-28 | 2013-05-01 | 山东地纬计算机软件有限公司 | Device and method for supporting customization and running of software-as-a-service (SaaS) application processes |
| US20140215057A1 (en) * | 2013-01-28 | 2014-07-31 | Rackspace Us, Inc. | Methods and Systems of Monitoring Failures in a Distributed Network System |
| CN106952010A (en) * | 2017-01-04 | 2017-07-14 | 国家电网公司 | A kind of demand response system and method based on multi-tenant technology |
| CN107896250A (en) * | 2017-11-16 | 2018-04-10 | 优公里（北京）网络技术有限公司 | A kind of method of the multi-tenant data dynamic migration based on SaaS |
| CN108810164A (en) * | 2018-06-29 | 2018-11-13 | 合肥微商圈信息科技有限公司 | A kind of device for supporting the on-demand customization of SaaS application flows and operation |
| CN108829507A (en) * | 2018-03-30 | 2018-11-16 | 北京百度网讯科技有限公司 | The resource isolation method, apparatus and server of distributed data base system |
| CN110362390A (en) * | 2019-06-06 | 2019-10-22 | 银江股份有限公司 | A kind of distributed data integrated operations dispatching method and device |
-
2019
- 2019-11-22 CN CN201911152645.6A patent/CN111045802B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101652787A (en) * | 2007-03-30 | 2010-02-17 | 微软公司 | In-memory caching of shared customizable multi-tenant data |
| CN103077024A (en) * | 2012-12-28 | 2013-05-01 | 山东地纬计算机软件有限公司 | Device and method for supporting customization and running of software-as-a-service (SaaS) application processes |
| US20140215057A1 (en) * | 2013-01-28 | 2014-07-31 | Rackspace Us, Inc. | Methods and Systems of Monitoring Failures in a Distributed Network System |
| CN106952010A (en) * | 2017-01-04 | 2017-07-14 | 国家电网公司 | A kind of demand response system and method based on multi-tenant technology |
| CN107896250A (en) * | 2017-11-16 | 2018-04-10 | 优公里（北京）网络技术有限公司 | A kind of method of the multi-tenant data dynamic migration based on SaaS |
| CN108829507A (en) * | 2018-03-30 | 2018-11-16 | 北京百度网讯科技有限公司 | The resource isolation method, apparatus and server of distributed data base system |
| CN108810164A (en) * | 2018-06-29 | 2018-11-13 | 合肥微商圈信息科技有限公司 | A kind of device for supporting the on-demand customization of SaaS application flows and operation |
| CN110362390A (en) * | 2019-06-06 | 2019-10-22 | 银江股份有限公司 | A kind of distributed data integrated operations dispatching method and device |
Non-Patent Citations (2)
| Title |
|---|
| YUE CHENG 等: "An in-memory object caching framework with adaptive load balancing", 《PROCEEDINGS OF TENTH EUROPEAN CONFERENCE ON COMPUTER SYSTEM》, pages 1 - 16 * |
| 李战: "基于Docker 的容 器集群调度机制的设计与实现", 《中国优秀硕士学位论文全 文数据库》, pages 139 - 91 * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112463828A (en) * | 2020-11-02 | 2021-03-09 | 马上消费金融股份有限公司 | Data processing method, device, equipment, system and readable storage medium |
| CN112783611A (en) * | 2021-01-29 | 2021-05-11 | 紫光云技术有限公司 | Universal configurable method for preparing cloud database Redis instance resources |
| CN114567555A (en) * | 2022-03-04 | 2022-05-31 | 浪潮云信息技术股份公司 | Cloud-based method and system for automatically acquiring slow logs by Redis cluster |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111045802B (en) | 2024-01-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109274731B (en) | Method and device for deploying and calling web service based on multi-tenant technology | |
| US9984648B2 (en) | Delivering GPU resources to a migrating virtual machine | |
| US9110806B2 (en) | Opportunistic page caching for virtualized servers | |
| CN111045802A (en) | Redis cluster component scheduling system and method and platform device | |
| CN106776067B (en) | Method and device for managing system resources in multi-container system | |
| US20140372790A1 (en) | System and method for assigning memory available for high availability failover to virtual machines | |
| CN111538561B (en) | OpenStack large-scale cluster deployment test method and system based on KVM virtualization technology | |
| US9836516B2 (en) | Parallel scanners for log based replication | |
| EP4030289A1 (en) | Method and device for virtual machine memory management | |
| CN113626286A (en) | Multi-cluster instance processing method and device, electronic equipment and storage medium | |
| CN111857977B (en) | Elastic expansion method, device, server and storage medium | |
| CN110502392A (en) | Cloud platform management and monitoring system | |
| CN113986449A (en) | Container-oriented Linux kernel virtualization system and method | |
| CN102981888A (en) | Virtualization implementing method for Power server | |
| WO2023016414A1 (en) | Credential rotation method, computing device, and storage medium | |
| CN113254156A (en) | Container group deployment method and device, electronic equipment and storage medium | |
| CN112491980A (en) | Cloud host service management method, system, terminal and storage medium | |
| CN110795202A (en) | Resource allocation method and device of virtualized cluster resource management system | |
| CN113626150A (en) | Elastic container example implementation method | |
| CN114503438A (en) | Semi-decoupled partitioning for video coding and decoding | |
| CN114661420B (en) | Application protection method, device and system based on Kubernetes container platform | |
| US11709749B1 (en) | Diagnostic data collection for kubernetes | |
| CN115328608A (en) | Kubernetes container vertical expansion adjusting method and device | |
| CN114168156A (en) | Multi-tenant data persistence method and device, storage medium and computer equipment | |
| CN110401652B (en) | Digital media data processing method based on super-fusion storage |
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 |