CN112448968B - Method for processing network request, related device and storage system - Google Patents

Method for processing network request, related device and storage system Download PDF

Info

Publication number
CN112448968B
CN112448968B CN201910805171.4A CN201910805171A CN112448968B CN 112448968 B CN112448968 B CN 112448968B CN 201910805171 A CN201910805171 A CN 201910805171A CN 112448968 B CN112448968 B CN 112448968B
Authority
CN
China
Prior art keywords
link establishment
requests
server
client
establishment requests
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
Application number
CN201910805171.4A
Other languages
Chinese (zh)
Other versions
CN112448968A (en
Inventor
叶帆
张志乐
丁萌
张雷
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Cloud Computing Technologies Co Ltd
Original Assignee
Huawei Cloud Computing Technologies Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Huawei Cloud Computing Technologies Co Ltd filed Critical Huawei Cloud Computing Technologies Co Ltd
Priority to CN201910805171.4A priority Critical patent/CN112448968B/en
Publication of CN112448968A publication Critical patent/CN112448968A/en
Application granted granted Critical
Publication of CN112448968B publication Critical patent/CN112448968B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/14Session management
    • H04L67/141Setup of application sessions

Abstract

The embodiment of the application discloses a method for processing a network request, a related device and a storage system. The method in the embodiment of the application comprises the following steps: the client receives a first number of link establishment requests, then allocates port numbers for a second number of link establishment requests in the first number of link establishment requests, and completes TCP handshake with the server for the second number of link establishment requests.

Description

Method for processing network request, related device and storage system
Technical Field
The present application relates to the field of data storage technologies, and in particular, to a method, a related apparatus, and a storage system for processing a network request.
Background
The traditional storage system adopts a centralized storage array to store all data, and along with the explosive growth of the data, the traditional storage system cannot meet the requirements of people on scale and safety, so that a distributed storage system is born.
The distributed storage system comprises a client and a plurality of servers, and the servers are used for respectively storing data. The server is also called a storage node. Since each server shares the storage load, the reliability, the availability and the access efficiency of the system are improved. Links are established between the client and each server, the client can access the servers through the links, and data input and output in the servers can be realized through access.
However, in practical applications, there is a case of process upgrade or restart at the client, in which case, the client may reestablish the link with each server, and a specific method is to establish all the links with each server at one time, so that a larger bandwidth is required.
Disclosure of Invention
The embodiment of the application provides a method for processing a network request, a related device and a storage system, which can reduce the requirement on bandwidth while processing a request for establishing a link.
A first aspect of an embodiment of the present application provides a method for processing a network request, where the method includes:
when the client process is upgraded or restarted, the client receives a first number of link establishment requests;
the client side does not process the first number of link establishing requests at one time, but allocates port numbers for a second number of link establishing requests in the first number of link establishing requests, and completes Transmission Control Protocol (TCP) handshake between the second number of link establishing requests and the server side, wherein the second number is smaller than the first number; after that, the client may send an access request to the server that completes the TCP handshake to access the server.
According to the embodiment of the application, part of link establishment requests are processed first, and not all link establishment requests are processed at one time, so that the requirement on bandwidth can be reduced.
Based on the first aspect, an embodiment of the present application further provides a first implementation manner of the first aspect:
therefore, when the client needs to send the access request to the server, if the second link establishment request corresponding to the access request is not processed, the second number of link establishment requests can be the link establishment requests corresponding to the access request sent by the client to the server; in this way, the client can preferentially process the second number of link establishment requests, allocate port numbers to the second number of link establishment requests, and complete TCP handshake with the server for the second number of link establishment requests.
The embodiment of the application can preferentially process the second quantity of link establishment requests corresponding to the access requests without sequentially processing the first quantity of link establishment requests according to a fixed sequence, so that the link establishment requests are selectively processed according to the access requests, and the flexibility is higher; and at any time after the second number of link establishment requests and the server end complete the TCP handshake, the access requests can be sent to the server end, and the access requests do not need to be sent to the server end after the first number of link establishment requests are all processed, so that the waiting time for sending the access requests is shortened.
Based on the first implementation manner of the first aspect, the present application provides a second implementation manner of the first aspect:
and when the TCP handshake with the server is completed for the second number of link establishment requests, the client sends an access request to the server to realize the access to the server.
In this way, compared with sending the access requests after the first number of link establishment requests are processed at one time, the waiting time for sending the access requests in the embodiment of the application is shortened from the time for processing the first number of link establishment requests to the time for processing the second number of link establishment requests.
Based on the first aspect, or the first implementation manner of the first aspect, or the second implementation manner of the first aspect, the present application provides an example of a third implementation manner of the first aspect:
the client allocating port numbers for a second number of the first number of link establishment requests comprises:
and the client allocates port numbers for a second number of link establishment requests in the first number of link establishment requests according to the port historical allocation record.
In the embodiment of the application, the client does not need to traverse all the ports to allocate the proper port numbers for the second number of link establishment requests, but the client allocates the port numbers for the second number of link establishment requests according to the port historical allocation records, so that the allocation time of the port numbers is shortened, and the allocation efficiency of the port numbers is improved.
A second aspect of the embodiments of the present application provides an apparatus for processing a network request, where the apparatus includes:
a receiving unit, configured to receive a first number of link establishment requests;
the processing unit is used for allocating port numbers for a second number of link establishment requests in the first number of link establishment requests and completing Transmission Control Protocol (TCP) handshake between the second number of link establishment requests and the server; wherein the second number is smaller than the first number.
Based on the second aspect, the embodiments of the present application further provide a first implementation manner of the second aspect:
the apparatus further includes a sending unit configured to send an access request to the server when a TCP handshake with the server is completed for a second number of link establishment requests.
Based on the second aspect or the first implementation manner of the second aspect, the present application provides a second implementation manner of the second aspect:
the processing unit is used for allocating port numbers for the second number of link establishment requests in the first number of link establishment requests according to port historical allocation records, and completing Transmission Control Protocol (TCP) handshake between the second number of link establishment requests and the server; wherein the second number is less than the first number.
A third aspect of the embodiments of the present application provides a server, including: a memory and a central processor, the memory in communication with the processor;
wherein, the memorizer is used for storing the procedure;
the processor is configured to execute the program in the memory to perform the method according to any one of the first aspect of the embodiments of the present application.
A fourth aspect of embodiments of the present application provides a computer-readable storage medium, comprising instructions, which, when executed on a computer, cause the computer to perform the method according to any one of the first aspects of embodiments of the present application.
A fifth aspect of embodiments of the present application provides a computer program product, which includes computer software instructions that can be loaded by a processor to perform the method according to any one of the first aspect of embodiments of the present application.
A sixth aspect of the present embodiment provides a storage system, including a client and a server;
the client is configured to perform the method according to any one of the first aspect of the embodiments of the present application.
According to the technical scheme, the embodiment of the application has the following advantages:
firstly, a client receives a first number of link establishing requests, then the client allocates port numbers for a second number of link establishing requests in the first number of link establishing requests, and completes Transmission Control Protocol (TCP) handshake with a server for the second number of link establishing requests, wherein the second number is smaller than the first number; therefore, the embodiment of the application processes part of the link establishment requests, rather than processing all the link establishment requests at one time, so that the requirement on bandwidth can be reduced.
Drawings
FIG. 1 is a block diagram of a storage system according to an embodiment of the present application;
FIG. 2 is a diagram illustrating an embodiment of a method for processing a network request according to an embodiment of the present application;
FIG. 3 is a schematic diagram of an embodiment of a client processing a first number of requests to establish a link according to an embodiment of the present application;
FIG. 4 is a schematic diagram of an embodiment of the present application in which a client processes a second number of requests to establish a link;
fig. 5 is a schematic diagram of an embodiment of an apparatus for processing a network request according to an embodiment of the present application;
fig. 6 is a schematic structural diagram of a server according to an embodiment of the present invention;
fig. 7 is a schematic diagram of an embodiment of a storage system according to an embodiment of the present application.
Detailed Description
The embodiment of the application provides a method for processing a network request, a related device and a storage system, which can reduce the requirement on bandwidth while processing a request for establishing a link.
The embodiment of the application can be applied to a storage system as shown in fig. 1, and the storage system comprises a client and a plurality of servers. The client is a carrier with a data processing function and can send an access request to each server, wherein the client can be a server. The server is a carrier with a data storage space and is used for storing file data and ensuring the availability and integrity of the data, wherein the server can be a server, a disk or a logical storage space.
Under normal conditions, the client is in communication connection with each server through a link. The communication connection may be a transmission control protocol (tcp) connection. The client can access each server through the link.
However, there are cases where the links between the client and the respective servers are established again, for example, when a process in the client is upgraded or restarted, the client needs to establish the links with the respective servers again. Specifically, the client receives a link establishment message, where the link establishment message includes a request for establishing a link between the client and each server. Generally, one server corresponds to one link establishment request. The link establishing message also includes a processing sequence of the link establishing requests, and the client side can process each link establishing request in sequence according to the processing sequence so as to reestablish the link with each server side.
Since processing all link establishment requests at one time requires a large bandwidth, the embodiments of the present application process link establishment requests in batches to reduce the bandwidth requirement. For ease of understanding, the process of handling the request to establish a link will be described in detail below.
Referring to fig. 2, a schematic diagram of an embodiment of a method for processing a network request according to an embodiment of the present application is shown. An embodiment of a method for processing a network request is provided in the present application, including:
101, a client receives a first number of requests to establish a link.
In the embodiment of the application, the link establishment requests may correspond to the servers one to one, and accordingly, the first number is the total number of the servers; for example, if the storage system shown in fig. 1 includes 10 servers, the first number is 10, and each server corresponds to one link establishment request.
Each link establishment request comprises two parts of requesting to allocate port numbers and completing TCP handshake. In order to enable the client to process each link establishment request in order, in general, the client receives the link establishment request and also receives a processing sequence of the link establishment requests, so that the client processes each link establishment request in sequence according to the processing sequence.
102, the client allocates port numbers for a second number of link establishment requests in the first number of link establishment requests, and completes TCP handshake with the server for the second number of link establishment requests; wherein the second number is smaller than the first number.
In the embodiment of the present application, after receiving the first number of link establishment requests, the client does not process all link establishment requests at one time, but processes all link establishment requests in batches, specifically, referring to fig. 3, an embodiment of the client processing the first number of link establishment requests in the embodiment of the present application is shown, and as shown in fig. 3, the client processes a second number of link establishment requests in the first number of link establishment requests first.
It should be noted that there are various methods for processing the second number of link establishment requests, and this is not limited in the embodiment of the present application. For example, priority queues may be preset, please refer to fig. 4, an embodiment of the present application for processing a second number of link establishment requests is shown in fig. 4, where the priority queues include a normal priority queue and a high priority queue, and the client preferentially processes the link establishment requests in the high priority queue. After receiving the first number of link establishment requests, the client may add the first number of link establishment requests to the normal priority queue, where the normal priority queue in fig. 4 shows the first number of link establishment requests, then determine the second number of link establishment requests from the first number of link establishment requests, and transfer the second number of link establishment requests to the high priority queue, so that the client preferentially processes the second number of link establishment requests.
The method for determining the second number of link establishment requests includes a plurality of methods, and can be set according to actual needs. Specifically, the value of the second number may be set first, and the value of the second number may be set directly or indirectly. For example, if the second number is set to 5 directly, the client determines 5 link establishment requests; the value of the second number may also be indirectly set by setting the processing time of the link establishment request, after the processing time is set, the second number is the number of link establishment requests actually processed by the client within the processing time, if the processing time of the link establishment request is 1s, the second number is the number of link establishment requests actually processed by the client within 1s, and if the number of link establishment requests actually processed by the client within 1s is 6, the second number is 6.
After the setting of the second number of values is completed, the client may randomly select the second number of link establishment requests from the first number of link establishment requests, or sequentially select the second number of link establishment requests from the first number of link establishment requests according to the processing sequence received in operation 101.
In this embodiment of the present application, the specific process of processing the second number of link establishment requests includes allocating port numbers to the second number of link establishment requests, and completing a TCP handshake with the server.
It can be understood that, before establishing a link between a client and a server, a set of parameters needs to be determined, where the set of parameters includes a port number of the client, a protocol IP address of the client, a port number of the server, and an IP address of the server, and for a set of determined clients and servers, the protocol IP address of the client, the port number of the server, and the IP address of the server are all fixed, so in this embodiment of the present application, only the port number of the client needs to be determined. The method for allocating port numbers to the second number of link establishment requests includes multiple methods, which are not limited in the embodiment of the present application. For example, the kernel of the client may allocate a port number to the second number of requests for establishing links, and specifically, the kernel of the client may traverse the ports of each client, determine at least one port with a smaller number of link connections from the ports of all the clients, and allocate the port number of the at least one port to the second number of requests for establishing links.
The client and the server complete TCP handshake for the second number of link establishment requests, which generally includes three handshakes, and the specific handshake process is not described in detail herein.
It should be noted that, since the second number is smaller than the first number, to complete the handshake between the request for establishing a link and the server TCP, at least two operations 102 are performed; it should be noted that, in any two operations 102, the second number may be the same or different, that is, after the current operation 102 is executed, the second number may be reset when the operation 102 is executed next time, and the specific process may refer to the setting process of the second number, which is not described in detail herein.
According to the embodiment of the application, the second quantity of link establishment requests are processed firstly, and the first quantity of link establishment requests are not processed at one time, so that the requirement on bandwidth can be reduced.
As can be seen from the above description, the determination of the second number of link establishment requests may be determined according to the value of the second number and the processing sequence, and in addition, there are other methods, which will be specifically described below by way of example.
In another embodiment of the method for processing a network request provided by the embodiment of the present application, in this embodiment, the second number of link establishment requests are link establishment requests corresponding to access requests sent by a client to a server.
It should be noted that the client may receive an access request to the server in the process of processing the first number of link establishment requests. After receiving the access request, the client needs to send the access request to the server, so as to realize access to the server. However, in order to avoid sending the access request after the first number of link establishment requests are processed, which results in an excessively long waiting time for the access request, in the embodiment of the present application, the access request needs to be sent to the server as soon as possible, and before sending the access request to the server, the client needs to establish a link with the server first. Therefore, the link establishment requests corresponding to the access requests sent by the client to the server are determined as the second number of link establishment requests. Therefore, the client can preferentially process the link establishment requests corresponding to the access requests sent by the client to the server, and the client can send the access requests to the server after the second number of link establishment requests are processed.
Based on the above description, it can be seen that in the embodiment of the present application, the second number of requests for establishing links is determined according to the received access request to the server.
When the second number of link establishment requests are link establishment requests corresponding to access requests sent by the client to the server, there are many cases in the time for processing the second number of link establishment requests, which will be described in detail below. If the client receives the access request after receiving the first number of link establishment requests and before starting to process the first link establishment request, the client can determine the link establishment requests corresponding to the access requests sent by the client to the server as the second number of link establishment requests and start to process the second number of link establishment requests under the condition that one link establishment request is not processed; if the client receives the access requests, the client may determine the link establishment requests corresponding to the access requests sent by the client to the server as the link establishment requests of the second quantity after processing the first link establishment requests, and then process the link establishment requests of the second quantity.
The number of the access requests can be one or multiple, in general, one access request corresponds to one server, and different access requests can correspond to the same server; since one server side corresponds to one link establishing request, one access request corresponds to one link establishing request, and different access requests can correspond to the same link establishing request.
It is understood that all the link establishment requests corresponding to the access request may include the link establishment request that has been processed, or may include the link establishment request that has not been processed.
When the link establishing requests corresponding to all the access requests include the processed link establishing requests, the client does not need to allocate a port number for the processed link establishing requests and perform TCP handshake with the server because the link between the server corresponding to the processed link establishing requests and the client is already established.
When the link establishment requests corresponding to all the access requests include unprocessed link establishment requests, the client needs to allocate a port number to the unprocessed link establishment requests, and perform TCP handshake with the server for the unprocessed link establishment requests.
It should be noted that, when the number of unprocessed link establishment requests is at least two, the port numbers may be sequentially allocated to the respective link establishment requests according to the processing sequence received in operation 101 and the TCP handshake may be performed with the server, and the port numbers may be sequentially allocated to the respective link establishment requests according to the time sequence of receiving the access request by the client and the TCP handshake may be performed with the server.
For example, it is assumed that the access request includes a first access request, a second access request, and a third access request, the unprocessed link establishment request includes a first link establishment request, a second link establishment request, and a third link establishment request, and the first access request corresponds to the first link establishment request, the second access request corresponds to the second link establishment request, and the third access request corresponds to the third link establishment request; if the client receives the second access request, then receives the first access request and finally receives the third access request, the client firstly allocates a port number for the second link establishment request, completes TCP handshake with the corresponding server for the second link establishment request, then allocates a port number for the first link establishment request, completes TCP handshake with the corresponding server for the first link establishment request, and finally allocates a port number for the third link establishment request, and completes TCP handshake with the corresponding server for the third link establishment request.
In the embodiment of the application, when the second number of link establishment requests and the server end complete the TCP handshake at any time, the client end can send the access request to the server end without waiting for the first number of link establishment requests to be processed completely before sending the access request to the server end, so that the waiting time for sending the access request is shortened.
In another embodiment of a method for processing a network request provided in an embodiment of the present application, in this embodiment, the method further includes: and when the TCP handshake with the server is completed for the second number of link establishment requests, the client sends an access request to the server.
It can be understood that, in order to send the access request to the server as soon as possible, the client may send the access request to the server when the TCP handshake with the server is completed for the second number of link establishment requests, so that the waiting time for sending the access request in the embodiment of the present application is shortened from the time of processing the first number of link establishment requests to the time of processing the second number of link establishment requests, compared with sending the access request after the first number of link establishment requests are processed at one time.
When the number of the access requests is at least two, the sequence of sending each access request by the client can be set according to actual needs; for example, each access request may be sent to the server randomly, or may be sent to the server sequentially according to the time sequence in which the client receives the access requests.
For example, taking the first access request, the second access request, and the third access request as an example, after TCP handshake with the server is completed for the second number of link establishment requests, the client needs to send the first access request, the second access request, and the third access request to the respective corresponding servers.
In the embodiment of the application, the client side can be understood as uniformly sending the access request after the TCP handshake with the server side is completed for the second number of link establishment requests; in other embodiments, in order to send each access request in time, in the process of processing the second number of link establishment requests, after completing TCP handshake with the server for the link establishment request corresponding to one access request, the client may first send the access request to the corresponding server, and then complete TCP handshake with the server for the link establishment request corresponding to the next access request.
According to the foregoing embodiment, the kernel of the client may allocate port numbers to the second number of link establishment requests, however, since the kernel needs to traverse all the ports of the client in the process of allocating port numbers to each link establishment request, when the second number is larger, the time for allocating port numbers to the second number of link establishment requests is too long, the allocation efficiency is lower, and for the first number of link establishment requests, the time for allocating port numbers is longer; especially, in a large-scale scenario, the number of the servers in the storage system generally includes tens of thousands, that is, the first number of the corresponding link establishment requests also includes tens of thousands, and if the ports of all the clients are traversed when the port number is allocated to each link establishment request, the time for allocating the port number to the first number of link establishment requests is extra.
Therefore, in another embodiment of a method for processing a network request provided by an embodiment of the present application, in this embodiment, allocating, by a client, a port number to a second number of requests for establishing links in a first number of requests for establishing links includes:
and the client allocates port numbers for a second number of link establishment requests in the first number of link establishment requests according to the port historical allocation record.
In the embodiment of the application, the port number is directly allocated by the application module of the client according to the port history allocation record. Because the port number allocated to each link establishing request is recorded in the port historical allocation record, the number of the links corresponding to each port can be determined according to the port historical allocation record, and then the port number of the port with less links can be allocated to the link establishing requests with the second number quickly, so that the allocation time of the port number is shortened, and the allocation efficiency of the port number is improved.
Referring to fig. 5, a schematic diagram of an embodiment of an apparatus for processing a network request according to the present application is provided. As shown in fig. 5, an embodiment of the present application provides an apparatus for processing a network request, including:
a receiving unit 201, configured to receive a first number of link establishment requests;
the processing unit 202 is configured to allocate port numbers to a second number of link establishment requests in the first number of link establishment requests, and complete TCP handshake with the server for the second number of link establishment requests; wherein the second number is smaller than the first number.
In another embodiment of the method for processing a network request provided by the embodiment of the present application, as shown in fig. 5, in this embodiment, the apparatus for processing a network request further includes a sending unit 203, configured to send an access request to a server when a second number of link establishment requests complete a TCP handshake with the server.
In another embodiment of the method for processing a network request provided in the embodiment of the present application, in this embodiment, the processing unit 202 is configured to allocate port numbers to a second number of link establishment requests in a first number of link establishment requests according to a port historical allocation record, and complete TCP handshake with a server for the second number of link establishment requests; wherein the second number is smaller than the first number.
Referring to fig. 6, fig. 6 is a schematic structural diagram of a server according to an embodiment of the present invention, where the server 300 may generate relatively large differences due to different configurations or performances, and may include one or more Central Processing Units (CPUs) 322 (e.g., one or more processors) and a memory 332, and one or more storage media 330 (e.g., one or more mass storage devices) storing an application 332 or data 333. Memory 332 and storage media 330 may be, among other things, transient storage or persistent storage. The program stored on the storage medium 330 may include one or more modules (not shown), each of which may include a series of instruction operations for the server. Still further, the central processor 322 may be configured to communicate with the storage medium 330 to execute a series of instruction operations in the storage medium 330 on the server 300.
In this embodiment, CPU322 may perform the steps described in any of the previous method embodiments.
Embodiments of the present application further provide a computer storage medium for storing computer software instructions for the server, which includes a program designed for executing the server.
Embodiments of the present application further provide a computer program product, which includes computer software instructions that can be loaded by a processor to perform the steps of any of the foregoing method embodiments.
Referring to fig. 7, a schematic diagram of an embodiment of a memory system according to the present application is shown. As shown in fig. 7, an embodiment of the present application further provides a storage system, which includes a client 400 and a server 500;
the client 400 is used for the steps described in any of the method embodiments described above.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

Claims (7)

1. A method of processing a network request, the method comprising:
a client receives a first number of link establishment requests;
the client allocates port numbers for a second number of link establishing requests in the first number of link establishing requests, and completes TCP handshake with the server for the second number of link establishing requests; wherein the second number is less than the first number;
the second quantity of link establishment requests are link establishment requests corresponding to access requests sent by the client to the server;
the method further comprises the following steps:
completing TCP handshake with the server for the second number of link establishing requests, and sending the access request to the server by the client;
after sending the access request to the server, the client allocates port numbers to other link establishment requests in the first number of link establishment requests except the second number of link establishment requests, and completes TCP handshake with the server for the other link establishment requests.
2. The method of claim 1, wherein the client assigning port numbers to a second number of the first number of establish link requests comprises:
and the client allocates port numbers for the second quantity of link establishment requests in the first quantity of link establishment requests according to the historical port allocation records.
3. An apparatus for processing network requests, the apparatus comprising:
a receiving unit, configured to receive a first number of link establishment requests;
the processing unit is used for allocating port numbers to a second number of link establishment requests in the first number of link establishment requests and completing Transmission Control Protocol (TCP) handshake between the second number of link establishment requests and the server; wherein the second number is less than the first number;
the second quantity of link establishment requests are link establishment requests corresponding to access requests sent by the client to the server;
the device further comprises a sending unit, configured to send the access request to the server when TCP handshake with the server is completed for the second number of link establishment requests;
and the processing unit is further configured to, after sending the access request to the server, allocate port numbers to other link establishment requests, except for the second number of link establishment requests, in the first number of link establishment requests by the client, and complete TCP handshake with the server for the other link establishment requests.
4. The apparatus according to claim 3, wherein the processing unit is configured to allocate port numbers for a second number of the first number of requests to establish links according to a port history allocation record.
5. A server, comprising: a memory and a central processing unit; the memory is in communication with the processor;
wherein the memory is used for storing programs;
the processor is configured to execute a program in the memory to perform the method of any of claims 1-2.
6. A computer-readable storage medium comprising instructions that, when executed on a computer, cause the computer to perform the method of any of claims 1-2.
7. A storage system is characterized by comprising a client and a server;
the client is configured to perform the method of any of claims 1 to 2.
CN201910805171.4A 2019-08-28 2019-08-28 Method for processing network request, related device and storage system Active CN112448968B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910805171.4A CN112448968B (en) 2019-08-28 2019-08-28 Method for processing network request, related device and storage system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910805171.4A CN112448968B (en) 2019-08-28 2019-08-28 Method for processing network request, related device and storage system

Publications (2)

Publication Number Publication Date
CN112448968A CN112448968A (en) 2021-03-05
CN112448968B true CN112448968B (en) 2022-08-09

Family

ID=74741154

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910805171.4A Active CN112448968B (en) 2019-08-28 2019-08-28 Method for processing network request, related device and storage system

Country Status (1)

Country Link
CN (1) CN112448968B (en)

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102594798A (en) * 2011-12-31 2012-07-18 苏州阔地网络科技有限公司 Agent method and system for connecting databases
CN103312807A (en) * 2013-06-20 2013-09-18 华为技术有限公司 Data transmission method, data transmission device and data transmission system
CN103428287A (en) * 2013-08-09 2013-12-04 华为技术有限公司 Method and device for establishing connection
CN104333573A (en) * 2012-06-29 2015-02-04 北京奇虎科技有限公司 Processing method and processing system for highly-concurrent requests
CN105357253A (en) * 2015-09-28 2016-02-24 努比亚技术有限公司 Network data request processing device and method
CN105704175A (en) * 2014-11-25 2016-06-22 阿里巴巴集团控股有限公司 Connection establishing method and device
CN106603598A (en) * 2015-10-15 2017-04-26 阿里巴巴集团控股有限公司 Method for processing service request and apparatus thereof
CN109151082A (en) * 2018-11-02 2019-01-04 郑州云海信息技术有限公司 A kind of multi-connection method for building up, device and system
CN110012075A (en) * 2019-03-12 2019-07-12 平安科技(深圳)有限公司 Data transmission method and relevant device

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140006464A1 (en) * 2012-06-29 2014-01-02 William M Pitts Using projected timestamps to control the sequencing of file modifications in distributed filesystems

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102594798A (en) * 2011-12-31 2012-07-18 苏州阔地网络科技有限公司 Agent method and system for connecting databases
CN104333573A (en) * 2012-06-29 2015-02-04 北京奇虎科技有限公司 Processing method and processing system for highly-concurrent requests
CN103312807A (en) * 2013-06-20 2013-09-18 华为技术有限公司 Data transmission method, data transmission device and data transmission system
CN103428287A (en) * 2013-08-09 2013-12-04 华为技术有限公司 Method and device for establishing connection
CN105704175A (en) * 2014-11-25 2016-06-22 阿里巴巴集团控股有限公司 Connection establishing method and device
CN105357253A (en) * 2015-09-28 2016-02-24 努比亚技术有限公司 Network data request processing device and method
CN106603598A (en) * 2015-10-15 2017-04-26 阿里巴巴集团控股有限公司 Method for processing service request and apparatus thereof
CN109151082A (en) * 2018-11-02 2019-01-04 郑州云海信息技术有限公司 A kind of multi-connection method for building up, device and system
CN110012075A (en) * 2019-03-12 2019-07-12 平安科技(深圳)有限公司 Data transmission method and relevant device

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
如何一步一步做到单机千万并发连接(一);叶东富;《http://zhuanlan.zhihu.com/p/22483256》;20160917;全文 *

Also Published As

Publication number Publication date
CN112448968A (en) 2021-03-05

Similar Documents

Publication Publication Date Title
CN109597818A (en) Data-updating method, device, storage medium and equipment
CN109375933B (en) Method and equipment for upgrading client
CN109408243B (en) RDMA-based data processing method, device and medium
US20220261270A1 (en) Reusing software application containers
US9736235B2 (en) Computer system, computer, and load balancing method
CN108055311B (en) HTTP asynchronous request method, device, server, terminal and storage medium
WO2021057666A1 (en) Transmission control method, network management server, base station and storage medium
EP3885907A1 (en) Read/write request processing method and apparatus, electronic device, and storage medium
US20160259812A1 (en) Method and system for accessing a distributed file system
US8458702B1 (en) Method for implementing user space up-calls on java virtual machine before/after garbage collection
CN108304272B (en) Data IO request processing method and device
CN112286688A (en) Memory management and use method, device, equipment and medium
CN113515320A (en) Hardware acceleration processing method and device and server
CN110399329B (en) RDMA data processing method and related device
CN112448968B (en) Method for processing network request, related device and storage system
US20170126855A1 (en) Packet Processing Method and Related Device That are Applied to Network Device
US7693166B2 (en) Method and apparatus for transmitting data to network and method and apparatus for receiving data from network
US20220263869A1 (en) Data validation for zero copy protocols
TW201644249A (en) Devices and methods for performing TCP handshakes
CN112764897B (en) Task request processing method, device and system and computer readable storage medium
CN111669355B (en) Method for batch processing of nginx network isolation space and nginx server
CN111669423B (en) Batch processing method and system of network isolation space based on user mode protocol stack
CN110445848B (en) Method and apparatus for transaction processing
CN111431951B (en) Data processing method, node equipment, system and storage medium
CN111309467A (en) Task distribution method and device, electronic equipment and 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
TA01 Transfer of patent application right
TA01 Transfer of patent application right

Effective date of registration: 20220216

Address after: 550025 Huawei cloud data center, jiaoxinggong Road, Qianzhong Avenue, Gui'an New District, Guiyang City, Guizhou Province

Applicant after: Huawei Cloud Computing Technology Co.,Ltd.

Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen

Applicant before: HUAWEI TECHNOLOGIES Co.,Ltd.

GR01 Patent grant
GR01 Patent grant