CN113760940A - Quota management method, device, equipment and medium applied to distributed system - Google Patents
Quota management method, device, equipment and medium applied to distributed system Download PDFInfo
- Publication number
- CN113760940A CN113760940A CN202011018956.6A CN202011018956A CN113760940A CN 113760940 A CN113760940 A CN 113760940A CN 202011018956 A CN202011018956 A CN 202011018956A CN 113760940 A CN113760940 A CN 113760940A
- Authority
- CN
- China
- Prior art keywords
- per
- quota
- client
- query rate
- slave node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000007726 management method Methods 0.000 title claims abstract description 69
- 238000000034 method Methods 0.000 claims description 25
- 230000000694 effects Effects 0.000 abstract description 15
- 239000002699 waste material Substances 0.000 abstract description 10
- 238000010586 diagram Methods 0.000 description 9
- 238000012545 processing Methods 0.000 description 9
- 230000003287 optical effect Effects 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 230000008901 benefit Effects 0.000 description 4
- 230000008859 change Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 2
- 238000013507 mapping Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 230000008602 contraction Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000008707 rearrangement Effects 0.000 description 1
- 239000004065 semiconductor Substances 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
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Abstract
The embodiment of the invention provides a quota management method, a quota management device, quota management equipment and quota management media applied to a distributed system, wherein the quota management method is applied to slave node services and comprises the following steps: when request information sent by a current client is received, acquiring a client per second query rate quota corresponding to the current client; the query rate quota per second of the client is determined by the master node service according to a node query rate quota per second range reported by the current slave node service and a registered query rate quota per second registered by the client associated with the current slave node service; and performing query rate quota per second control on the access client according to the query rate quota per second of the client and the used query rate quota per second. The technical scheme of the embodiment of the invention solves the problems of unreasonable quota allocation and resource waste caused by the fact that the quota of each node cannot be effectively managed at present, and realizes the technical effect of effectively managing and controlling quota resources.
Description
Technical Field
The embodiment of the invention relates to the technical field of computers, in particular to a quota management method, device, equipment and medium applied to a distributed system.
Background
In order to provide mass data storage, HBase is typically employed as a distributed database. The HBase distributed database can realize concurrent access of a plurality of devices. In practical applications, a corresponding quota may be allocated to each node, so that when request information is received, the request information is processed based on the allocated quota.
In the process of implementing the invention, the inventor finds that the prior art has the following problems:
at present, although a corresponding quota can be allocated to each node, the allocated quota is randomly allocated and cannot be effectively managed for each node, so that the quota allocation is unreasonable and the problem of resource waste exists.
Disclosure of Invention
The invention provides a quota management method, a quota management device, quota management equipment and a quota management medium applied to a distributed system, which are used for realizing the technical effects of effectively managing a quota and avoiding resource waste.
In a first aspect, an embodiment of the present invention provides a quota management method applied to a distributed system, where the method is applied to a slave node service, and includes:
receiving request information sent by a current client, and acquiring a client per second query rate quota corresponding to the current client; the query rate quota per second of the client is determined by the master node service according to a node query rate quota per second range reported by the current slave node service and a registered query rate quota per second registered by the client associated with the current slave node service;
and managing and controlling the data access request sent by the current client according to the query rate quota per second of the client and the used query rate quota per second.
In a second aspect, an embodiment of the present invention further provides a quota management method applied to a distributed system, where the method is applied to a master node service, and includes:
for each slave node service, determining a node query rate quota per second corresponding to the current slave node service according to a received node query rate quota per second range reported by the current slave node service;
according to the node query rate per second quota corresponding to the current slave node service and the registered query rate per second quota registered by the client associated with the current slave node service, determining the client query rate per second quota of each client associated with the current slave node service, so that the current slave node service acquires the client query rate per second quota, and performing query rate quota per second control on the request information received by the current slave node service according to the client query rate quota per second.
In a third aspect, an embodiment of the present invention further provides a quota management apparatus applied to a distributed system, where the apparatus is configured in a slave node service, and includes:
the client query rate per second quota acquisition module is used for receiving request information sent by a current client and acquiring a client query rate per second quota corresponding to the current client; the query rate quota per second of the client is determined by the master node service according to a node query rate quota per second range reported by the current slave node service and a registered query rate quota per second registered by the client associated with the current slave node service;
and the quota control module is used for managing and controlling the data access request sent by the current client according to the query rate quota per second of the client and the used query rate quota per second.
In a fourth aspect, an embodiment of the present invention further provides a quota management apparatus applied to a distributed system, where the apparatus is configured in a master node service, and includes:
the node query rate quota per second determining module is used for determining a node query rate quota per second corresponding to the current slave node service according to a received node query rate quota per second range reported by the current slave node service aiming at each slave node service;
the client query rate quota per second determination module is used for determining client query rate quotas per second of each client associated with the current slave node service according to the node query rate quota per second corresponding to the current slave node service and the registered query rate quotas per second registered by the client associated with the current slave node service, so that the current slave node service acquires the client query rate quotas per second, and performs query rate quota per second control on request information received by the current slave node service according to the client query rate quotas per second.
In a fifth aspect, an embodiment of the present invention further provides an electronic device, where the electronic device includes:
one or more processors;
a storage device for storing one or more programs,
when the one or more programs are executed by the one or more processors, the one or more processors implement a quota management method applied to a distributed system according to any of the embodiments of the present invention.
In a sixth aspect, embodiments of the present invention further provide a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform a quota management method applied to a distributed system according to any of the embodiments of the present invention.
According to the technical scheme of the embodiment of the invention, after the query rate quota per second range pre-registered by the slave node service is registered to the master node service, the master node service can periodically determine the query rate quota per second of the nodes corresponding to each slave node and the query rate quota per second of the client side of each client side associated with each slave node, and send the query rate quota per second of the client side to the slave node service, so that the slave node service and the query rate quota per second of the client side are effectively controlled, and the technical effect of avoiding resource waste is achieved.
Drawings
In order to more clearly illustrate the technical solutions of the exemplary embodiments of the present invention, a brief description is given below of the drawings used in describing the embodiments. It should be clear that the described figures are only views of some of the embodiments of the invention to be described, not all, and that for a person skilled in the art, other figures can be derived from these figures without inventive effort.
Fig. 1 is a schematic flowchart of a quota management method applied to a distributed system according to a first embodiment of the present invention;
fig. 2 is a schematic flow chart of a quota management method applied to a distributed system according to a second embodiment of the present invention;
fig. 3 is a schematic flow chart of a quota management method applied to a distributed system according to a third embodiment of the present invention;
fig. 4 is a schematic flowchart of a quota management method applied to a distributed system according to a fourth embodiment of the present invention;
fig. 5 is a schematic diagram of a system architecture used when a master node service interacts with a slave node service according to a fifth embodiment of the present invention;
fig. 6 is a schematic structural diagram of a quota management apparatus applied to a distributed system according to a sixth embodiment of the present invention;
fig. 7 is a schematic structural diagram of a quota management apparatus applied to a distributed system according to a seventh embodiment of the present invention;
fig. 8 is a schematic structural diagram of an electronic device according to an eighth embodiment of the present invention.
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.
Example one
Fig. 1 is a schematic flow chart of a quota management method applied to a distributed system according to an embodiment of the present invention, where this embodiment may be executed by each slave node service associated with a master node service of the distributed system, and may be applicable to a case where a client query rate quota per second occupied by each client to the slave node service is determined.
As shown in fig. 1, the method of this embodiment includes:
s110, receiving request information sent by a current client, and acquiring a client per second query rate quota corresponding to the current client.
Wherein, the number of the slave node services can be multiple, and the number of the clients associated with each slave node service can be multiple. The request information may be read and write requests sent by one or more of the clients associated with the current slave node service. When the request information of the client is received from the node service, the query rate quota per second of the client corresponding to the client identifier can be obtained according to the client identifier of the client. Query Per Second (QPS) may be the number of queries that each service can respond to Per Second, which is a measure of how much traffic a particular Query server processes within a specified time. The QPS quota is a quota which is predetermined by the master node service and is issued to the slave node service. The client query rate per second quota is a quota corresponding to each client.
For the purpose of clearly describing the technical solution of the present embodiment, the solution may be described by taking a certain slave node as an example and a certain client as an example.
It should be noted that the number of clients associated with the current slave node service may include a plurality of clients, and a client corresponding to the request information when received may be a current client. The query rate quota per second corresponding to the current client may be used as the query rate quota per second for the client.
In this embodiment, determining the query rate quota per second for each client is determined by the master node service according to the query rate quota per second range for the node reported by the current slave node and the query rate quota per second for registration of the client registration associated with the current slave node service.
Specifically, when the slave node service is started, a standalone capability (QPS) of the current slave node may be registered in the master node service, that is, the master node service may receive a node query rate quota per second range reported by the slave node service. Meanwhile, the client can also register the client's query rate quota per second in the master node service. According to the total quota, the query rate quota per second of the slave nodes and the query rate quota per second of the registered client, the query rate quota per second of the nodes corresponding to the slave node service and the query rate quota per second of the client to each slave node service can be respectively determined. In this embodiment, the node query rate quota per second range registered in the current slave node service may be registered in advance in the master node service, so that the master node service determines, according to the node query rate quota per second range, the client query rate quota per second for each client associated with the current slave node service.
The slave node service is provided with a quota information reporting and updating component, and based on the quota information reporting and updating component, the local QPS capability pre-registered in the slave node service can be reported to the quota management component in the master node service. Meanwhile, the quota information reporting and updating component can also acquire the determined node per second query rate quota and the client per second query rate quota from the quota management component. The quota management component in the master node service can determine the query rate quota per second from the client to the client of the slave node service according to the received query rate quota per second range of the node, the query rate quota per second of the registered client and the total quota, and store the query rate quota per second so that the quota information reporting and updating component can acquire the determined quota information from the quota management component. The quota management component is arranged in the main node service and is mainly used for managing and counting all QPS (quantum per unit) capacities in the cluster in real time, and optionally quota used amount and quota total amount.
Specifically, a preset node query rate quota per second range in the current slave node service may be registered in the master node service based on the quota information reporting and updating component, and after the master node service receives the node query rate quota per second range reported by the slave node service, the client query rate quota per second of each client associated with the current slave node service may be determined.
In this embodiment, reporting the local QPS capability set in the current slave node service to the master node service has an advantage that a quota management component in the master node service can allocate a corresponding node query rate quota per second to the slave node service, and further determine a client query rate quota per second from each client to the slave node service.
In this embodiment, in order to determine the client query rate per second quota corresponding to each client, the following may be performed: and periodically acquiring the client query rate quota per second of each client associated with the current slave node service from the master node service.
Here, ten seconds may be taken as one period. During operation of the distributed system, situations may arise where the number of slave node services associated with the master node service is transmitting a change. When the number of the slave nodes changes, the query rate quota per second of the node allocated to the slave node service by the master node service also changes correspondingly, and correspondingly, the query rate quota per second of the client of each client associated with the slave node service also changes.
In order to facilitate timely determination of the client-side query rate quota per second of each client-side associated with the current slave node service, the client-side query rate quota per second of each client-side associated with the current slave node service can be periodically acquired from the quota management component of the master node service, so as to timely determine whether the received request information can be processed, and the technical effect of dynamically monitoring quotas is achieved.
And S120, managing and controlling the data access request sent by the current client according to the query rate quota per second of the client and the used query rate quota per second.
The used query rate quota per second is used for processing the sent request information. According to the client query rate quota per second and the used query rate quota per second obtained from the main node service, the remaining query rate quota per second can be determined, and based on the remaining query rate quota per second, query rate quota per second control can be performed on the access client, namely, the data access request sent by the current client is controlled.
Optionally, the controlling, according to the query rate quota per second and the used query rate quota per second of the client, the data access request sent by the current client includes: determining the current remaining per-second query rate quota according to the client per-second query rate quota and the per-second query rate quota used when the sent request information is processed; and performing quota control on the access client according to the current remaining query rate quota per second.
The client can send a read-write request to the slave node service, and when the slave node service receives read-write request information sent by the client, whether quota control is performed on the current client can be determined according to rate quota information inquired by the current client in the current slave node per second.
In this embodiment, the managing and controlling the data access request sent by the current client according to the current remaining query rate quota per second includes: acquiring a request amount per second query rate quota corresponding to the received request information; and if the current remaining per-second query rate quota is smaller than the request quantity per-second query rate quota, performing quota control on an access client, and sending feedback information to the client.
It should be noted that the client may send a plurality of pieces of read-write request information to the slave node service, and when processing the read-write request, a certain query rate quota per second may be occupied, and the remaining query rate quota per second may be determined according to the query rate quota per second occupied by the read-write request currently being processed and the query rate quota per second of the client corresponding to the current slave node service at the current client.
Specifically, if it is detected that the remaining query rate quota per second is smaller than the query rate quota per second of the requested amount, quota control may be performed on the access client, and feedback information is sent to the client, optionally, the request information is processed abnormally or the feedback information of the request is waited to be processed.
In this embodiment, the advantage of this kind of setting lies in, can effectively manage and control the rate quota per second of client, avoid the extravagant technical effect of resource.
According to the technical scheme of the embodiment of the invention, after the query rate quota per second range pre-registered by the slave node service is registered to the master node service, the master node service can periodically determine the query rate quota per second of the nodes corresponding to each slave node and the query rate quota per second of the client side of each client side associated with each slave node, and send the query rate quota per second of the client side to the slave node service, so that the slave node service and the query rate quota per second of the client side are effectively controlled, and the technical effect of avoiding resource waste is achieved.
Example two
As an optional embodiment of the foregoing embodiment, fig. 2 is a schematic flow chart of a quota management method applied to a distributed system according to a second embodiment of the present invention. The technical terms that are the same as or corresponding to the above embodiments are not repeated herein.
As shown in fig. 2, the method includes:
s210, registering the query rate per second capability of each slave node service in the master node service.
Specifically, a slave node service in the HBase cluster, that is, a node service responsible for providing data reading and writing to the outside, is started, and when the slave node service is started, a reporting and updating component based on the qualtapugin quota information in the slave node service registers in the master node service according to the locally configured single machine capability, that is, the preset query rate quota range per second of the node. That is, the node quota per second query rate range served by the slave node is registered in the hbsasemaster, that is, the Master node of the HBase cluster, and the Master node is responsible for coordinating the distribution of the RegionServer and the management Region in the cluster.
S220, periodically obtaining the client-side per second query rate quota of each client-side associated with the current slave node service from the master node service.
Specifically, the quota information reporting and updating module in the slave node service may periodically obtain, from a quota management component in the master node service, a per-second query rate quota of a client of each client associated with the current slave node service. For example, the capacity information that each client should have in the current node is obtained from the quota management component served by the master node every 1 min.
It should be noted that the master node service may determine, according to the range of the query rate per second quota reported by each slave node service, the query rate per second quota registered by the client, and the total quota, the query rate per second quota per second from each client to the client of the slave node service, and store the query rate per second quota to the quota management component of the master node service, so as to report and update quota information in the slave node service to obtain corresponding query rate per second quota information of the client.
And S230, updating the client quota mapping table in the content.
Specifically, after the quota information reporting and updating component of the node service acquires the query rate quota per second of the client, the query rate quota per second of the client can be updated in the slave node service, so that access control is performed on the client according to the updated query rate quota per second of the client. It should be noted that, when receiving the request information from the node service, the quota check module in the slave node service may check whether the requested quota of the client request information exceeds the remaining client quota in real time, and if so, feed back an operation that the request information is processed abnormally to the client.
That is to say, when the client sends the request information to the slave node service, the slave node service may determine a specific processing mode for the request information according to the requested volume per second query rate quota corresponding to the request information and the current capacity information, thereby achieving the technical problem of avoiding the query rate per second from being exceeded.
According to the technical scheme of the embodiment of the invention, after the query rate quota per second range pre-registered by the slave node service is registered to the master node service, the master node service can periodically determine the query rate quota per second of the nodes corresponding to each slave node and the query rate quota per second of the client side of each client side associated with each slave node, and send the query rate quota per second of the client side to the slave node service, so that the slave node service and the query rate quota per second of the client side are effectively controlled, and the technical effect of avoiding resource waste is achieved.
EXAMPLE III
Fig. 3 is a schematic flow chart of a quota management method applied to a distributed system according to a third embodiment of the present invention, where this embodiment may be executed by a master node service of the distributed system, and is suitable for a situation where query rate quota per second is effectively controlled, and the method may be executed by a quota management device applied to the distributed system, and the device may be implemented in a form of software and/or hardware.
As shown in fig. 1, the method of this embodiment includes:
s310, aiming at each slave node service, determining a node query rate quota per second corresponding to the current slave node service according to a received node query rate quota per second range reported by the current slave node service.
The Master node of the HBase cluster is responsible for coordinating the RegionServer in the cluster and managing the distribution of the Region in the cluster. In the process of practical application, in order to ensure that a reasonable node per second query rate quota is distributed to each slave node service, namely, quota aggregation and update are realized, the number of slave node services can be determined in real time, and the node per second query rate quota corresponding to each slave node service is determined according to the number of slave node services and the range of the node per second query rate quota.
In particular, the master node service may detect in real time whether a change in the number of slave node services with which it communicates has occurred. When detecting that the number of the slave nodes changes, the per-second query rate quota of each slave node service can be determined according to the per-second query rate quota range of the node reported by each slave node service, the changed number of the nodes, and the total per-second query rate quota. When the query rate quota per second of the slave node changes, the query rate quota per second of the clients associated with the slave node also changes correspondingly. According to the updated query rate quota per second of the nodes and the query rate quota per second range registered by the client in the master node service in advance, the query rate quota per second from each client to the client served by the slave node can be re-determined.
In this embodiment, whether the number of slave node services changes may be periodically determined, and then, the corresponding QPS and the client query rate per second quotas of the clients associated with the slave node services may be newly allocated to each slave node service. Optionally, the current slave node service quantity is periodically determined, and the node query rate quota per second for each slave node service and the client query rate quota per second associated with each slave node service are determined according to the current slave node service quantity.
In this embodiment, when detecting that the number of slave node services changes, determining, according to a received range of the query rate quota per second of the node reported by each slave node service, a query rate quota per second of the node corresponding to each changed slave node service includes: receiving heartbeat information periodically sent by each slave node service, and determining the service quantity of the current slave node if the quantity of the received heartbeat information changes within a preset time length; and determining the node query rate quota per second of each changed slave node service according to the current slave node service quantity, the total query rate quota per second and the node query rate quota per second range.
Where the periodicity may be that the slave node service sends heartbeat information to the master node service every ten seconds. The master node service may receive heartbeat information periodically transmitted by each slave node service, and based on the received heartbeat information, it may be determined whether a number of each slave node service associated with the master node service has changed. Optionally, when it is detected that the heartbeat information sent by a certain slave node service is not received within a certain time period, it indicates that the number of slave node services is changed. That is, the master node service may check the number of slave nodes in the current cluster every ten seconds. When it is detected that the number of slave nodes changes, the node query rate quota per second for each slave node service may be determined according to the total query rate quota per second, the pre-registered range of the node query rate quota per second, and the updated number of slave node services.
In this embodiment, the advantage of detecting the number of slave nodes is that the corresponding query rate quota per second and the query rate quota per second from the client to the client served by each slave node can be dynamically allocated to each slave node, that is, the technical effect of automatically summarizing and updating quotas is achieved.
Based on the above technical solution, it should be noted that, since the query rate quota per second of each client associated with each slave node service is to be determined, after the number of slave nodes changes and the query rate quota per second of each node corresponding to each slave node service is determined, the query rate quota per second of the client needs to be determined according to the query rate quota per second of the node served by the slave node and the query rate quota per second of the registered client.
Optionally, the determining, according to the query rate per second quota of the node corresponding to the current slave node service and the query rate per second quota per second registered by the client associated with the current slave node, the query rate per second quota per second of the client of each client associated with the current slave node service includes: acquiring a registration per second query rate quota pre-registered by each client; and determining the client query rate quota per second of each client associated with the current node according to the number of the current slave nodes, the node query rate quota per second corresponding to the changed current slave node service and the registered query rate quota per second of each client associated with the current client.
Before the client accesses the slave node service, the total query rate quota per second of the client can be registered in advance, that is, the query rate quota per second is registered. The current slave node number refers to the number of slave node services counted by the master node service every time heartbeat information is received. After the number of the slave node services changes, the query rate quota per second of the node corresponding to the slave node services also changes correspondingly, and the changed query rate quota per second can be used as the query rate quota per second of the node. The changed node query rate quota per second and the client query rate quota per second can be updated in the quota management component of the master node service, so that quota information of the slave node service can be reported and the component can be updated, the updated client query rate quota per second can be obtained from the quota management component, and then the access control can be performed on the client according to the client query rate quota per second in the slave node service, and the technical effect of effective quota control is achieved.
In the actual application process, when a certain slave node service fails or a new slave node service is added, the number of slave node services changes. According to the changed slave node service quantity of the nodes, the query rate quota per second from each client to each remaining node can be recalculated.
S320, determining the query rate quota per second of each client associated with the current slave node service according to the query rate quota per second of the node corresponding to the current slave node service and the query rate quota per second of the registration of the client associated with the current slave node service.
Wherein the number of slave node services associated with the master node service may comprise a plurality. For the purpose of clearly describing the technical solution of the present embodiment, a service of one of the slave nodes may be taken as an example for description. Other slave node services may also use the same processing.
The node query rate quota per second may be a node query rate quota per second that is re-determined and corresponds to each slave node service after receiving heartbeat information reported by each slave node service. When heartbeat information reported by each slave node service is received, the query rate quota per second of the node corresponding to the slave node service can be changed or not, and whether the change is related to the quantity of the received heartbeat information in a period of time or not is determined. Before the client sends the read-write request to the slave node service, the client also needs to register the query rate quota per second. The master node service can determine the query rate quota per second from each client to the client of the slave node service, namely the query rate quota per second of the client corresponding to the slave node service related to each client.
Specifically, the query rate quota per second of each client and the client corresponding to the current slave node service can be determined according to the query rate quota per second of the node corresponding to the current slave node service and the query rate quota per second of the registration pre-registered with the current slave node service to the associated client. After the query rate quota per second of the client is determined, the query rate quota per second of the client can be stored in a quota management component of the master node service, so that the slave node service periodically obtains the query rate quota per second of the client determined by the master node from the master node service.
It should be noted that, the slave node service may periodically obtain the updated query rate quota per second of the client from the master node service, and this has an advantage that the query rate quota per second of the client associated with each slave node service may be dynamically determined.
It should be further noted that, since the slave node service periodically sends heartbeat information to the master node service, the rate quota per second queried from each client to the client of the slave node service can be periodically determined and stored in the quota management component of the master node service. Since the slave node service also periodically acquires the client query rate quota per second from the quota management component, the technical effect of effectively managing quota information can be achieved.
According to the technical scheme of the embodiment of the invention, after the query rate quota per second range pre-registered by the slave node service is registered to the master node service, the master node service can periodically determine the query rate quota per second of the nodes corresponding to each slave node and the query rate quota per second of the client side of each client side associated with each slave node, and send the query rate quota per second of the client side to the slave node service, so that the slave node service and the query rate quota per second of the client side are effectively controlled, and the technical effect of avoiding resource waste is achieved.
Example four
As an optional embodiment of the foregoing embodiment, fig. 4 is a schematic flow chart of a quota management method applied to a distributed system according to a fourth embodiment of the present invention. The method can be applied to the master node service, and is used for redistributing the corresponding node query rate quota per second and the client query rate quota per second associated with the node to each slave node service according to the determined slave node service number. The technical terms that are the same as or corresponding to the above embodiments are not repeated herein.
As shown in fig. 4, the method includes:
and S410, acquiring the number of the slave node services.
Specifically, the slave node service may periodically send heartbeat information to the master node service, and the master node service may determine the number of slave node services associated with the master node service according to the heartbeat information received each time. Optionally, if the heartbeat information sent by a certain slave node is not received within a period of time, it is indicated that the slave node service fails, and accordingly, the number of slave node services changes.
S420, judging whether the number of the current slave nodes changes or not, if so, executing S430; if not, go to S410.
Specifically, after determining the current number of slave nodes served by the slave node according to the received heartbeat information, whether the number of current slave nodes changes may be determined according to the current number and the number of nodes determined when the heartbeat information was received last time.
For example, after receiving the heartbeat information, determining that the number of slave node services is 10, and optionally 8, the number of nodes determined when the heartbeat information was received last time may be obtained, and according to the current number of nodes and the number of nodes at last time, it may be determined that the number of the nodes has changed, and at this time, S430 may be performed; if it is detected that the number of the current slave nodes is not changed, the corresponding query rate quota per second may not be allocated to each slave node again, and the step returns to execute S410.
And S430, calculating the query rate quota per second from each client to the slave node service.
Specifically, when it is determined that the number of the current slave nodes changes, the quota of the service of each slave node also changes correspondingly, and meanwhile, the query rate quota per second of the client of each client associated with the slave node also changes correspondingly, and at this time, the query rate quota per second from each client to the slave node service may be calculated.
S440, updating the client quota mapping table in the memory.
Specifically, after determining the query rate quota per second of the client, the updated query rate quota per second of the client may be updated in a quota management component in the master node service. The quota reporting and updating component QuotaPlugin in the slave node service can periodically acquire the latest client quota information from the quota management component QuotaManager every ten seconds and update local content. The slave node service can use the quota reporting and updating component to acquire the client query rate quota per second from the quota management component of the master node service, so that quota control is performed on the client according to the client query rate quota per second.
According to the technical scheme of the embodiment of the invention, after the query rate quota per second range pre-registered by the slave node service is registered to the master node service, the master node service can periodically determine the query rate quota per second of the nodes corresponding to each slave node and the query rate quota per second of the client side of each client side associated with each slave node, and send the query rate quota per second of the client side to the slave node service, so that the slave node service and the query rate quota per second of the client side are effectively controlled, and the technical effect of avoiding resource waste is achieved.
EXAMPLE five
As an alternative embodiment of the foregoing embodiment, fig. 5 is a schematic diagram of a system architecture used when a master node service interacts with a slave node service according to a fifth embodiment of the present invention.
Reference may be made to fig. 5, in which the Master node in the hbsasemaster cluster is responsible for coordinating the regionservers in the cluster and managing the distribution of regions in the cluster. I.e. the master node service is responsible for coordinating the slave node services in the cluster. The region server slave node service, which may be understood as a slave node service of the HBase cluster, is responsible for providing data read and write (QPS service) to an external (client), i.e., a query rate quota per second service. And the Client service Client can send corresponding read-write requests to the slave nodes. The quota management component is arranged in the main node service and is used for managing and counting all the query rate quotas per second in the cluster in real time, wherein the query rate quotas per second comprise used amount, total amount and the like. The quota information reporting and updating component is arranged in each slave node service, and is used for sending a node per second query rate quota range locally registered by the slave node to the master node and acquiring the per second query rate capacity information which can be used by the client at the current slave node from the quota management component.
Specifically, when the slave node service RegionServer is started, the query rate quota range of the slave node per second of the node may be reported to the master node service based on the queraplugin in the slave node service, that is, the locally configured single machine capability (QPS write/get) is registered in the queramamanager management module in the master node service HMaster. The QuotaManager periodically checks the number of slave node services in the current cluster at regular intervals, optionally, ten seconds. According to the received query rate per second quota of the nodes served by the slave nodes, the number of the nodes and the query rate per second quota registered in advance by the client, the query rate per second quota per second from the client to each client served by the slave nodes can be determined. The slave node service can periodically acquire the redistributed quota of the query rate per second of the client from the QuotaManager in the master node service, and update the local memory. The slave node service can limit the read-write request quantity sent by the client according to the updated query rate quota per second of the client. Meanwhile, the slave node service also comprises an RpcQuotaCheck quota checking module which can determine whether the read-write request quantity sent by the client exceeds the query rate quota per second of the client according to the updated query rate per second of the client, if so, the excess part can be submitted, namely, the excess part can be fed back to the client, so that the client can automatically retry the excess part.
According to the technical scheme of the embodiment of the invention, the quota management component is arranged in the main node service, and the quota reporting and updating component is arranged in the slave node service, so that the quota total amount can be controlled based on the quota management component, and more accurate resource management and control are provided; meanwhile, the corresponding query rate quota per second can be dynamically adjusted according to the number of the slave node services, and the technical effect of convenience in expansion and contraction is achieved.
EXAMPLE six
Fig. 6 is a schematic structural diagram of a quota management apparatus applied to a distributed system according to a sixth embodiment of the present invention, where the apparatus is configured in a slave node service, and includes: a client query rate per second quota acquisition module 610 and a quota control module 620.
A query rate per second quota per second acquisition module 610 of the client, configured to receive request information sent by a current client, and acquire a query rate per second quota per second of the client corresponding to the current client; the query rate quota per second of the client is determined by the master node service according to a node query rate quota per second range reported by the current slave node service and a registered query rate quota per second registered by the client associated with the current slave node service; and the quota control module 620 is configured to manage and control the data access request sent by the current client according to the query rate quota per second of the client and the used query rate quota per second.
On the basis of the above technical solution, the apparatus further includes: and the node quota registration module is used for registering the node per second query rate quota range preset in the current slave node service into the master node service, so that the master node service determines the client per second query rate quota of each client associated with the current slave node service according to the node per second query rate quota range.
On the basis of the above technical solution, the client query rate quota per second acquisition module is further configured to periodically acquire, from the master node service, the client query rate quota per second of each client associated with the current slave node service.
On the basis of the technical scheme, the quota control module is further configured to determine the current remaining per-second query rate quota according to the client per-second query rate quota and the per-second query rate quota used when the sent request information is processed; and performing quota control on the access client according to the current remaining query rate quota per second.
On the basis of the technical scheme, the quota control module is also used for acquiring the query rate quota per second of the request quantity corresponding to the received request information; and if the current remaining per-second query rate quota is smaller than the request quantity per-second query rate quota, performing quota control on an access client, and sending feedback information to the client.
According to the technical scheme of the embodiment of the invention, after the query rate quota per second range pre-registered by the slave node service is registered to the master node service, the master node service can periodically determine the query rate quota per second of the nodes corresponding to each slave node and the query rate quota per second of the client side of each client side associated with each slave node, and send the query rate quota per second of the client side to the slave node service, so that the slave node service and the query rate quota per second of the client side are effectively controlled, and the technical effect of avoiding resource waste is achieved.
The quota management device applied to the distributed system provided by the embodiment of the invention can execute the quota management method applied to the distributed system provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
It should be noted that, the units and modules included in the apparatus are merely divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the embodiment of the invention.
EXAMPLE seven
Fig. 7 is a schematic structural diagram of a quota management apparatus applied to a distributed system according to a seventh embodiment of the present invention, where the apparatus is configured in a master node service and includes: a node query per second rate quota determination module 710 and a client query per second rate quota determination module 720.
The node query rate per second quota determining module 710 is configured to determine, for each slave node service, a node query rate per second quota corresponding to a current slave node service according to a received node query rate per second quota range reported by the current slave node service; a client query rate per second quota determining module 720, configured to determine, according to the node query rate per second quota corresponding to the current slave node service, a registered query rate per second quota registered by a client associated with the current slave node service, a client query rate per second quota of each client associated with the current slave node service, so that the current slave node service acquires the client query rate per second quota, and perform query rate quota per second control on request information received by the current slave node service according to the client query rate per second quota
On the basis of the above technical solutions, the apparatus further includes: the method comprises the steps of periodically determining the service quantity of current slave nodes, and determining the query rate quota per second of each slave node service and the query rate quota per second of a client associated with each slave node service according to the service quantity of the current slave nodes.
On the basis of the technical schemes, the node query rate quota per second determining module is further used for receiving heartbeat information periodically sent by each slave node service, and if the number of the received heartbeat information changes within a preset time period, determining the number of the current slave node services; and determining the node query rate quota per second of each changed slave node service according to the current slave node service quantity, the total query rate quota per second and the node query rate quota per second range.
On the basis of the technical solutions, the query rate per second quota determining module of the client is used for acquiring the query rate per second range of registration registered by each client in advance; and determining the client query rate quota per second of each client associated with the current node according to the number of the current slave nodes, the node query rate quota per second corresponding to the changed current slave node service and the registered query rate quota per second of each client associated with the current client.
According to the technical scheme of the embodiment of the invention, after the query rate quota per second range pre-registered by the slave node service is registered to the master node service, the master node service can periodically determine the query rate quota per second of the nodes corresponding to each slave node and the query rate quota per second of the client side of each client side associated with each slave node, and send the query rate quota per second of the client side to the slave node service, so that the slave node service and the query rate quota per second of the client side are effectively controlled, and the technical effect of avoiding resource waste is achieved.
The quota management device applied to the distributed system provided by the embodiment of the invention can execute the quota management method applied to the distributed system provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.
It should be noted that, the units and modules included in the apparatus are merely divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the embodiment of the invention.
Example eight
Fig. 8 is a schematic structural diagram of an apparatus according to an eighth embodiment of the present invention. FIG. 8 illustrates a block diagram of an exemplary device 80 suitable for use in implementing embodiments of the present invention. The device 80 shown in fig. 8 is only an example and should not bring any limitation to the function and scope of use of the embodiments of the present invention.
As shown in FIG. 8, device 80 is embodied in a general purpose computing device. The components of the device 80 may include, but are not limited to: one or more processors or processing units 801, a system memory 802, and a bus 803 that couples various system components including the system memory 802 and the processing unit 801.
The system memory 802 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)804 and/or cache memory 805. The device 80 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 806 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 8, and commonly referred to as a "hard drive"). Although not shown in FIG. 8, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 803 by one or more data media interfaces. Memory 802 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
A program/utility 808 having a set (at least one) of program modules 807 may be stored, for instance, in memory 802, such program modules 807 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may include an implementation of a network environment. Program modules 807 generally perform the functions and/or methodologies of embodiments of the present invention as described herein.
The processing unit 801 executes various functional applications and data processing by running a program stored in the system memory 802, for example, implementing the quota management method applied to the distributed system provided by the embodiment of the present invention.
Example nine
An embodiment of the present invention further provides a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform a quota management method applied to a distributed system.
The method comprises the following steps:
when request information is received, acquiring a client-side per second query rate quota corresponding to a current client-side; the query rate quota per second of the client is determined by the master node service according to a node query rate quota per second range reported by the current slave node service and a registered query rate quota per second registered by the client associated with the current slave node service;
and performing query rate quota per second control on the access client according to the query rate quota per second of the client and the used query rate quota per second. Or the like, or, alternatively,
when the change of the number of the slave node services is detected, determining the query rate quota per second of the node corresponding to each changed slave node service according to the received query rate quota per second range of the node reported by each slave node service;
for each node, determining a client query rate quota per second of each client associated with the current slave node service according to the node query rate quota per second corresponding to the current slave node service and a registered query rate quota per second registered by a client associated with the current slave node service, so that the current slave node service acquires the client query rate quota per second, and performs query rate quota per second control on request information received by the current slave node service according to the client query rate quota per second.
Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, 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), an optical fiber, 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 document, 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.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for embodiments of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.
Claims (13)
1. A quota management method applied to a distributed system is characterized in that the quota management method applied to a slave node service comprises the following steps:
receiving request information sent by a current client, and acquiring a client per second query rate quota corresponding to the current client; the query rate quota per second of the client is determined by the master node service according to a node query rate quota per second range reported by the current slave node service and a registered query rate quota per second registered by the client associated with the current slave node service;
and managing and controlling the data access request sent by the current client according to the query rate quota per second of the client and the used query rate quota per second.
2. The method of claim 1, further comprising:
and registering the node per second query rate quota range preset in the current slave node service into a master node service, so that the master node service determines client per second query rate quotas of clients associated with the current slave node service according to the node per second query rate quota range.
3. The method of claim 1, wherein the obtaining a client query rate per second quota corresponding to a current client comprises:
and periodically acquiring the client query rate quota per second of each client associated with the current slave node service from the master node service.
4. The method according to claim 2, wherein the managing and controlling the data access request sent by the current client according to the client query rate per second quota and the used query rate per second quota includes:
determining the current remaining per-second query rate quota according to the client per-second query rate quota and the per-second query rate quota used when the sent request information is processed;
and managing and controlling the data access request sent by the current client according to the current remaining query rate quota per second.
5. The method according to claim 4, wherein the managing and controlling the data access request sent by the current client according to the current remaining query rate per second quota includes:
acquiring a request amount per second query rate quota corresponding to the received request information;
and if the current remaining per-second query rate quota is smaller than the request quantity per-second query rate quota, managing and controlling the data access request sent by the current client, and sending feedback information to the client.
6. A quota management method applied to a distributed system is characterized by being applied to a master node service, and comprising the following steps:
for each slave node service, determining a node query rate quota per second corresponding to the current slave node service according to a received node query rate quota per second range reported by the current slave node service;
according to the node query rate per second quota corresponding to the current slave node service and the registered query rate per second quota registered by the client associated with the current slave node service, determining the client query rate per second quota of each client associated with the current slave node service, so that the current slave node service acquires the client query rate per second quota, and performing query rate quota per second control on the request information received by the current slave node service according to the client query rate quota per second.
7. The method of claim 6, further comprising:
the method comprises the steps of periodically determining the service quantity of current slave nodes, and determining the query rate quota per second of each slave node service and the query rate quota per second of a client associated with each slave node service according to the service quantity of the current slave nodes.
8. The method of claim 7, wherein the periodically determining a current number of slave node services and determining a node query rate per second quota for each slave node service according to the current number of slave node services comprises:
receiving heartbeat information periodically sent by each slave node service, and determining the service quantity of the current slave nodes if the heartbeat information is received within a preset time length and changes;
and determining the node query rate quota per second of each changed slave node service according to the current slave node service quantity, the total query rate quota per second and the node query rate quota per second range.
9. The method of claim 8, wherein determining client query rate per second quotas for respective clients associated with the current slave node service according to the node query rate per second quotas corresponding to the current slave node service and registered query rate per second quotas for client registrations associated with the current slave node service comprises:
acquiring a registration per second query rate quota pre-registered by each client;
and determining the client-side query rate quota per second of each client side associated with the current slave node service according to the changed node-side query rate quota per second corresponding to the current slave node service and the registered query rate quota per second of each client side associated with the current client side.
10. A quota management apparatus applied to a distributed system, configured in a slave node service, comprising:
the client query rate per second quota acquisition module is used for receiving request information sent by a current client and acquiring a client query rate per second quota corresponding to the current client; the query rate quota per second of the client is determined by the master node service according to a node query rate quota per second range reported by the current slave node service and a registered query rate quota per second registered by the client associated with the current slave node service;
and the quota control module is used for managing and controlling the data access request sent by the current client according to the query rate quota per second of the client and the used query rate quota per second.
11. A quota management apparatus applied to a distributed system, configured in a master node service, comprising:
the node query rate quota per second determining module is used for determining a node query rate quota per second corresponding to the current slave node service according to a received node query rate quota per second range reported by the current slave node service aiming at each slave node service;
the client query rate quota per second determination module is used for determining client query rate quotas per second of each client associated with the current slave node service according to the node query rate quota per second corresponding to the current slave node service and the registered query rate quotas per second registered by the client associated with the current slave node service, so that the current slave node service acquires the client query rate quotas per second, and performs query rate quota per second control on request information received by the current slave node service according to the client query rate quotas per second.
12. An electronic device, characterized in that the electronic device comprises:
one or more processors;
a storage device for storing one or more programs,
when executed by the one or more processors, cause the one or more processors to implement the quota management method applied to the distributed system as recited in any of claims 1-5 or 6-9.
13. A storage medium containing computer-executable instructions for performing the quota management method applied to a distributed system as claimed in any one of claims 1-5 or 6-9 when executed by a computer processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011018956.6A CN113760940A (en) | 2020-09-24 | 2020-09-24 | Quota management method, device, equipment and medium applied to distributed system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011018956.6A CN113760940A (en) | 2020-09-24 | 2020-09-24 | Quota management method, device, equipment and medium applied to distributed system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113760940A true CN113760940A (en) | 2021-12-07 |
Family
ID=78785851
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011018956.6A Pending CN113760940A (en) | 2020-09-24 | 2020-09-24 | Quota management method, device, equipment and medium applied to distributed system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113760940A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114745338A (en) * | 2022-03-30 | 2022-07-12 | Oppo广东移动通信有限公司 | Flow control method, flow control device, storage medium and server |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101799797A (en) * | 2010-03-05 | 2010-08-11 | 中国人民解放军国防科学技术大学 | Dynamic allocation method of user disk quota in distributed storage system |
| CN102447736A (en) * | 2011-11-17 | 2012-05-09 | 华中科技大学 | Management and control method for user quota in multi-network storage system |
| US20120117235A1 (en) * | 2009-08-18 | 2012-05-10 | Telefonaktiebolaget L M Ericsson (Publ) | Method, Apparatus and Computer Program for Enforcing Policy Across Associated Sessions Taking Into Account a Total Usage Quota for Associated User |
| CN103095720A (en) * | 2013-01-30 | 2013-05-08 | 中国科学院自动化研究所 | Safety management method of cloud memory system based on session management server |
| CN104750558A (en) * | 2013-12-31 | 2015-07-01 | 伊姆西公司 | Resource allocation management method and device of hierarchical quota system |
| CN109660400A (en) * | 2018-12-24 | 2019-04-19 | 苏州思必驰信息科技有限公司 | Flow control configuration method and system |
| CN109784963A (en) * | 2017-11-14 | 2019-05-21 | 阿里巴巴集团控股有限公司 | A kind of resource management system, method, server and computer storage medium |
| CN110458468A (en) * | 2019-08-16 | 2019-11-15 | 北京百度网讯科技有限公司 | A kind of task processing method, device, electronic equipment and storage medium |
| CN110708258A (en) * | 2019-09-29 | 2020-01-17 | Oppo广东移动通信有限公司 | Flow control method, flow control device, server and storage medium |
| CN111064602A (en) * | 2019-12-02 | 2020-04-24 | 紫光云技术有限公司 | Resource quota management method under public cloud platform |
| CN111552677A (en) * | 2020-05-13 | 2020-08-18 | 重庆紫光华山智安科技有限公司 | Quota management method, device, management node and storage medium |
-
2020
- 2020-09-24 CN CN202011018956.6A patent/CN113760940A/en active Pending
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20120117235A1 (en) * | 2009-08-18 | 2012-05-10 | Telefonaktiebolaget L M Ericsson (Publ) | Method, Apparatus and Computer Program for Enforcing Policy Across Associated Sessions Taking Into Account a Total Usage Quota for Associated User |
| CN101799797A (en) * | 2010-03-05 | 2010-08-11 | 中国人民解放军国防科学技术大学 | Dynamic allocation method of user disk quota in distributed storage system |
| CN102447736A (en) * | 2011-11-17 | 2012-05-09 | 华中科技大学 | Management and control method for user quota in multi-network storage system |
| CN103095720A (en) * | 2013-01-30 | 2013-05-08 | 中国科学院自动化研究所 | Safety management method of cloud memory system based on session management server |
| CN104750558A (en) * | 2013-12-31 | 2015-07-01 | 伊姆西公司 | Resource allocation management method and device of hierarchical quota system |
| CN109784963A (en) * | 2017-11-14 | 2019-05-21 | 阿里巴巴集团控股有限公司 | A kind of resource management system, method, server and computer storage medium |
| CN109660400A (en) * | 2018-12-24 | 2019-04-19 | 苏州思必驰信息科技有限公司 | Flow control configuration method and system |
| CN110458468A (en) * | 2019-08-16 | 2019-11-15 | 北京百度网讯科技有限公司 | A kind of task processing method, device, electronic equipment and storage medium |
| CN110708258A (en) * | 2019-09-29 | 2020-01-17 | Oppo广东移动通信有限公司 | Flow control method, flow control device, server and storage medium |
| CN111064602A (en) * | 2019-12-02 | 2020-04-24 | 紫光云技术有限公司 | Resource quota management method under public cloud platform |
| CN111552677A (en) * | 2020-05-13 | 2020-08-18 | 重庆紫光华山智安科技有限公司 | Quota management method, device, management node and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 赵燕;刘心松;邱元杰;周正娟;: "基于数字有机体存储系统配额机制的设计与实现", 成都信息工程学院学报, no. 01, 15 February 2009 (2009-02-15) * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114745338A (en) * | 2022-03-30 | 2022-07-12 | Oppo广东移动通信有限公司 | Flow control method, flow control device, storage medium and server |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109983441B (en) | Resource management for batch jobs | |
| US8671134B2 (en) | Method and system for data distribution in high performance computing cluster | |
| CN110941481A (en) | Resource scheduling method, device and system | |
| US20140289286A1 (en) | System and method for performance tuning of garbage collection algorithms | |
| US9135040B2 (en) | Selecting provisioning targets for new virtual machine instances | |
| US20200351207A1 (en) | Method and system of limiting traffic | |
| CN104937584A (en) | Providing optimized quality of service to prioritized virtual machines and applications based on quality of shared resources | |
| JPH10283211A (en) | Processor resource management method for multi-system environment | |
| US9940020B2 (en) | Memory management method, apparatus, and system | |
| WO2021057607A1 (en) | Method and apparatus for node speed limiting, electronic device, and storage medium | |
| JP2001331333A (en) | Computer system and method for controlling computer system | |
| US20160352821A1 (en) | Method and system for allocating resources for virtual hosts | |
| CN105763595A (en) | Method of improving data processing efficiency and server | |
| CN111163186B (en) | ID generation method, device, equipment and storage medium | |
| US9697047B2 (en) | Cooperation of hoarding memory allocators in a multi-process system | |
| US11709707B2 (en) | Low latency distributed counters for quotas | |
| CN112799824A (en) | Current limiting method, device, equipment and storage medium | |
| CN110909978A (en) | Resource processing method, device, server and computer readable storage medium | |
| CN105338037A (en) | Dynamic scheduling method and system | |
| CN113760940A (en) | Quota management method, device, equipment and medium applied to distributed system | |
| CN113326146A (en) | Message processing method and device, electronic equipment and storage medium | |
| CN109067649B (en) | Node processing method and device, storage medium and electronic equipment | |
| CN111008071A (en) | Task scheduling system, method and server | |
| CN112860506A (en) | Monitoring data processing method, device, system and storage medium | |
| CN107508765B (en) | Message processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |