CN113760940B - 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
- CN113760940B CN113760940B CN202011018956.6A CN202011018956A CN113760940B CN 113760940 B CN113760940 B CN 113760940B CN 202011018956 A CN202011018956 A CN 202011018956A CN 113760940 B CN113760940 B CN 113760940B
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; 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 OR CALCULATING; 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Computing Systems (AREA)
- Computer And Data Communications (AREA)
Abstract
The embodiment of the invention provides a quota management method, a quota management device, quota management equipment and quota management medium applied to a distributed system, wherein the quota management method is applied to slave node services and comprises the following steps: when receiving request information sent by a current client, acquiring a query rate quota per second of the client corresponding to the current client; the method comprises the steps that a client-side query rate quota per second is determined by a master node service according to a node query rate quota per second range reported by a current slave node service and a registered query rate quota per second registered by a client-side associated with the current slave node service; and controlling the query rate quota per second for 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 the 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
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 application, a corresponding quota can be allocated to each node, so that when request information is received, the request information is processed based on the allocated quota.
In carrying out the present invention, the inventors have found that the following problems exist in the prior art:
At present, although a corresponding quota can be allocated to each node, the allocated quota is randomly allocated, and the quota of each node cannot be effectively managed, so that the quota allocation is unreasonable, and the problem of resource waste exists.
Disclosure of Invention
The invention provides a quota management method, device, equipment and medium applied to a distributed system, which are used for realizing effective quota management 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 query rate quota per second of a client corresponding to the current client; the method comprises the steps that a client-side query rate quota per second is determined by a master node service according to a node query rate quota per second range reported by a current slave node service and a registered query rate quota per second registered by a client-side 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 and the used query rate quota per second of the client.
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 primary node service, and includes:
Aiming at each slave node service, determining the node per second query rate quota corresponding to the current slave node service according to the received node per second query rate quota range reported by the current slave node service;
According to the node per second query rate quota corresponding to the current slave node service, determining the client per second query rate quota of each client associated with the current slave node service according to the registered per second query rate quota of the client associated with the current slave node service, so that the current slave node service obtains the client per second query rate quota, and carrying out per second query rate quota control on request information received by the current slave node service according to the client per second query rate quota.
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-side query rate quota obtaining module is used for receiving request information sent by a current client-side and obtaining a client-side query rate quota corresponding to the current client-side per second; the method comprises the steps that a client-side query rate quota per second is determined by a master node service according to a node query rate quota per second range reported by a current slave node service and a registered query rate quota per second registered by a client-side associated with the current slave node service;
and the quota control module is used for 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 device applied to a distributed system, where the quota management device is configured in a service of a master node, and the quota management device includes:
The node per-second query rate quota determining module is used for determining the node per-second query rate quota corresponding to the current slave node service according to the received node per-second query rate quota range reported by the current slave node service for each slave node service;
The client-side per-second inquiry rate quota determining module is used for determining client-side per-second inquiry rate quotas of all the clients associated with the current slave node service according to the node per-second inquiry rate quotas corresponding to the current slave node service, determining the client-side per-second inquiry rate quotas of all the clients associated with the current slave node service, enabling the current slave node service to acquire the client-side per-second inquiry rate quotas, and carrying out per-second inquiry rate quota control on request information received by the current slave node service according to the client-side per-second inquiry rate quotas.
In a fifth aspect, an embodiment of the present invention further provides an electronic device, including:
One or more processors;
Storage means for storing one or more programs,
The one or more programs, when executed by the one or more processors, cause the one or more processors to implement a quota management method for a distributed system as described in any of the embodiments of the 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 for a distributed system according to any of the embodiments of the present invention.
According to the technical scheme, after the query rate quota range of each second registered in advance by the slave node service is registered to the master node service, the master node service can periodically determine the query rate quota of each second of the node corresponding to each slave node and the query rate quota of each second of the client associated with each slave node, and send the query rate quota of each second of the client to the slave node service, so that the slave node service and the query rate quota of each second of the client are effectively managed and controlled, and the technical effect of resource waste is avoided.
Drawings
In order to more clearly illustrate the technical solution of the exemplary embodiments of the present invention, a brief description is given below of the drawings required for describing the embodiments. It is obvious that the drawings presented are only drawings of some of the embodiments of the invention to be described, and not all the drawings, and that other drawings can be made according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flowchart of a quota management method applied to a distributed system according to an embodiment of the invention;
Fig. 2 is a flow chart of a quota management method applied to a distributed system according to a second embodiment of the invention;
fig. 3 is a flow chart of a quota management method applied to a distributed system according to a third embodiment of the invention;
Fig. 4 is a flow chart of a quota management method applied to a distributed system according to a fourth embodiment of the invention;
FIG. 5 is a schematic diagram of a system architecture used when a master node service and a slave node service provided in a fifth embodiment of the present invention interact;
fig. 6 is a schematic structural diagram of a quota management device applied to a distributed system according to a sixth embodiment of the invention;
fig. 7 is a schematic structural diagram of a quota management device applied to a distributed system according to a seventh embodiment of the invention;
fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings.
Example 1
Fig. 1 is a flowchart of a quota management method applied to a distributed system according to an embodiment of the invention, where the embodiment may be performed by each slave node service associated with a master node service of the distributed system, the method can be applied to the situation of determining the query rate quota per second from each client to the client occupied by the slave node service, and can be executed by a quota management device applied to a distributed system, and the system can be realized by software and/or hardware.
As shown in fig. 1, the method of this embodiment includes:
S110, receiving request information sent by a current client, and acquiring a query rate quota per second of the client corresponding to the current client.
Wherein the number of slave node services may be plural, and the number of clients associated with each slave node service may be plural. The request information may be a read-write request sent by one or more of the clients associated with the current slave node service. When request information of a client is received from a node service, a query rate quota per second of the client corresponding to a client identifier can be acquired according to the client identifier of the client. The Query Per Second (QPS) rate may be the number of queries each service can respond to Per Second, and is a measure of how much traffic a particular Query server handles in a specified time. The QPS quota is predetermined for the master node service and issued to the slave node service. The client query rate per second quota is a quota corresponding to each client.
For the sake of clearly describing the technical solution of this embodiment, the solution may be described by taking a certain slave node service and a certain client as examples.
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 time of receiving the request information may be regarded as the current client. The query rate per second quota corresponding to the current client can be used as the query rate per second quota of the client.
In this embodiment, it is determined that the client per-second query rate quota corresponding to each client is determined by the master node service from the node per-second query rate quota range currently reported by the slave node and the registration per-second query rate quota for the client registration associated with the current slave node service.
Specifically, when the slave node service starts, the stand-alone capability (QPS) of the current slave node may be registered in the master node service, that is, the master node service may receive the query rate quota range per second of the node reported by the slave node service. Meanwhile, the client can register the query rate quota per second of the client in the main node service. From the total quota, the slave node per-second query rate quota range and the registered client per-second query rate quota, a node per-second query rate quota corresponding to the slave node service and a client per-second query rate quota from the client to the respective slave node service may be determined, respectively. In this embodiment, the node per second query rate quota 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 a 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.
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 a quota management component in the master node service. Meanwhile, the quota information reporting and updating component can also acquire the determined query rate quota per second of the node and the query rate quota per second of the client from the quota management component. This is because the quota management component in the master node service can determine and store the query rate quota per second from the client to the client served by the slave node according to the received query rate quota range per second, the query rate quota per second of the registered client, and the total quota, 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 (quality control system) capabilities in the cluster in real time, and optionally, the quota used amount and the quota total amount.
Specifically, the quota information reporting and updating component may register a preset per-second query rate quota range of a node in the current slave node service to the master node service, and after the master node service receives the per-second query rate quota range of the node reported by the slave node service, it may determine a per-second query rate quota of each client associated with the current slave node service.
In this embodiment, the benefit of reporting the local QPS capability set in the current slave node service to the master node service is that the quota management component in the master node service may be enabled to allocate a corresponding query rate quota per second for the slave node service, so as to determine the query rate quota per second from each client to the client of the slave node service.
In this embodiment, to determine the client rate per second quota corresponding to each client, it may be: periodically acquiring the query rate quota per second of each client associated with the current slave node service from the master node service.
Where ten seconds may be taken as one cycle. During operation of the distributed system, a situation may occur in which the number of slave node services associated with a master node service changes in transmission. When the number of slave nodes changes, the rate quota per second of the node allocated by the master node service to the slave node service also changes accordingly, and accordingly, the 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 query rate quota per second of each client associated with the current slave node service, the query rate quota per second of each client associated with the current slave node service may be periodically obtained from the quota management component of the master node service, so as to timely determine whether the received request information can be processed, thereby realizing the technical effect of dynamically monitoring the quota.
S120, managing and controlling the data access request sent by the current client according to the query rate quota per second and the used query rate quota per second of the client.
Wherein the used inquiry rate quota is the inquiry rate quota per second used when processing the sent request information. According to the query rate quota per second and the used query rate quota per second of the client obtained from the main node service, the remaining query rate quota per second can be determined, and the query rate quota per second can be controlled for the access client based on the remaining query rate quota per second, namely, the data access request sent by the current client is managed.
Optionally, the managing the data access request sent by the current client according to the query rate quota per second and the used query rate quota per second of the client includes: determining the current remaining query rate quota per second according to the query rate quota per second of the client and the query rate quota per second used when processing the transmitted request information; and according to the current residual query rate quota per second, performing quota control on the access client.
The client can send a read-write request to the slave node service, and when the slave node service receives the read-write request information sent by the client, whether to perform quota control on the current client can be determined according to the per-second query rate quota information of the current client in the current slave node.
In this embodiment, the managing, according to the current remaining query rate quota per second, the data access request sent by the current client includes: acquiring a query rate quota per second of a request quantity corresponding to the received request information; and if the current residual query rate quota per second is smaller than the request amount per second query rate quota, performing quota control on the access client and sending feedback information to the client.
It should be noted that, the client may send a plurality of read-write request information to the slave node service, and when the read-write request is processed, 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 currently processed read-write request and the query rate quota per second of the client corresponding to the current client at the current slave node service.
Specifically, if the remaining query rate quota per second is detected to be smaller than the query rate quota per second of the request amount, quota control can be performed on the access client, and feedback information is sent to the client, and optionally, the request information is abnormal to process or the feedback information of the request is waited to be processed.
In this embodiment, the advantage of this setting is that the query rate quota per second of the client can be effectively managed and controlled, so as to avoid the technical effect of resource waste.
According to the technical scheme, after the query rate quota range of each second registered in advance by the slave node service is registered to the master node service, the master node service can periodically determine the query rate quota of each second of the node corresponding to each slave node and the query rate quota of each second of the client associated with each slave node, and send the query rate quota of each second of the client to the slave node service, so that the slave node service and the query rate quota of each second of the client are effectively managed and controlled, and the technical effect of resource waste is avoided.
Example two
As an alternative embodiment of the foregoing embodiment, fig. 2 is a flow chart of a quota management method applied to a distributed system according to a second embodiment of the present invention. Wherein, the technical terms identical to or corresponding to the above embodiments are not repeated herein.
As shown in fig. 2, the method includes:
S210, registering the query rate capability per second of each slave node service in the master node service.
Specifically, the slave node service in the HBase cluster, namely the node service responsible for providing data read-write to the outside, is started, and based on QuotaPlugin quota information reporting and updating components in the slave node service, the slave node service registers to the master node service according to Shan Jineng force configured locally, namely a preset query rate quota range per second of the node. That is, the query rate quota range per second for the node served by the slave node is registered into HBaseMaster, i.e., the Master node of the HBase cluster, which is responsible for coordinating RegionServer in the cluster and managing the distribution of regions in the cluster.
S220, periodically acquiring the query rate quota per second of each client 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 the query rate quota per second of each client associated with the current slave node service from the quota management component in the master node service. For example, the capacity information that each client should have in the current node is acquired 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 quota per second of the node reported by each slave node service, the query rate quota per second registered by the client and the total quota, the query rate quota per second from each client to the client of the slave node service, and store the query rate quota per second to the quota management component of the master node service, so as to report and update the quota information in the slave node service to obtain corresponding query rate quota information per second of the client.
S230, updating a client quota mapping table in the content.
Specifically, after the quota information reporting and updating component of the slave node service obtains 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. When receiving the request information from the node service, the quota checking module in the node service can check whether the request amount quota of the client request information exceeds the remaining client quota in real time, and if yes, the abnormal request information processing operation is fed back to the client.
That is, when the client sends the request information to the slave node service, the slave node service can determine a specific processing mode of the request information according to the query rate quota per second and the current capacity information corresponding to the request information, thereby realizing the technical problem of avoiding the overuse of the query rate per second.
According to the technical scheme, after the query rate quota range of each second registered in advance by the slave node service is registered to the master node service, the master node service can periodically determine the query rate quota of each second of the node corresponding to each slave node and the query rate quota of each second of the client associated with each slave node, and send the query rate quota of each second of the client to the slave node service, so that the slave node service and the query rate quota of each second of the client are effectively managed and controlled, and the technical effect of resource waste is avoided.
Example III
Fig. 3 is a flow chart of a quota management method applied to a distributed system, which is provided by a third embodiment of the present invention, where the method may be performed by a quota management device applied to a distributed system and the device may be implemented in software and/or hardware.
As shown in fig. 1, the method of this embodiment includes:
S310, for each slave node service, determining the query rate quota per second of the node corresponding to the current slave node service according to the received query rate quota per second range of the node reported by the current slave node service.
The Master node of the HBase cluster is responsible for coordinating RegionServer in the cluster and managing the distribution of regions in the cluster. In the practical application process, the situation of the expansion and contraction capacity slave nodes exists, in order to ensure that reasonable node per second inquiry rate quota is distributed for each slave node service, namely, summarization and update of quota are realized, the number of the slave node services can be determined in real time, and the node per second inquiry rate quota corresponding to each slave node service is determined according to the number of the slave node services and the node per second inquiry rate quota range.
In particular, the master node service may detect in real time whether the number of slave node services with which it communicates has changed. When the number of the slave nodes is detected to change, the rate quota per second of the nodes served by each slave node can be determined according to the rate quota range per second, the changed number of the nodes and the total rate quota per second of the nodes served by each slave node. When the query rate quota per second of the slave node changes, the query rate quota per second of each client associated with the slave node also changes accordingly. According to the updated inquiry rate quota per second of the node and the inquiry rate quota range per second registered by the client in the master node service in advance, the inquiry rate quota per second from each client to the client served by the slave node can be redetermined.
In this embodiment, it may be periodically determined whether the number of slave node services changes, so as to reassign the corresponding QPS to each slave node service and the client rate quota per second of each client associated with the slave node service. Optionally, the number of current slave node services is determined periodically, and the node per second query rate quota of each slave node service and the client per second query rate quota associated with each slave node service are determined according to the number of current slave node services.
In this embodiment, when detecting a change in the number of slave node services, determining, according to a received range of query rate quota per second of each node reported by each slave node service, a query rate quota per second of each node corresponding to each slave node service after the change includes: receiving heartbeat information periodically sent by each slave node service, and determining the current slave node service quantity if the quantity of the received heartbeat information changes within a preset time period; and determining the query rate quota per second of the node served by each slave node after the change according to the current service number of the slave nodes, the total query rate quota per second and the query rate quota per second range of the node.
Wherein 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, may determine whether the number of each slave node service associated with the master node service has changed. Optionally, when detecting that the heartbeat information sent by a slave node service is not received within a certain period of time, the number of the 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 a change in the number of slave nodes is detected, the rate quota per second for each slave node can be determined according to the total rate quota per second, the pre-registered rate quota per second range, and the updated number of slave node services.
In this embodiment, the advantage of detecting the number of slave nodes is that the corresponding per-second query rate quota and the per-second query rate quota from the client to the client served by each slave node can be dynamically allocated to each slave node, so that the technical effects of automatically summarizing and updating the quota are achieved.
On the basis of the above technical solution, it should be noted that, since the client per second query rate quota of each client associated with each slave node service is to be determined, after the number of slave nodes changes and the node per second query rate quota corresponding to each slave node service is determined, the client per second query rate quota of the client needs to be determined according to the node per second query rate quota of the slave node service and the registered client per second query rate quota.
Optionally, the determining 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 corresponding to the current slave node service and the registered per second query rate quota of the client associated with the current slave node comprises: acquiring a registration query rate quota per second registered in advance by each client; and determining the client side per second query rate quota of each client side associated with the current node according to the current slave node number, the node per second query rate quota corresponding to the changed current slave node service and the registered per second query rate quota of each client side associated with the current client side.
Wherein, the total query rate quota per second of the client, that is, the query rate quota per second, can be registered in advance before the client accesses the slave node service. The current number of slave nodes refers to the number of slave node services counted by the master node service after each heartbeat message 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 query rate quota per second of the node and the query rate quota per second of the client can be updated in the quota management component of the master node service so as to report and update the quota information of the slave node service, the updated query rate quota per second of the client can be obtained from the quota management component, and further the access control of the client is carried out in the slave node service according to the query rate quota per second of the client, so that the technical effect of effectively managing and controlling the quota is achieved.
In the actual application process, a situation that a certain slave node service fails or a new slave node service is added exists, and the number of the slave node services is changed at this time. According to the number of slave node services after node change, the query rate quota per second which is equally divided to each remaining node by each client can be recalculated.
S320, determining the client side per second query rate quota of each client side associated with the current slave node service according to the node per second query rate quota corresponding to the current slave node service and the registered per second query rate quota of the client side associated with the current slave node service.
Wherein the number of slave node services associated with the master node service may include a plurality. For the sake of clarity of description of the technical solution of this embodiment, a specific slave node service may be described as an example. Other slave node services may also employ the same processing.
The query rate quota per second of the node may be a redetermined query rate quota per second of the node corresponding to each slave node service after heartbeat information reported by each slave node service is received. 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 can not be changed, and whether the change occurs is related to the quantity of the received heartbeat information in a period of time. The client also needs to register the client's per second query rate quota before sending a read-write request to the slave node service. 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 each associated slave node service according to the query rate quota per second of the nodes of each slave node service and the query rate quota per second of the registered clients.
Specifically, according to the query rate quota per second of the node corresponding to the current slave node service and the registered query rate quota per second of the client corresponding to the current slave node service, which are registered in advance with the current slave node service, the query rate quota per second of the client corresponding to the current slave node service can be determined. After determining the query rate quota per second, 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.
When needing to be described, the slave node service can periodically acquire updated client-per-second query rate quota from the master node service, and the benefit of this is that the client-per-second query rate quota associated with each slave node service can be dynamically determined.
It should be further noted that, since the slave node service periodically transmits heartbeat information to the master node service, the rate quota per second from each client to the client of the slave node service may be periodically determined and stored in the quota management component of the master node service. The slave node service also periodically acquires the query rate quota of the client per second from the quota management component, so that the technical effect of effectively managing quota information can be realized.
According to the technical scheme, after the query rate quota range of each second registered in advance by the slave node service is registered to the master node service, the master node service can periodically determine the query rate quota of each second of the node corresponding to each slave node and the query rate quota of each second of the client associated with each slave node, and send the query rate quota of each second of the client to the slave node service, so that the slave node service and the query rate quota of each second of the client are effectively managed and controlled, and the technical effect of resource waste is avoided.
Example IV
As an alternative embodiment of the foregoing embodiment, fig. 4 is a flowchart 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 reassigning the corresponding node per second query rate quota and the client side per second query rate quota associated with the node to each slave node service according to the determined number of the slave node services. Wherein, the technical terms identical to or corresponding to the above embodiments are not repeated herein.
As shown in fig. 4, the method includes:
s410, obtaining the number of 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 each received heartbeat information. Optionally, if heartbeat information sent by a certain slave node is not received within a period of time, the fault of the slave node service is indicated, and accordingly, the number of the slave node services is changed.
S420, judging whether the number of the current slave nodes changes, if so, executing S430; if not, S410 is performed.
Specifically, after determining the current number of slave nodes serving according to the received heartbeat information, whether the number of the current slave nodes changes or not 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 the heartbeat information is received, the number of slave nodes is determined to be 10, the number of nodes determined when the heartbeat information is received last time can be obtained, and optionally, 8 nodes can be obtained, the number of the nodes can be determined to have changed according to the current number of nodes and the previous number of nodes, and at this time, S430 can be executed; if it is detected that the number of the current slave nodes is not changed, the corresponding per-second query rate quota may not be allocated to each slave node again, and S410 may be executed in a returning manner.
S430, calculating the query rate quota per second from each client to the slave node service.
Specifically, when the number of the current slave nodes is determined to change, the quota of each slave node service also changes correspondingly, and meanwhile, the query rate quota per second of each client associated with the slave node also changes correspondingly, so that the query rate quota per second from each client to the slave node service can be calculated.
S440, updating a client quota mapping table in the memory.
Specifically, after determining the client per second query rate quota of the client, the updated client per second query rate quota may be updated in a quota management component in the host node service. The quota reporting and updating component QuotaPlugin in the slave node service may periodically obtain the latest client quota information from the quota management component QuotaManager every ten seconds and update the local content. The slave node service can use the quota reporting and updating component to acquire the query rate quota per second of the client from the quota management component of the master node service, so that the quota control is performed on the client according to the query rate quota per second of the client.
According to the technical scheme, after the query rate quota range of each second registered in advance by the slave node service is registered to the master node service, the master node service can periodically determine the query rate quota of each second of the node corresponding to each slave node and the query rate quota of each second of the client associated with each slave node, and send the query rate quota of each second of the client to the slave node service, so that the slave node service and the query rate quota of each second of the client are effectively managed and controlled, and the technical effect of resource waste is avoided.
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 and a slave node service provided in the fifth embodiment of the present invention interact.
See fig. 5, where the Master node in HBaseMaster clusters is responsible for coordinating RegionServer in the clusters and managing the distribution of regions in the clusters. I.e. the master node service is responsible for coordinating the slave node services in the cluster. RegionServer the slave node service, which can be understood as the slave node service of the HBase cluster, is responsible for providing data read-write (QPS service) to the outside (client), namely, the query rate quota service per second. The Client service Client can send corresponding read-write requests to the slave nodes. QuotaManager (quota management component) is disposed in the main node service and is responsible for managing and counting all the query rate quota per second in the cluster in real time, including the used amount, total amount and other query rate quota per second. QuotaPlugin (quota information reporting and updating component) is arranged in each slave node service, and is used for sending the query rate per second quota range of the locally registered node of the slave node to the master node, and is also used for acquiring the query rate per second capacity information which can be used by the client side at the current slave node from the quota management component.
Specifically, upon startup of the slave node service RegionServer, the slave node per second query rate quota range of the node may be reported to the master node service based on QuotaPlugin in the slave node service, i.e., locally configured stand-alone capabilities (QPS write/get) are registered in QuotaManager management module in the master node service HMaster. QuotaManager periodically checks the number of slave node services in the current cluster at regular intervals, optionally ten seconds. The client-to-each-slave node service client-per-second query rate quota can be determined according to the received slave node service node-per-second query rate quota, the number of nodes and the registered-per-second query rate quota pre-registered by the client. The slave node service may periodically obtain the allocated client per second query rate quota from 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 further comprises a RpcQuotaCheck quota checking module, whether the read-write request quantity sent by the client exceeds the query rate quota per second of the client is determined according to the updated query rate per second of the client, if so, the excess part can be submitted, and 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, the quota management component is arranged in the master node service, and the quota reporting and updating component is arranged in the slave node service, so that the total quota 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 capacity expansion and contraction convenience is achieved.
Example six
Fig. 6 is a schematic structural diagram of a quota management device applied to a distributed system, where the quota management device is configured in a slave node service, and the quota management device includes: a client query rate per second quota acquisition module 610 and a quota control module 620.
A client per second query rate quota obtaining module 610, configured to receive request information sent by a current client, and obtain a client per second query rate quota corresponding to the current client; the method comprises the steps that a client-side query rate quota per second is determined by a master node service according to a node query rate quota per second range reported by a current slave node service and a registered query rate quota per second registered by a client-side associated with the current slave node service; and the quota control module 620 is configured to manage a data access request sent by the current client according to the query rate quota per second and the used query rate quota per second of the client.
On the basis of the technical scheme, the device further comprises: the node quota registration module is used for registering the preset query rate quota range per second of the node in the current slave node service into the master node service, so that the master node service determines the query rate quota per second of each client associated with the current slave node service according to the query rate quota range per second of the node.
On the basis of the technical scheme, the client-side query rate quota obtaining module is further used for periodically obtaining the client-side query rate quota of each client-side associated with the current slave node service from the master node service.
On the basis of the technical scheme, the quota control module is further used for determining the current remaining query rate quota per second according to the query rate quota per second of the client and the query rate quota per second used for processing the sent request information; and according to the current residual query rate quota per second, performing quota control on the access client.
On the basis of the technical scheme, the quota control module is further used for acquiring the query rate quota per second of the request quantity corresponding to the received request information; and if the current residual query rate quota per second is smaller than the request amount per second query rate quota, performing quota control on the access client and sending feedback information to the client.
According to the technical scheme, after the query rate quota range of each second registered in advance by the slave node service is registered to the master node service, the master node service can periodically determine the query rate quota of each second of the node corresponding to each slave node and the query rate quota of each second of the client associated with each slave node, and send the query rate quota of each second of the client to the slave node service, so that the slave node service and the query rate quota of each second of the client are effectively managed and controlled, and the technical effect of resource waste is avoided.
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 the corresponding functional modules and beneficial effects of the execution method.
It should be noted that each unit and module included in the above apparatus are only divided according to the functional logic, but not limited to the above division, so long as the corresponding functions can be implemented; in addition, the specific names of the functional units are also only for distinguishing from each other, and are not used to limit the protection scope of the embodiments of the present invention.
Example seven
Fig. 7 is a schematic structural diagram of a quota management device applied to a distributed system, where the quota management device is configured in a master node service, and the quota management device includes: a node rate quota per second determination module 710 and a client rate quota per second determination module 720.
The node per second query rate quota determining module 710 is configured to determine, for each slave node service, a node per second query rate quota corresponding to a current slave node service according to a received node per second query rate quota range reported by the current slave node service; a client per second inquiry rate quota determining module 720, configured to determine a client per second inquiry rate quota of each client associated with a current slave node service according to the node per second inquiry rate quota corresponding to the current slave node service, determine a registered per second inquiry rate quota registered with the client associated with the current slave node service, so that the current slave node service obtains the client per second inquiry rate quota, and perform per second inquiry rate quota control on request information received by the current slave node service according to the client per second inquiry rate quota
On the basis of the technical schemes, the device further comprises: periodically determining the current number of slave node services, and determining the node per second query rate quota of each slave node service and the client per second query rate quota associated with each slave node service according to the current number of slave node services.
On the basis of the technical schemes, the query rate quota determining module of each second of the node is also used for receiving heartbeat information periodically sent by each slave node service, and determining the current slave node service quantity if the quantity of the received heartbeat information changes within a preset time length; and determining the query rate quota per second of the node served by each slave node after the change according to the current service number of the slave nodes, the total query rate quota per second and the query rate quota per second range of the node.
On the basis of the technical schemes, the inquiry rate quota determining module of each second of the client is used for obtaining the inquiry rate range of each second of registration registered by each client in advance; and determining the client side per second query rate quota of each client side associated with the current node according to the current slave node number, the node per second query rate quota corresponding to the changed current slave node service and the registered per second query rate quota of each client side associated with the current client side.
According to the technical scheme, after the query rate quota range of each second registered in advance by the slave node service is registered to the master node service, the master node service can periodically determine the query rate quota of each second of the node corresponding to each slave node and the query rate quota of each second of the client associated with each slave node, and send the query rate quota of each second of the client to the slave node service, so that the slave node service and the query rate quota of each second of the client are effectively managed and controlled, and the technical effect of resource waste is avoided.
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 the corresponding functional modules and beneficial effects of the execution method.
It should be noted that each unit and module included in the above apparatus are only divided according to the functional logic, but not limited to the above division, so long as the corresponding functions can be implemented; in addition, the specific names of the functional units are also only for distinguishing from each other, and are not used to limit the protection scope of the embodiments of the present invention.
Example eight
Fig. 8 is a schematic structural diagram of an apparatus according to an eighth embodiment of the present invention. Fig. 8 shows a block diagram of an exemplary device 80 suitable for use in implementing the embodiments of the present invention. The device 80 shown in fig. 8 is merely an example and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.
As shown in fig. 8, device 80 is in the form of a general purpose computing device. The components of 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 connects the various system components (including the system memory 802 and processing units 801).
Bus 803 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, micro channel architecture (MAC) bus, enhanced ISA bus, video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.
Device 80 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by device 80 and includes both volatile and nonvolatile media, removable and non-removable media.
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. 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, commonly referred to as a "hard disk drive"). Although not shown in fig. 8, a magnetic disk drive for reading from and writing to a removable non-volatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In such cases, each drive may be coupled to bus 803 via one or more data medium interfaces. Memory 802 may include at least one program product having a set (e.g., at least one) of program modules 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 in, for example, 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 or some combination of which may include an implementation of a network environment. Program modules 807 typically carry out the functions and/or methods of the described embodiments of the invention.
The device 80 may also communicate with one or more external devices 809 (e.g., keyboard, pointing device, display 810, etc.), one or more devices that enable a user to interact with the device 80, and/or any devices (e.g., network card, modem, etc.) that enable the device 80 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 811. Also, device 80 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN) and/or a public network, such as the Internet, through network adapter 812. As shown, network adapter 812 communicates with other modules of device 80 over bus 803. It should be appreciated that although not shown in fig. 8, other hardware and/or software modules may be used in connection with device 80, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
The processing unit 801 executes various functional applications and data processing by running a program stored in the system memory 802, for example, implementing a quota management method applied to a distributed system provided by an embodiment of the invention.
Example nine
A ninth embodiment of the present invention also provides a storage medium containing computer-executable instructions, which when executed by a computer processor, are for performing a quota management method applied to a distributed system.
The method comprises the following steps:
When receiving request information, acquiring a query rate quota per second of a client corresponding to a current client; the method comprises the steps that a client-side query rate quota per second is determined by a master node service according to a node query rate quota per second range reported by a current slave node service and a registered query rate quota per second registered by a client-side associated with the current slave node service;
And controlling the query rate quota per second for the access client according to the query rate quota per second of the client and the used query rate quota per second. Or alternatively, the first and second heat exchangers may be,
When the number of the slave node services is detected to change, determining the query rate quota per second of the node corresponding to each slave node service after the change according to the received query rate quota per second range of the node reported by each slave node service;
For each node, determining the client-side per-second query rate quota of each client-side associated with the current slave node service according to the node per-second query rate quota corresponding to the current slave node service and the registered per-second query rate quota of the client-side registered with the current slave node, so that the current slave node service obtains the client-side per-second query rate quota, and performing per-second query rate quota control on request information received by the current slave node service according to the client-side per-second query rate quota.
The computer storage media of embodiments of the invention may take the form of 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. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any 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 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.
The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. 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 one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ 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 kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
Note that the above is only a preferred embodiment of the present invention and the technical principle applied. 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, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.
Claims (12)
1. A quota management method applied to a distributed system, wherein the quota management method is applied to a slave node service, and comprises the following steps:
Receiving request information sent by a current client, and acquiring a query rate quota per second of a client corresponding to the current client; the method comprises the steps that a client-side query rate quota per second is determined by a master node service according to a node query rate quota per second range reported by a current slave node service and a registered query rate quota per second registered by a client-side associated with the current slave node service;
The slave node service periodically sends heartbeat information to the master node service so that the master node service determines the current slave node service quantity, and determines the node per second query rate quota of each slave node service after change according to the current slave node service quantity, the total per second query rate quota and the node per second query rate quota range;
And managing and controlling the data access request sent by the current client according to the query rate quota per second and the used query rate quota per second of the client.
2. The method as recited in claim 1, further comprising:
Registering the preset query rate quota range of each second of the node in the current slave node service into a master node service, so that the master node service determines the query rate quota of each second of the client associated with the current slave node service according to the query rate quota range of each second of the node.
3. The method of claim 1, wherein the obtaining the client per second query rate quota corresponding to the current client comprises:
periodically acquiring the query rate quota per second of each client associated with the current slave node service from the master node service.
4. The method of claim 2, wherein the managing the data access request sent by the current client according to the client's rate-per-second quota and the used rate-per-second quota comprises:
Determining the current remaining query rate quota per second according to the query rate quota per second of the client and the query rate quota per second used when processing the transmitted request information;
And managing and controlling the data access request sent by the current client according to the current residual query rate quota per second.
5. The method of claim 4, wherein the managing the data access request sent by the current client according to the current remaining quota of queries per second comprises:
Acquiring a query rate quota per second of a request quantity corresponding to the received request information;
and if the current residual query rate quota per second 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. The quota management method applied to the distributed system is characterized by comprising the following steps of:
Aiming at each slave node service, determining the node per second query rate quota corresponding to the current slave node service according to the received node per second query rate quota range reported by the current slave node service;
Determining the client-side per-second query rate quota of each client-side associated with the current slave node service according to the node per-second query rate quota corresponding to the current slave node service, and performing per-second query rate quota control on request information received by the current slave node service according to the client-side per-second query rate quota;
wherein determining the rate quota per second for each node served by the slave node comprises:
Receiving heartbeat information periodically sent by each slave node service, and determining the current number of slave node services if the heartbeat information is received for a preset time period and changes;
And determining the query rate quota per second of the node served by each slave node after the change according to the current service number of the slave nodes, the total query rate quota per second and the query rate quota per second range of the node.
7. The method as recited in claim 6, further comprising:
And periodically determining the current slave node service quantity, and determining the query rate quota per second of the client associated with each slave node service according to the current slave node service quantity.
8. The method of claim 6, wherein the determining the client per second query rate quota for each client associated with the current slave node service from the node per second query rate quota corresponding to the current slave node service and the registered per second query rate quota for the client associated with the current slave node service comprises:
acquiring a registration query rate quota per second registered in advance by each client;
And determining the client side per second query rate quota of each client side associated with the current slave node service according to the node per second query rate quota corresponding to the current slave node service after the change and the registered per second query rate quota of each client side associated with the current client side.
9. A quota management apparatus for use in a distributed system, the quota management apparatus being configured for use in a slave node service, the quota management apparatus comprising:
The client-side query rate quota obtaining module is used for receiving request information sent by a current client-side and obtaining a client-side query rate quota corresponding to the current client-side per second; the method comprises the steps that a client-side query rate quota per second is determined by a master node service according to a node query rate quota per second range reported by a current slave node service and a registered query rate quota per second registered by a client-side associated with the current slave node service;
The slave node service periodically sends heartbeat information to the master node service so that the master node service determines the current slave node service quantity, and determines the node per second query rate quota of each slave node service after change according to the current slave node service quantity, the total per second query rate quota and the node per second query rate quota range;
and the quota control module is used for 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.
10. A quota management device applied to a distributed system, configured in a service of a master node, comprising:
The node per-second query rate quota determining module is used for determining the node per-second query rate quota corresponding to the current slave node service according to the received node per-second query rate quota range reported by the current slave node service for each slave node service;
A client per-second inquiry rate quota determining module, configured to determine a client per-second inquiry rate quota of each client associated with a current slave node service according to the node per-second inquiry rate quota corresponding to the current slave node service, and perform per-second inquiry rate quota control on request information received by the current slave node service according to the client per-second inquiry rate quota;
the node query rate quota determining module is further configured to receive heartbeat information periodically sent by each slave node service, and determine the current number of slave node services if the number of received heartbeat information changes within a preset duration; and determining the query rate quota per second of the node served by each slave node after the change according to the current service number of the slave nodes, the total query rate quota per second and the query rate quota per second range of the node.
11. An electronic device, the electronic device comprising:
One or more processors;
Storage means for storing one or more programs,
When executed by the one or more processors, cause the one or more processors to implement a quota management method as in any of claims 1-5 or 6-8 for a distributed system.
12. A storage medium containing computer executable instructions which, when executed by a computer processor, are for performing a quota management method as claimed in any one of claims 1-5 or 6-8 applied to a distributed system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011018956.6A CN113760940B (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 CN113760940B (en) | 2020-09-24 | 2020-09-24 | Quota management method, device, equipment and medium applied to distributed system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113760940A CN113760940A (en) | 2021-12-07 |
| CN113760940B true CN113760940B (en) | 2024-10-18 |
Family
ID=78785851
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011018956.6A Active CN113760940B (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) | CN113760940B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114745338B (en) * | 2022-03-30 | 2024-09-06 | Oppo广东移动通信有限公司 | Flow control method, device, storage medium and server |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
Family Cites Families (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| ES2430056T3 (en) * | 2009-08-18 | 2013-11-18 | Telefonaktiebolaget Lm Ericsson (Publ) | Method, device and computer program to impose a policy through associated sessions taking into account the usage fee for an associated user |
| CN101799797B (en) * | 2010-03-05 | 2011-08-31 | 中国人民解放军国防科学技术大学 | Dynamic allocation method of user disk quota in distributed storage system |
| CN102447736B (en) * | 2011-11-17 | 2013-12-18 | 华中科技大学 | Management and control method for user quota in multi-network storage system |
| CN103095720B (en) * | 2013-01-30 | 2016-03-23 | 中国科学院自动化研究所 | A kind of method for managing security of cloud storage system of dialogue-based management server |
| CN104750558B (en) * | 2013-12-31 | 2018-07-03 | 伊姆西公司 | The method and apparatus that resource allocation is managed in quota system is layered |
| CN109784963A (en) * | 2017-11-14 | 2019-05-21 | 阿里巴巴集团控股有限公司 | A kind of resource management system, method, server and computer storage medium |
| CN109660400B (en) * | 2018-12-24 | 2021-06-25 | 思必驰科技股份有限公司 | Flow control configuration method and system |
| CN110458468B (en) * | 2019-08-16 | 2025-07-29 | 北京百度网讯科技有限公司 | Task processing method and device, electronic equipment and storage medium |
| CN111552677B (en) * | 2020-05-13 | 2021-01-26 | 重庆紫光华山智安科技有限公司 | Quota management method, device, management node and storage medium |
-
2020
- 2020-09-24 CN CN202011018956.6A patent/CN113760940B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113760940A (en) | 2021-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107360224B (en) | Method, system, device and storage medium for generating serial number in distributed system | |
| US10235047B2 (en) | Memory management method, apparatus, and system | |
| CN112214382B (en) | Alarm method and device | |
| US8671134B2 (en) | Method and system for data distribution in high performance computing cluster | |
| CN109379448B (en) | File distributed deployment method and device, electronic equipment and storage medium | |
| JP2001331333A (en) | Computer system and control method for computer system | |
| CN113438184B (en) | Network card queue management method and device and electronic equipment | |
| CN111917587B (en) | Method for network service management by using service system and service system | |
| CN109495542B (en) | Load distribution method and terminal equipment based on performance monitoring | |
| US20210248070A1 (en) | Data transmission method and apparatus | |
| US10282120B2 (en) | Method, apparatus and system for inserting disk | |
| US20160352821A1 (en) | Method and system for allocating resources for virtual hosts | |
| CN114285807A (en) | Message information management method, device, server and storage medium | |
| CN114564313A (en) | Load adjustment method and device, electronic equipment and storage medium | |
| JP6279816B2 (en) | Storage monitoring system and monitoring method thereof | |
| CN118689411A (en) | Quota management method, computer device, storage medium and program product | |
| US20140089624A1 (en) | Cooperation of hoarding memory allocators in a multi-process system | |
| CN113760940B (en) | Quota management method, device, equipment and medium applied to distributed system | |
| WO2020233364A1 (en) | Resource processing platform confirmation method and apparatus, and electronic device and medium | |
| CN113285890B (en) | Gateway flow distribution method and device, electronic equipment and storage medium | |
| CN116684496A (en) | Cluster resource management method, device, equipment and medium | |
| CN117176813A (en) | Method and device for processing service request | |
| CN115437794B (en) | I/O request scheduling method and device, electronic equipment and storage medium | |
| CN116095007A (en) | Load scheduling method, device, computer equipment and storage medium | |
| US20230196421A1 (en) | Program, information processing method, and information processing apparatus |
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 |