CN110868323A - Bandwidth control method, device, equipment and medium - Google Patents
Bandwidth control method, device, equipment and medium Download PDFInfo
- Publication number
- CN110868323A CN110868323A CN201911122501.6A CN201911122501A CN110868323A CN 110868323 A CN110868323 A CN 110868323A CN 201911122501 A CN201911122501 A CN 201911122501A CN 110868323 A CN110868323 A CN 110868323A
- Authority
- CN
- China
- Prior art keywords
- client
- bandwidth
- request
- write
- read
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/70—Admission control; Resource allocation
- H04L47/80—Actions related to the user profile or the type of traffic
- H04L47/805—QOS or priority aware
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Abstract
The application discloses a bandwidth control method, a device, equipment and a medium, comprising the following steps: acquiring a client request sent by a client; if the client request is a mounting request, judging whether the number of the clients currently linked by the node reaches a preset connection number threshold value, if not, utilizing a preset QOS bandwidth control mode to correspondingly process the mounting request, and if so, rejecting the mounting request; if the client request is a read-write request, counting real-time read-write bandwidths of all clients currently linked by the node, if the real-time read-write bandwidths are smaller than the bandwidth threshold of the NFS service node of the node, correspondingly processing the read-write request, and if the real-time read-write bandwidths reach the bandwidth threshold of the NFS service node of the node, refusing to receive the corresponding read-write request. Therefore, the maximization of the number of the connected clients and the maximization of the bandwidth utilization can be realized, so that the bandwidth utilization rate is improved, and the stability of the cluster is ensured.
Description
Technical Field
The present application relates to the field of cluster bandwidth management technologies, and in particular, to a bandwidth control method, apparatus, device, and medium.
Background
In the process of building and using the cluster, the bandwidth and the connection number are very important indexes and are important indications of the cluster performance, and high requirements on the I/O (Input/Output) performance of the cluster are met during large-scale parallel computing and storage. When the cluster frequently performs I/O operation, great pressure is brought to the bandwidth and the connection number of the cluster, so that it is necessary to research the bandwidth and connection number control allocation strategy of the cluster.
The NFS (Network File System ) receives a File System Call request sent by a client, forwards the request to a cluster server through an RPC (Remote Procedure Call), performs corresponding operations on the File System through calling a local File System on a server at the server, and returns information to the client after the operations are completed. Generally, a cluster usually has one or more service terminals to provide services, the number of corresponding clients is much larger than that of the service terminals, especially in some scenarios, frequent I/O operations performed by a plurality of clients may bring about little pressure on the bandwidth of the cluster service terminals, and at present, there is a problem that the number of connected clients of the service terminals and the bandwidth allocation are unreasonable.
Disclosure of Invention
In view of this, an object of the present application is to provide a bandwidth control method, apparatus, device and medium, which can achieve maximization of the number of actually connected clients and maximization of bandwidth utilization under the condition that the number of cluster node connected clients and bandwidth are limited, thereby improving bandwidth utilization and ensuring cluster stability. The specific scheme is as follows:
in a first aspect, the present application discloses a bandwidth control method, which is applied to any NFS service node in a cluster, and includes:
acquiring a client request sent by a client;
if the client requests are mounting requests, judging whether the number of the clients currently linked by the node reaches a preset connection number threshold value, if the number of the clients currently linked does not reach the preset connection number threshold value, performing corresponding processing on the mounting requests by using a preset QOS bandwidth control mode, and if the number of the clients currently linked reaches the preset connection number threshold value, rejecting the mounting requests;
if the client request is a read-write request, counting real-time read-write bandwidths of all clients currently linked by the node, if the real-time read-write bandwidths are smaller than the bandwidth threshold of the NFS service node of the node, performing corresponding processing on the read-write request, and if the real-time read-write bandwidths reach the bandwidth threshold of the NFS service node of the node, refusing to receive the corresponding read-write request.
Optionally, the performing, by using a preset QOS bandwidth control mode, corresponding processing on the mount request includes:
carrying out corresponding processing on the mounting request by utilizing a sharing mode; receiving the mounting request, establishing a link with a client corresponding to the current mounting request, and issuing a warning exceeding a theoretical bandwidth to the client corresponding to the current mounting request if the total preset allocated bandwidth of the client currently linked with the node is greater than the bandwidth threshold of the NFS service node after the link is established; the preset distribution bandwidth is determined by a preset read-write bandwidth threshold value of a client;
or, the mounting request is correspondingly processed by using an exclusive mode; if the total preset allocated bandwidth of the client currently linked with the node is smaller than the bandwidth threshold of the NFS service node, determining a bandwidth difference value between a total preset allocation bandwidth of the currently linked client of the node and the bandwidth threshold of the NFS service node, if the bandwidth difference value is greater than or equal to a preset allocation bandwidth of the client corresponding to the current mount request, receiving the mounting request, establishing a link with the client corresponding to the current mounting request, if the bandwidth difference is smaller than the preset allocated bandwidth of the client corresponding to the current mounting request, and receiving the mounting request, establishing a link with a client corresponding to the current mounting request, determining the bandwidth difference as the allocated bandwidth of the client, and rejecting the mounting request if the total preset allocated bandwidth of the client currently linked with the node reaches the bandwidth threshold of the NFS service node.
Optionally, after obtaining the client request sent by the client, the method further includes:
analyzing the client request to obtain a request type and a client IP corresponding to the client request; wherein the request type comprises the mount request and the read-write request.
Optionally, before the performing corresponding processing on the mount request by using the preset QOS bandwidth control mode, the method further includes:
searching whether a client IP in a current mounting request exists in locally stored client configuration information, if so, searching a client preset read-write bandwidth threshold of the current client IP from the client configuration information to obtain the client preset read-write bandwidth threshold corresponding to the current client, if not, acquiring a client default read-write bandwidth threshold from the client configuration information, and determining a preset distribution bandwidth of the current client by using the client default read-write bandwidth threshold.
Optionally, the performing corresponding processing on the read-write request includes:
and putting the read-write request into a request queue corresponding to the current client IP, and establishing a corresponding thread for read-write processing.
Optionally, before the obtaining of the client request sent by the client, the method further includes:
creating a configuration file; the configuration file comprises the preset connection quantity threshold, the NFS service node bandwidth threshold and client configuration information; the client configuration information comprises a client preset read-write bandwidth threshold, a client default read-write bandwidth threshold and a client IP; and the client side preset read-write bandwidth threshold corresponds to the client side IP.
Optionally, the method further includes:
and modifying the configuration file, and then synchronizing the modified configuration file to other nodes.
In a second aspect, the present application discloses a bandwidth control apparatus, which is applied to any NFS service node in a cluster, and includes:
the client request acquisition module is used for acquiring a client request sent by a client;
the mounting request processing module is used for judging whether the number of the currently linked clients of the node reaches a preset connection number threshold value or not if the client request is the mounting request, performing corresponding processing on the mounting request by using a preset QOS bandwidth control mode if the number of the currently linked clients does not reach the preset connection number threshold value, and rejecting the mounting request if the number of the currently linked clients reaches the preset connection number threshold value;
and the read-write request processing module is used for counting real-time read-write bandwidths of all clients currently linked by the node if the client requests are read-write requests, correspondingly processing the read-write requests if the real-time read-write bandwidths are smaller than the bandwidth threshold of the NFS service node of the node, and refusing to receive the corresponding read-write requests if the real-time read-write bandwidths reach the bandwidth threshold of the NFS service node of the node.
In a third aspect, the present application discloses a bandwidth control device comprising a processor and a memory; wherein the content of the first and second substances,
the memory is used for storing a computer program;
the processor is configured to execute the computer program to implement the foregoing bandwidth control method.
In a fourth aspect, the present application discloses a computer readable storage medium for storing a computer program, wherein the computer program when executed by a processor implements the aforementioned bandwidth control method.
It can be seen that, in the present application, a client request sent by a client is obtained first, if the client request is a mount request, it is determined whether the number of currently linked clients of the node reaches a preset connection number threshold, if the number of currently linked clients does not reach the preset connection number threshold, a preset QOS bandwidth control mode is used to perform corresponding processing on the mount request, and if the number of currently linked clients reaches the preset connection number threshold, the mount request is rejected. If the client request is a read-write request, counting real-time read-write bandwidths of all clients currently linked by the node, if the real-time read-write bandwidths are smaller than the bandwidth threshold of the NFS service node of the node, performing corresponding processing on the read-write request, and if the real-time read-write bandwidths reach the bandwidth threshold of the NFS service node of the node, refusing to receive the corresponding read-write request. Therefore, when the client sends the mounting request, the mounting request is correspondingly processed by using the preset connection quantity threshold and the QOS bandwidth control mode, and when the client sends the read-write request, the read-write request is processed according to the real-time bandwidth of the currently linked client, so that the maximization of the actual connection client quantity and the maximization of the bandwidth utilization can be realized under the condition that the cluster node is connected with the limited number of the clients and the limited bandwidth, the bandwidth utilization rate is improved, and the stability of the cluster is ensured.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
FIG. 1 is a flow chart of a bandwidth control method disclosed herein;
fig. 2 is a flow chart of a specific bandwidth control method disclosed in the present application;
fig. 3 is a flow chart illustrating a specific bandwidth control method disclosed in the present application;
FIG. 4 is a schematic structural diagram of a bandwidth control apparatus disclosed herein;
FIG. 5 is a logic diagram of an exemplary bandwidth control device disclosed herein;
FIG. 6 is a block diagram of a bandwidth control apparatus as disclosed herein;
fig. 7 is a diagram of a server structure disclosed in the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, an embodiment of the present application discloses a bandwidth control method, which is applied to any NFS service node in a cluster, and includes:
step S11: and acquiring a client request sent by the client.
In a specific implementation manner, when a client request sent by a client is obtained, the client request is analyzed to obtain a request type and a client IP corresponding to the client request; the request types comprise mounting requests and reading and writing requests.
Step S12: if the client request is a mount request, judging whether the number of the currently linked clients of the node reaches a preset connection number threshold, if not, utilizing a preset QOS (Quality of Service) bandwidth control mode to correspondingly process the mount request, and if so, rejecting the mount request.
That is, in this embodiment, after acquiring the attach request sent by the client, it is first determined whether the number of currently linked clients of the node reaches a preset connection number threshold, and if the number of currently linked clients does not reach the preset connection number threshold, the mount request is correspondingly processed by using a preset QOS bandwidth control mode.
In a specific implementation manner, the mount request may be processed correspondingly by using a sharing mode, specifically, the mount request is received, a link is established with a client corresponding to the current mount request, and if the link is established, and the total preset allocated bandwidth of the client currently linked with the node is greater than the bandwidth threshold of the NFS service node, a warning exceeding the theoretical bandwidth is issued to the client corresponding to the current mount request; and the preset distribution bandwidth is determined by a preset read-write bandwidth threshold value of the client. For example, if the read bandwidth threshold is preset by the client to be 50M, the preset allocated bandwidth of the client is 50M. That is, in the sharing mode, the total allocated bandwidth of all the mounted clients may exceed the total bandwidth of the cluster node, but the actual traffic does not exceed the node limit, that is, the actual used total bandwidth of all the mounted clients does not exceed the bandwidth threshold of the node, for example, the NFS node read bandwidth threshold is 50M, the write bandwidth is 50M, and the client default bandwidth is set to 20M; the client C1 is linked successfully, the read bandwidth threshold is 20M, and the write bandwidth threshold is 20M; the client C2 is linked successfully, the read bandwidth threshold is 20M, and the write bandwidth threshold is 20M; when the client C3 is linked, the setting is successful, and an alarm exceeding the theoretical bandwidth threshold is sent out; the client C4 links successfully and sends out an alarm of exceeding the theoretical bandwidth, and so on, when the number of currently linked clients does not reach the preset connection number threshold, the client may be allowed to mount, when the actual flow of the node reaches 50M, an actual bandwidth alarm is sent out, but the client is still allowed to link, and when processing read and write requests of all clients, it needs to be determined whether the real-time bandwidth of all currently connected clients exceeds the node bandwidth threshold.
In another specific embodiment, the mount request is processed correspondingly by using an exclusive mode; if the total preset allocated bandwidth of the client currently linked with the node is smaller than the bandwidth threshold of the NFS service node, determining a bandwidth difference value between a total preset allocation bandwidth of the currently linked client of the node and the bandwidth threshold of the NFS service node, if the bandwidth difference value is greater than or equal to a preset allocation bandwidth of the client corresponding to the current mount request, receiving the mounting request, establishing a link with the client corresponding to the current mounting request, if the bandwidth difference is smaller than the preset allocated bandwidth of the client corresponding to the current mounting request, and receiving the mounting request, establishing a link with a client corresponding to the current mounting request, determining the bandwidth difference as the allocated bandwidth of the client, and rejecting the mounting request if the total preset allocated bandwidth of the client currently linked with the node reaches the bandwidth threshold of the NFS service node. That is, in the exclusive mode, the total allocated bandwidth of the mount client is not greater than the total bandwidth of the node. For example, the reading bandwidth threshold of the NFS node is 50M, the writing bandwidth is 50M, and the default bandwidth of the client is set to 20M; the client C1 is linked successfully, the read bandwidth threshold is 20M, and the write bandwidth threshold is 20M; the client C2 is linked successfully, the read bandwidth threshold is 20M, and the write bandwidth threshold is 20M; when the client C3 is linked, the read-write bandwidth threshold is 10M, an alarm is sent out, and other client links are limited. When processing the client read-write request, only judging whether the current client threshold is exceeded, and when the client is released, restoring the threshold of C3 to 20M.
If the mounting is successful, recording the corresponding client IP and the client bandwidth information into the corresponding structural body, and updating the real-time used bandwidth of the node; and if the link quantity threshold value is exceeded, outputting corresponding alarm information.
In addition, in this embodiment, before the mount request is correspondingly processed by using a preset QOS bandwidth control mode, whether a client IP in the current mount request exists in locally stored client configuration information may be searched, if the client IP exists in the client configuration information, a client preset read-write bandwidth threshold of the current client IP is searched from the client configuration information, so as to obtain the client preset read-write bandwidth threshold corresponding to the current client, and if the client configuration information does not have the current client IP, a client default read-write bandwidth threshold is obtained from the client configuration information, and a preset allocation bandwidth of the current client is determined by using the client default read-write bandwidth threshold. That is, the client-side default read-write bandwidth threshold is determined as the preset allocated bandwidth of the current client-side.
Step S13: if the client request is a read-write request, counting real-time read-write bandwidths of all clients currently linked by the node, if the real-time read-write bandwidths are smaller than the bandwidth threshold of the NFS service node of the node, performing corresponding processing on the read-write request, and if the real-time read-write bandwidths reach the bandwidth threshold of the NFS service node of the node, refusing to receive the corresponding read-write request.
In a specific implementation manner, the read-write request is placed in a request queue corresponding to the current client IP, and a corresponding thread is created for read-write processing. That is, the NFS service node divides the read-write requests according to the IP, puts the read-write requests of the same IP into the same queue, and creates a certain number of threads for processing. And when the bandwidth threshold is exceeded, limiting the client, setting the corresponding flag position as true, judging whether the client exceeds the threshold according to the flag position when the network layer receives the data message, and stopping receiving the client request if the client exceeds the threshold.
As can be seen, in the embodiment of the present application, a client request sent by a client is obtained first, if the client request is a mount request, it is determined whether the number of currently linked clients of the node reaches a preset connection number threshold, if the number of currently linked clients does not reach the preset connection number threshold, a preset QOS bandwidth control mode is used to perform corresponding processing on the mount request, and if the number of currently linked clients reaches the preset connection number threshold, the mount request is rejected. If the client request is a read-write request, counting real-time read-write bandwidths of all clients currently linked by the node, if the real-time read-write bandwidths are smaller than the bandwidth threshold of the NFS service node of the node, performing corresponding processing on the read-write request, and if the real-time read-write bandwidths reach the bandwidth threshold of the NFS service node of the node, refusing to receive the corresponding read-write request. Therefore, when the client sends the mounting request, the mounting request is correspondingly processed by using the preset connection quantity threshold and the QOS bandwidth control mode, and when the client sends the read-write request, the read-write request is processed according to the real-time bandwidth of the currently linked client, so that the maximization of the actual connection client quantity and the maximization of the bandwidth utilization can be realized under the condition that the cluster node is connected with the limited number of the clients and the limited bandwidth, the bandwidth utilization rate is improved, and the stability of the cluster is ensured.
Referring to fig. 2, fig. 2 is a specific bandwidth control method disclosed in the present application, which is applied to any NFS service node in a cluster, and includes:
step S21: creating a configuration file; the configuration file comprises the preset connection quantity threshold, the NFS service node bandwidth threshold and client configuration information; the client configuration information comprises a client preset read-write bandwidth threshold, a client default read-write bandwidth threshold and a client IP; and the client side preset read-write bandwidth threshold corresponds to the client side IP.
In a specific implementation manner, the created configuration file may include the connection number of all nodes in the cluster and default values of the bandwidth threshold, or may configure corresponding bandwidth thresholds and connection number thresholds for individual nodes, and configure the client configuration information, including the client preset read-write bandwidth threshold, the client default read-write bandwidth threshold, and the client preset read-write bandwidth threshold corresponding to the client IP. After the configuration file is created, the configuration file needs to be synchronized to other nodes in the cluster. When the NFS service is started, the cluster node reads configuration information from the configuration file, and puts IP and bandwidth setting information into a corresponding linked list structure. That is, the corresponding read-write bandwidth threshold may be set for the client IP, or the client default read-write bandwidth threshold may also be set.
Step S22: and acquiring a client request sent by the client.
Step S23: if the client requests are mounting requests, whether the number of the clients currently linked by the node reaches a preset connection number threshold value is judged, if the number of the clients currently linked does not reach the preset connection number threshold value, a preset QOS bandwidth control mode is utilized to correspondingly process the mounting requests, and if the number of the clients currently linked reaches the preset connection number threshold value, the mounting requests are rejected.
Step S24: if the client request is a read-write request, counting real-time read-write bandwidths of all clients currently linked by the node, if the real-time read-write bandwidths are smaller than the bandwidth threshold of the NFS service node of the node, performing corresponding processing on the read-write request, and if the real-time read-write bandwidths reach the bandwidth threshold of the NFS service node of the node, refusing to receive the corresponding read-write request.
Step S25: the configuration file is modified.
And allowing the client IP and the corresponding bandwidth information to be dynamically modified in use, namely, the client preset read-write bandwidth threshold and the client default read-write bandwidth threshold, wherein the configuration needs to be synchronized to other nodes after modification. Also, individual server node defaults, cluster all nodes defaults, and client defaults may be modified. That is, the connection number threshold and the node bandwidth threshold of a single server-side node, the connection number threshold and the default of the node bandwidth threshold of all the nodes in the cluster, and the client configuration information include the client preset read-write bandwidth threshold, the client default read-write bandwidth threshold, and the corresponding client IP may be modified.
Moreover, when the NFS node is switched or restarted, the connection may be switched to another node in a load balancing manner, and at this time, after the other server node receives a new client request, the bandwidth control method described in the foregoing embodiment is performed.
For example, referring to fig. 3, fig. 3 is a specific bandwidth control flow chart disclosed in the present application. The method comprises the steps that an NFS service node is started, a configuration file is analyzed, configuration information in the configuration file is obtained, then network data is read, a client request is obtained from the network data, then the request is analyzed, the request type is judged, if the client request is a mounting request, whether the number of clients currently linked by the node reaches a preset connection number threshold value is judged, if yes, the request is refused to be received, and if not, corresponding request processing is carried out. And if the client requests are read-write requests, counting real-time read-write bandwidths of all clients currently linked by the node, if the current implementation bandwidth reaches a preset node bandwidth threshold value, refusing to receive the requests, and otherwise, processing the current requests. Therefore, storage service management and reasonable allocation of storage resources are facilitated, and the maximization of the number of actually connected clients and the maximization of bandwidth utilization are realized, so that the bandwidth utilization rate is improved, and the stability of a cluster is ensured.
Referring to fig. 4, an embodiment of the present application discloses a bandwidth control apparatus, which is applied to any NFS service node in a cluster, and includes:
the client request obtaining module 11 is configured to obtain a client request sent by a client.
A mount request processing module 12, configured to determine, if the client request is a mount request, whether the number of clients currently linked by the node reaches a preset connection number threshold, if the number of clients currently linked does not reach the preset connection number threshold, perform corresponding processing on the mount request by using a preset QOS bandwidth control mode, and if the number of clients currently linked reaches the preset connection number threshold, reject the mount request.
A read-write request processing module 13, configured to count real-time read-write bandwidths of all clients currently linked to the node if the client request is a read-write request, perform corresponding processing on the read-write request if the real-time read-write bandwidth is smaller than a bandwidth threshold of an NFS service node of the node, and refuse to receive the corresponding read-write request if the real-time read-write bandwidth reaches the bandwidth threshold of the NFS service node of the node.
As can be seen, in the embodiment of the present application, a client request sent by a client is obtained first, if the client request is a mount request, it is determined whether the number of currently linked clients of the node reaches a preset connection number threshold, if the number of currently linked clients does not reach the preset connection number threshold, a preset QOS bandwidth control mode is used to perform corresponding processing on the mount request, and if the number of currently linked clients reaches the preset connection number threshold, the mount request is rejected. If the client request is a read-write request, counting real-time read-write bandwidths of all clients currently linked by the node, if the real-time read-write bandwidths are smaller than the bandwidth threshold of the NFS service node of the node, performing corresponding processing on the read-write request, and if the real-time read-write bandwidths reach the bandwidth threshold of the NFS service node of the node, refusing to receive the corresponding read-write request. Therefore, when the client sends the mounting request, the mounting request is correspondingly processed by using the preset connection quantity threshold and the QOS bandwidth control mode, and when the client sends the read-write request, the read-write request is processed according to the real-time bandwidth of the currently linked client, so that the maximization of the actual connection client quantity and the maximization of the bandwidth utilization can be realized under the condition that the cluster node is connected with the limited number of the clients and the limited bandwidth, the bandwidth utilization rate is improved, and the stability of the cluster is ensured.
Wherein, the mounting request processing module 12 comprises a mounting request processing submodule,
in a specific implementation manner, the mount request processing sub-module is configured to perform corresponding processing on the mount request by using a QOS sharing mode, specifically, receive the mount request, establish a link with a client corresponding to the current mount request, and issue a warning that a theoretical bandwidth is exceeded to the client corresponding to the current mount request if a total preset allocated bandwidth of the client currently linked to the node is greater than a bandwidth threshold of the NFS service node after the link is established; the preset distribution bandwidth is determined by a preset read-write bandwidth threshold value of a client;
in another specific embodiment, the mount request processing sub-module is configured to perform corresponding processing on the mount request in a QOS exclusive mode, specifically, if a total preset allocated bandwidth of a client currently linked to the node is smaller than the NFS service node bandwidth threshold, determine a bandwidth difference between the total preset allocated bandwidth of the client currently linked to the node and the NFS service node bandwidth threshold, if the bandwidth difference is greater than or equal to a preset allocated bandwidth of a client corresponding to the current mount request, accept the mount request and establish a link with the client corresponding to the current mount request, if the bandwidth difference is smaller than the preset allocated bandwidth of the client corresponding to the current mount request, accept the mount request and establish a link with the client corresponding to the current mount request, and determine the bandwidth difference as the allocated bandwidth of the client, and if the total preset allocated bandwidth of the client currently linked with the node reaches the bandwidth threshold of the NFS service node, rejecting the mounting request.
The bandwidth control device also comprises a request analysis module used for analyzing the client request to obtain a request type and a client IP corresponding to the client request; wherein the request type comprises the mount request and the read-write request.
The bandwidth control device further comprises a client configuration information searching module, which is used for searching whether the client IP in the current mounting request exists in locally stored client configuration information, if the current client IP exists in the client configuration information, searching a client preset read-write bandwidth threshold of the current client IP from the client configuration information to obtain the client preset read-write bandwidth threshold corresponding to the current client, if the current client IP does not exist in the client configuration information, acquiring a client default read-write bandwidth threshold from the client configuration information, and determining the preset distribution bandwidth of the current client by using the client default read-write bandwidth threshold.
The read-write request processing module 13 includes a read-write request processing sub-module, and is configured to place the read-write request into a request queue corresponding to the current client IP, and create a corresponding thread for read-write processing.
The bandwidth control device also comprises a configuration file creating module used for creating a configuration file; the configuration file comprises the preset connection quantity threshold, the NFS service node bandwidth threshold and client configuration information; the client configuration information comprises a client preset read-write bandwidth threshold, a client default read-write bandwidth threshold and a client IP; and the client side preset read-write bandwidth threshold corresponds to the client side IP.
The bandwidth control device also comprises a configuration file modification module used for modifying the configuration file and then synchronizing the modified configuration file to other nodes.
For example, referring to fig. 5, fig. 5 is a logic diagram of a specific bandwidth control apparatus, which includes a configuration management module, configured to implement setting and modification of connection number, bandwidth resource, and the like according to a configuration file and a command; the interface client in the figure requests the function of the acquisition module, namely the client request is acquired through the interface; the mounting request module function is realized through the connection number management module and the QOS management control module, and the connection number management module is used for realizing the control of the connection number of the nodes and giving a warning when the connection number exceeds the connection number; the QOS management control module is used for the QOS bandwidth control module to correspondingly process the mounting request, namely control the node connection book, and comprises the functions of node bandwidth control and client bandwidth control; the read-write request module function is realized through the node bandwidth management module, the client bandwidth control module and the QOS bandwidth control mode module, and the node bandwidth management module is used for realizing node bandwidth control, including node bandwidth inquiry, and warning and limiting are carried out after the bandwidth exceeds a node bandwidth threshold; and the client bandwidth control module is used for monitoring the bandwidth of each client, stopping receiving the client request when the bandwidth exceeds a threshold value, and performing a client bandwidth query function. CTDB (i.e., Cluster trivirtual Database) for monitoring the service of the Cluster nodes.
Referring to fig. 6, an embodiment of the present application discloses a bandwidth control device, which includes a processor 21 and a memory 22; wherein, the memory 22 is used for saving computer programs; the processor 21 is configured to execute the computer program to implement the following steps:
acquiring a client request sent by a client; if the client requests are mounting requests, judging whether the number of the clients currently linked by the node reaches a preset connection number threshold value, if the number of the clients currently linked does not reach the preset connection number threshold value, performing corresponding processing on the mounting requests by using a preset QOS bandwidth control mode, and if the number of the clients currently linked reaches the preset connection number threshold value, rejecting the mounting requests; if the client request is a read-write request, counting real-time read-write bandwidths of all clients currently linked by the node, if the real-time read-write bandwidths are smaller than the bandwidth threshold of the NFS service node of the node, performing corresponding processing on the read-write request, and if the real-time read-write bandwidths reach the bandwidth threshold of the NFS service node of the node, refusing to receive the corresponding read-write request.
As can be seen, in the embodiment of the present application, a client request sent by a client is obtained first, if the client request is a mount request, it is determined whether the number of currently linked clients of the node reaches a preset connection number threshold, if the number of currently linked clients does not reach the preset connection number threshold, a preset QOS bandwidth control mode is used to perform corresponding processing on the mount request, and if the number of currently linked clients reaches the preset connection number threshold, the mount request is rejected. If the client request is a read-write request, counting real-time read-write bandwidths of all clients currently linked by the node, if the real-time read-write bandwidths are smaller than the bandwidth threshold of the NFS service node of the node, performing corresponding processing on the read-write request, and if the real-time read-write bandwidths reach the bandwidth threshold of the NFS service node of the node, refusing to receive the corresponding read-write request. Therefore, when the client sends the mounting request, the mounting request is correspondingly processed by using the preset connection quantity threshold and the QOS bandwidth control mode, and when the client sends the read-write request, the read-write request is processed according to the real-time bandwidth of the currently linked client, so that the maximization of the actual connection client quantity and the maximization of the bandwidth utilization can be realized under the condition that the cluster node is connected with the limited number of the clients and the limited bandwidth, the bandwidth utilization rate is improved, and the stability of the cluster is ensured.
In this embodiment, when the processor 21 executes the computer subprogram stored in the memory 22, the following steps may be specifically implemented: carrying out corresponding processing on the mounting request by utilizing a sharing mode; receiving the mounting request, establishing a link with a client corresponding to the current mounting request, and issuing a warning exceeding a theoretical bandwidth to the client corresponding to the current mounting request if the total preset allocated bandwidth of the client currently linked with the node is greater than the bandwidth threshold of the NFS service node after the link is established; the preset distribution bandwidth is determined by a preset read-write bandwidth threshold value of a client; or, the mounting request is correspondingly processed by using an exclusive mode; if the total preset allocated bandwidth of the client currently linked with the node is smaller than the bandwidth threshold of the NFS service node, determining a bandwidth difference value between a total preset allocation bandwidth of the currently linked client of the node and the bandwidth threshold of the NFS service node, if the bandwidth difference value is greater than or equal to a preset allocation bandwidth of the client corresponding to the current mount request, receiving the mounting request, establishing a link with the client corresponding to the current mounting request, if the bandwidth difference is smaller than the preset allocated bandwidth of the client corresponding to the current mounting request, and receiving the mounting request, establishing a link with a client corresponding to the current mounting request, determining the bandwidth difference as the allocated bandwidth of the client, and rejecting the mounting request if the total preset allocated bandwidth of the client currently linked with the node reaches the bandwidth threshold of the NFS service node.
In this embodiment, when the processor 21 executes the computer subprogram stored in the memory 22, the following steps may be specifically implemented: analyzing the client request to obtain a request type and a client IP corresponding to the client request; wherein the request type comprises the mount request and the read-write request.
In this embodiment, when the processor 21 executes the computer subprogram stored in the memory 22, the following steps may be specifically implemented: searching whether a client IP in a current mounting request exists in locally stored client configuration information, if so, searching a client preset read-write bandwidth threshold of the current client IP from the client configuration information to obtain the client preset read-write bandwidth threshold corresponding to the current client, if not, acquiring a client default read-write bandwidth threshold from the client configuration information, and determining a preset distribution bandwidth of the current client by using the client default read-write bandwidth threshold.
In this embodiment, when the processor 21 executes the computer subprogram stored in the memory 22, the following steps may be specifically implemented: and putting the read-write request into a request queue corresponding to the current client IP, and establishing a corresponding thread for read-write processing.
In this embodiment, when the processor 21 executes the computer subprogram stored in the memory 22, the following steps may be specifically implemented: creating a configuration file; the configuration file comprises the preset connection quantity threshold, the NFS service node bandwidth threshold and client configuration information; the client configuration information comprises a client preset read-write bandwidth threshold, a client default read-write bandwidth threshold and a client IP; and the client side preset read-write bandwidth threshold corresponds to the client side IP.
In this embodiment, when the processor 21 executes the computer subprogram stored in the memory 22, the following steps may be specifically implemented: and modifying the configuration file, and then synchronizing the modified configuration file to other nodes.
The memory 22 is used as a carrier for resource storage, and may be a read-only memory, a random access memory, a magnetic disk or an optical disk, and the storage manner may be a transient storage or a permanent storage.
Referring to fig. 7, the present application discloses a server 20 including a bandwidth control device including a processor 21 and a memory 22 disclosed in the foregoing embodiments. For the steps that the processor 21 can specifically execute, reference may be made to corresponding contents disclosed in the foregoing embodiments, and details are not described herein again.
Further, the server 20 in this embodiment may further specifically include a power supply 23, a communication interface 24, an input/output interface 25, and a communication bus 26; the power supply 23 is configured to provide operating voltage for each hardware device on the server 20; the communication interface 24 can create a data transmission channel between the server 20 and an external device, and a communication protocol followed by the communication interface is any communication protocol applicable to the technical solution of the present application, and is not specifically limited herein; the input/output interface 25 is configured to obtain external input data or output data to the outside, and a specific interface type thereof may be selected according to specific application requirements, which is not specifically limited herein.
Further, an embodiment of the present application also discloses a computer readable storage medium for storing a computer program, wherein the computer program, when executed by a processor, implements the following steps:
acquiring a client request sent by a client; if the client requests are mounting requests, judging whether the number of the clients currently linked by the node reaches a preset connection number threshold value, if the number of the clients currently linked does not reach the preset connection number threshold value, performing corresponding processing on the mounting requests by using a preset QOS bandwidth control mode, and if the number of the clients currently linked reaches the preset connection number threshold value, rejecting the mounting requests; if the client request is a read-write request, counting real-time read-write bandwidths of all clients currently linked by the node, if the real-time read-write bandwidths are smaller than the bandwidth threshold of the NFS service node of the node, performing corresponding processing on the read-write request, and if the real-time read-write bandwidths reach the bandwidth threshold of the NFS service node of the node, refusing to receive the corresponding read-write request.
As can be seen, in the embodiment of the present application, a client request sent by a client is obtained first, if the client request is a mount request, it is determined whether the number of currently linked clients of the node reaches a preset connection number threshold, if the number of currently linked clients does not reach the preset connection number threshold, a preset QOS bandwidth control mode is used to perform corresponding processing on the mount request, and if the number of currently linked clients reaches the preset connection number threshold, the mount request is rejected. If the client request is a read-write request, counting real-time read-write bandwidths of all clients currently linked by the node, if the real-time read-write bandwidths are smaller than the bandwidth threshold of the NFS service node of the node, performing corresponding processing on the read-write request, and if the real-time read-write bandwidths reach the bandwidth threshold of the NFS service node of the node, refusing to receive the corresponding read-write request. Therefore, when the client sends the mounting request, the mounting request is correspondingly processed by using the preset connection quantity threshold and the QOS bandwidth control mode, and when the client sends the read-write request, the read-write request is processed according to the real-time bandwidth of the currently linked client, so that the maximization of the actual connection client quantity and the maximization of the bandwidth utilization can be realized under the condition that the cluster node is connected with the limited number of the clients and the limited bandwidth, the bandwidth utilization rate is improved, and the stability of the cluster is ensured.
In this embodiment, when the computer subprogram stored in the computer-readable storage medium is executed by the processor, the following steps may be specifically implemented: carrying out corresponding processing on the mounting request by utilizing a sharing mode; receiving the mounting request, establishing a link with a client corresponding to the current mounting request, and issuing a warning exceeding a theoretical bandwidth to the client corresponding to the current mounting request if the total preset allocated bandwidth of the client currently linked with the node is greater than the bandwidth threshold of the NFS service node after the link is established; the preset distribution bandwidth is determined by a preset read-write bandwidth threshold value of a client; or, the mounting request is correspondingly processed by using an exclusive mode; if the total preset allocated bandwidth of the client currently linked with the node is smaller than the bandwidth threshold of the NFS service node, determining a bandwidth difference value between a total preset allocation bandwidth of the currently linked client of the node and the bandwidth threshold of the NFS service node, if the bandwidth difference value is greater than or equal to a preset allocation bandwidth of the client corresponding to the current mount request, receiving the mounting request, establishing a link with the client corresponding to the current mounting request, if the bandwidth difference is smaller than the preset allocated bandwidth of the client corresponding to the current mounting request, and receiving the mounting request, establishing a link with a client corresponding to the current mounting request, determining the bandwidth difference as the allocated bandwidth of the client, and rejecting the mounting request if the total preset allocated bandwidth of the client currently linked with the node reaches the bandwidth threshold of the NFS service node.
In this embodiment, when the computer subprogram stored in the computer-readable storage medium is executed by the processor, the following steps may be specifically implemented: analyzing the client request to obtain a request type and a client IP corresponding to the client request; wherein the request type comprises the mount request and the read-write request.
In this embodiment, when the computer subprogram stored in the computer-readable storage medium is executed by the processor, the following steps may be specifically implemented: searching whether a client IP in a current mounting request exists in locally stored client configuration information, if so, searching a client preset read-write bandwidth threshold of the current client IP from the client configuration information to obtain the client preset read-write bandwidth threshold corresponding to the current client, if not, acquiring a client default read-write bandwidth threshold from the client configuration information, and determining a preset distribution bandwidth of the current client by using the client default read-write bandwidth threshold.
In this embodiment, when the computer subprogram stored in the computer-readable storage medium is executed by the processor, the following steps may be specifically implemented: and putting the read-write request into a request queue corresponding to the current client IP, and establishing a corresponding thread for read-write processing.
In this embodiment, when the computer subprogram stored in the computer-readable storage medium is executed by the processor, the following steps may be specifically implemented: creating a configuration file; the configuration file comprises the preset connection quantity threshold, the NFS service node bandwidth threshold and client configuration information; the client configuration information comprises a client preset read-write bandwidth threshold, a client default read-write bandwidth threshold and a client IP; and the client side preset read-write bandwidth threshold corresponds to the client side IP.
In this embodiment, when the computer subprogram stored in the computer-readable storage medium is executed by the processor, the following steps may be specifically implemented: and modifying the configuration file, and then synchronizing the modified configuration file to other nodes.
The embodiments are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same or similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The foregoing detailed description is directed to a method, an apparatus, a device, and a medium for controlling bandwidth provided by the present application, and a specific example is applied in the detailed description to explain the principles and embodiments of the present application, and the description of the foregoing embodiment is only used to help understand the method and the core idea of the present application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (10)
1. A bandwidth control method is applied to any NFS service node in a cluster, and comprises the following steps:
acquiring a client request sent by a client;
if the client requests are mounting requests, judging whether the number of the clients currently linked by the node reaches a preset connection number threshold value, if the number of the clients currently linked does not reach the preset connection number threshold value, performing corresponding processing on the mounting requests by using a preset QOS bandwidth control mode, and if the number of the clients currently linked reaches the preset connection number threshold value, rejecting the mounting requests;
if the client request is a read-write request, counting real-time read-write bandwidths of all clients currently linked by the node, if the real-time read-write bandwidths are smaller than the bandwidth threshold of the NFS service node of the node, performing corresponding processing on the read-write request, and if the real-time read-write bandwidths reach the bandwidth threshold of the NFS service node of the node, refusing to receive the corresponding read-write request.
2. The bandwidth control method according to claim 1, wherein the performing the corresponding processing on the mount request by using the preset QOS bandwidth control mode comprises:
carrying out corresponding processing on the mounting request by utilizing a sharing mode; receiving the mounting request, establishing a link with a client corresponding to the current mounting request, and issuing a warning exceeding a theoretical bandwidth to the client corresponding to the current mounting request if the total preset allocated bandwidth of the client currently linked with the node is greater than the bandwidth threshold of the NFS service node after the link is established; the preset distribution bandwidth is determined by a preset read-write bandwidth threshold value of a client;
or, the mounting request is correspondingly processed by using an exclusive mode; if the total preset allocated bandwidth of the client currently linked with the node is smaller than the bandwidth threshold of the NFS service node, determining a bandwidth difference value between a total preset allocation bandwidth of the currently linked client of the node and the bandwidth threshold of the NFS service node, if the bandwidth difference value is greater than or equal to a preset allocation bandwidth of the client corresponding to the current mount request, receiving the mounting request, establishing a link with the client corresponding to the current mounting request, if the bandwidth difference is smaller than the preset allocated bandwidth of the client corresponding to the current mounting request, and receiving the mounting request, establishing a link with a client corresponding to the current mounting request, determining the bandwidth difference as the allocated bandwidth of the client, and rejecting the mounting request if the total preset allocated bandwidth of the client currently linked with the node reaches the bandwidth threshold of the NFS service node.
3. The bandwidth control method according to claim 2, wherein after obtaining the client request sent by the client, the method further comprises:
analyzing the client request to obtain a request type and a client IP corresponding to the client request; wherein the request type comprises the mount request and the read-write request.
4. The method of claim 3, wherein before the performing the corresponding processing on the mount request by using the preset QOS bandwidth control mode, the method further comprises:
searching whether a client IP in a current mounting request exists in locally stored client configuration information, if so, searching a client preset read-write bandwidth threshold of the current client IP from the client configuration information to obtain the client preset read-write bandwidth threshold corresponding to the current client, if not, acquiring a client default read-write bandwidth threshold from the client configuration information, and determining a preset distribution bandwidth of the current client by using the client default read-write bandwidth threshold.
5. The bandwidth control method according to claim 4, wherein the performing the corresponding processing on the read/write request includes:
and putting the read-write request into a request queue corresponding to the current client IP, and establishing a corresponding thread for read-write processing.
6. The bandwidth control method according to any one of claims 1 to 5, wherein before the obtaining the client request sent by the client, the method further comprises:
creating a configuration file; the configuration file comprises the preset connection quantity threshold, the NFS service node bandwidth threshold and client configuration information; the client configuration information comprises a client preset read-write bandwidth threshold, a client default read-write bandwidth threshold and a client IP; and the client side preset read-write bandwidth threshold corresponds to the client side IP.
7. The bandwidth control method of claim 6, further comprising:
and modifying the configuration file, and then synchronizing the modified configuration file to other nodes.
8. A bandwidth control apparatus, applied to any NFS service node in a cluster, includes:
the client request acquisition module is used for acquiring a client request sent by a client;
the mounting request processing module is used for judging whether the number of the currently linked clients of the node reaches a preset connection number threshold value or not if the client request is the mounting request, performing corresponding processing on the mounting request by using a preset QOS bandwidth control mode if the number of the currently linked clients does not reach the preset connection number threshold value, and rejecting the mounting request if the number of the currently linked clients reaches the preset connection number threshold value;
and the read-write request processing module is used for counting real-time read-write bandwidths of all clients currently linked by the node if the client requests are read-write requests, correspondingly processing the read-write requests if the real-time read-write bandwidths are smaller than the bandwidth threshold of the NFS service node of the node, and refusing to receive the corresponding read-write requests if the real-time read-write bandwidths reach the bandwidth threshold of the NFS service node of the node.
9. A bandwidth control device comprising a processor and a memory; wherein the content of the first and second substances,
the memory is used for storing a computer program;
the processor for executing the computer program to implement the bandwidth control method according to any one of claims 1 to 7.
10. A computer-readable storage medium for storing a computer program, wherein the computer program when executed by a processor implements the bandwidth control method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911122501.6A CN110868323B (en) | 2019-11-15 | 2019-11-15 | Bandwidth control method, device, equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911122501.6A CN110868323B (en) | 2019-11-15 | 2019-11-15 | Bandwidth control method, device, equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110868323A true CN110868323A (en) | 2020-03-06 |
| CN110868323B CN110868323B (en) | 2022-07-22 |
Family
ID=69654062
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911122501.6A Active CN110868323B (en) | 2019-11-15 | 2019-11-15 | Bandwidth control method, device, equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110868323B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112291310A (en) * | 2020-10-14 | 2021-01-29 | 杭州迪普科技股份有限公司 | Method and device for counting connection number |
| CN113835632A (en) * | 2021-09-17 | 2021-12-24 | 济南浪潮数据技术有限公司 | Method, system, equipment and storage medium for setting read-write bandwidth in batches |
| CN117041317A (en) * | 2023-10-09 | 2023-11-10 | 安徽隼波科技有限公司 | Method for managing connection between TCP multiple clients based on FreeRTOS |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105511805A (en) * | 2015-11-26 | 2016-04-20 | 深圳市中博科创信息技术有限公司 | Data processing method and device for cluster file system |
| CN107483637A (en) * | 2017-09-22 | 2017-12-15 | 郑州云海信息技术有限公司 | A kind of client link management method and device based on NFS |
| US9898482B1 (en) * | 2013-12-27 | 2018-02-20 | EMC IP Holding Company LLC | Managing stream connections in storage systems |
| CN109271112A (en) * | 2018-09-27 | 2019-01-25 | 郑州云海信息技术有限公司 | A kind of method of adjustment, device and the computer equipment of storage pool carry host |
| US20190332684A1 (en) * | 2018-04-25 | 2019-10-31 | International Business Machines Corporation | Optimized Network File System Client for Read-Only Exports/Mounts |
-
2019
- 2019-11-15 CN CN201911122501.6A patent/CN110868323B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9898482B1 (en) * | 2013-12-27 | 2018-02-20 | EMC IP Holding Company LLC | Managing stream connections in storage systems |
| CN105511805A (en) * | 2015-11-26 | 2016-04-20 | 深圳市中博科创信息技术有限公司 | Data processing method and device for cluster file system |
| CN107483637A (en) * | 2017-09-22 | 2017-12-15 | 郑州云海信息技术有限公司 | A kind of client link management method and device based on NFS |
| US20190332684A1 (en) * | 2018-04-25 | 2019-10-31 | International Business Machines Corporation | Optimized Network File System Client for Read-Only Exports/Mounts |
| CN109271112A (en) * | 2018-09-27 | 2019-01-25 | 郑州云海信息技术有限公司 | A kind of method of adjustment, device and the computer equipment of storage pool carry host |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112291310A (en) * | 2020-10-14 | 2021-01-29 | 杭州迪普科技股份有限公司 | Method and device for counting connection number |
| CN112291310B (en) * | 2020-10-14 | 2022-04-26 | 杭州迪普科技股份有限公司 | Method and device for counting connection number |
| CN113835632A (en) * | 2021-09-17 | 2021-12-24 | 济南浪潮数据技术有限公司 | Method, system, equipment and storage medium for setting read-write bandwidth in batches |
| CN117041317A (en) * | 2023-10-09 | 2023-11-10 | 安徽隼波科技有限公司 | Method for managing connection between TCP multiple clients based on FreeRTOS |
| CN117041317B (en) * | 2023-10-09 | 2023-12-08 | 安徽隼波科技有限公司 | Method for managing connection between TCP multiple clients based on FreeRTOS |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110868323B (en) | 2022-07-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110300050B (en) | Message pushing method and device, computer equipment and storage medium | |
| CN108052675B (en) | Log management method, system and computer readable storage medium | |
| CN110868323B (en) | Bandwidth control method, device, equipment and medium | |
| USRE45806E1 (en) | System and method for the optimization of database access in data base networks | |
| CN111522636B (en) | Application container adjusting method, application container adjusting system, computer readable medium and terminal device | |
| CN106972985B (en) | Method for accelerating data processing and forwarding of DPI (deep packet inspection) equipment and DPI equipment | |
| CN106713378B (en) | Method and system for providing service by multiple application servers | |
| US20150263985A1 (en) | Systems and methods for intelligent workload routing | |
| CN107800574B (en) | Storage QOS adjusting method, system, equipment and computer readable memory | |
| US11438271B2 (en) | Method, electronic device and computer program product of load balancing | |
| CN113259415B (en) | Network message processing method and device and network server | |
| CN110933171A (en) | Server asynchronous communication method, device, equipment and computer storage medium | |
| CN108259605B (en) | Data calling system and method based on multiple data centers | |
| KR20160025926A (en) | Apparatus and method for balancing load to virtual application server | |
| CN107483637B (en) | NFS-based client link management method and device | |
| CN113596105B (en) | Content acquisition method, edge node and computer readable storage medium | |
| CN113794755A (en) | Shared service pushing method and system based on micro-service architecture | |
| CN115883639A (en) | Web real-time message pushing method and device, equipment and storage medium | |
| CN111858060A (en) | Resource dynamic adjustment method and device for high-performance computing cluster | |
| CN110753043A (en) | Communication method, device, server and medium | |
| CN114979276B (en) | Dynamic scheduling method, device, equipment and storage medium for resources | |
| CN111431951A (en) | Data processing method, node equipment, system and storage medium | |
| CN112929410B (en) | System and method for supporting cloud desktop multi-terminal display | |
| CN111477229B (en) | Voice recognition request processing method and device | |
| CN116866947A (en) | Slice acquisition method, slice intermediate component, communication device, and readable storage medium |
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 |