A routing information synchronization method and related device

Abstract

The application discloses a route information synchronization method and related equipment, and the method comprises the following steps: when a route synchronization request sent by a client is received, determining an estimated response time of the route synchronization request based on current to-be-processed request information; the estimated response time represents a time period from a time point when the route synchronization request is received to a time point when a route information return packet corresponding to the route synchronization request is sent; if the estimated response time is less than or equal to a preset time, obtaining to-be-synchronized route information corresponding to the route synchronization request; when a current network bandwidth value is less than or equal to a preset network bandwidth value, sending the to-be-synchronized route information to the client; the preset network bandwidth value represents a maximum network bandwidth value when the local equipment is normally working. Thus, the problem that the existing route synchronization mode is not timely can be solved.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a method for synchronizing routing information and related equipment. Background Technology

[0002] The cloud storage system architecture includes cluster management nodes, storage nodes, and clients. The cluster management nodes are responsible for cluster control and maintaining routing information, the storage nodes are responsible for data storage, and the clients access the storage nodes to obtain the data they want.

[0003] Currently, when a storage node in a cloud storage system architecture fails or needs to be expanded, requiring the deletion or addition of nodes, the system's node topology changes. The cluster management node detects this change and performs routing updates. After updating the routing information, the management node needs to synchronize the latest routing information to all storage nodes and clients.

[0004] However, as the cluster size increases and service availability requirements rise, the current routing synchronization method for cluster management nodes suffers from untimely synchronization issues. Therefore, there is an urgent need to provide an efficient routing synchronization method to meet the requirements of routing synchronization performance. Summary of the Invention

[0005] To address the issue of untimely synchronization in existing cluster management node routing synchronization methods, this application provides a routing information synchronization method and related equipment:

[0006] According to a first aspect of this application, a routing information synchronization method is provided, comprising:

[0007] Upon receiving a route synchronization request from a client, the estimated response time for the route synchronization request is determined based on the current pending request information. The estimated response time represents the time elapsed from the moment the route synchronization request is received until the moment the corresponding route information packet for the route synchronization request is sent back.

[0008] If the estimated response time is less than or equal to the preset time, obtain the route information to be synchronized corresponding to the route synchronization request;

[0009] When the current network bandwidth value is less than or equal to the preset network bandwidth value, the routing information to be synchronized will be sent to the client; the preset network bandwidth value represents the maximum network bandwidth value when the local system is working normally.

[0010] According to a second aspect of this application, a routing information synchronization device is provided, the device comprising:

[0011] The first determining module is used to determine the estimated response time of the route synchronization request based on the current pending request information when it receives the route synchronization request sent by the client. The estimated response time represents the time elapsed from the moment the route synchronization request is received until the moment the corresponding route information packet for the route synchronization request is sent back.

[0012] The acquisition module is used to acquire the route information to be synchronized corresponding to the route synchronization request if the estimated response time is less than or equal to the preset time.

[0013] The sending module is used to send the routing information to be synchronized to the client when the current network bandwidth value is less than or equal to the preset network bandwidth value; the preset network bandwidth value represents the maximum network bandwidth value when the local system is working normally.

[0014] According to a third aspect of this application, a routing information synchronization system is provided, the system including a routing information synchronization device and a routing information management device;

[0015] The routing information management device is used to maintain routing information; after the routing information is updated, it sends the updated routing version identifier and routing information to the routing information synchronization device.

[0016] The routing information management device is also used to determine at least one routing information synchronization device identifier corresponding to the client when it receives heartbeat information sent by the client, and return at least one routing information synchronization device identifier to the client so that the client can send a routing synchronization request to the routing information synchronization device corresponding to any one of the at least one routing information synchronization device identifiers.

[0017] A routing information synchronization device includes: a first determining module, used to determine the estimated response time of a routing synchronization request based on current pending request information when a routing synchronization request is received from a client; the estimated response time represents the time elapsed from the moment the routing synchronization request is received until the moment the routing information corresponding to the routing synchronization request is sent back; an obtaining module, used to obtain the routing information to be synchronized corresponding to the routing synchronization request if the estimated response time is less than or equal to a preset time; and a sending module, used to send the routing information to be synchronized to the client when the current network bandwidth value is less than or equal to a preset network bandwidth value; the preset network bandwidth value represents the maximum network bandwidth value when the local system is working normally.

[0018] According to a fourth aspect of this application, an electronic device is provided, comprising a processor and a memory, wherein the memory stores at least one instruction or at least one program, and the at least one instruction or at least one program is loaded and executed by the processor to implement the routing information synchronization method of the first aspect of this application.

[0019] According to a fifth aspect of this application, a computer storage medium is provided, wherein at least one instruction or at least one program is stored in the storage medium, and the at least one instruction or at least one program is loaded and executed by a processor to implement the routing information synchronization method as described in the first aspect of this application.

[0020] According to a sixth aspect of this application, a computer program product is provided, comprising at least one instruction or at least one program segment, wherein the at least one instruction or at least one program segment is loaded and executed by a processor to implement the routing information synchronization method of the first aspect of this application.

[0021] The routing information synchronization method and related equipment provided in this application have the following technical effects:

[0022] This application, on the one hand, determines the estimated response time of route synchronization requests based on the current pending request information, only processes requests that can return within the expected time, and rejects requests with long response times. This avoids the waiting time of the client at the storage node and prevents the request overload of a single storage node, thus shortening the synchronization time of route information and improving synchronization efficiency. On the other hand, to avoid avalanche-like anomalies caused by excessive buffer occupancy due to the sending of a large number of route information return packets, which could render the storage node unusable, the storage node determines whether to perform flow control based on the current network bandwidth value before sending route information return packets. If the current network bandwidth value exceeds the preset network bandwidth value, the sending of route information to be synchronized is temporarily suspended. This improves the stability of the storage node and thus increases the success rate of route information synchronization. Attached Figure Description

[0023] To more clearly illustrate the technical solutions and advantages in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 This is a schematic diagram of an application environment provided in an embodiment of this application;

[0025] Figure 2 This is a schematic diagram of a cloud storage environment provided in an embodiment of this application;

[0026] Figure 3 This is a flowchart illustrating a routing information synchronization method provided in an embodiment of this application;

[0027] Figure 4This is a flowchart illustrating a method for determining the estimated response time of a route synchronization request, as provided in an embodiment of this application.

[0028] Figure 5 This is a schematic diagram illustrating an estimated response time provided in an embodiment of this application;

[0029] Figure 6 This is a schematic diagram illustrating another estimated response time provided in an embodiment of this application;

[0030] Figure 7 This is a schematic diagram of a process for obtaining the route information to be synchronized corresponding to a route synchronization request, provided in an embodiment of this application.

[0031] Figure 8 This is a schematic diagram of a process for determining a preset network bandwidth value provided in an embodiment of this application;

[0032] Figure 9 This is a flowchart illustrating a routing information synchronization method provided in an embodiment of this application;

[0033] Figure 10 This is a block diagram of a routing information synchronization device provided in an embodiment of this application;

[0034] Figure 11 This is a block diagram of a routing information synchronization system provided in an embodiment of this application;

[0035] Figure 12 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0036] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0037] It should be noted that the terms "comprising" and "having" and any variations thereof in the specification, claims and accompanying drawings of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product or server that includes a series of steps or units is not necessarily limited to those steps or units that are explicitly listed, but may include other steps or units that are not explicitly listed or that are inherent to such processes, methods, products or devices.

[0038] In related technologies, when a cluster management node makes a route change, it needs to synchronize the updated routing information to all storage nodes and clients in the cluster. As the storage capacity of the cluster increases, the number of storage nodes also increases. Iterations in the storage architecture and upgrades in storage node hardware will all lead to changes in routing information. Moreover, a cluster often needs to serve thousands to tens of thousands of clients, which requires the cluster management node to frequently send routing synchronization information to all storage nodes and clients. This not only makes it difficult to guarantee routing synchronization performance, but also consumes a lot of resources of the cluster management node, resulting in a decline in the performance of the entire cloud storage system.

[0039] As can be seen, the existing routing synchronization method synchronizes the latest routing information to all storage nodes and clients through the cluster management node. When the cluster management node becomes the bottleneck, the routing synchronization performance cannot be guaranteed, and it is difficult to scale to larger storage clusters.

[0040] Based on this, this application provides a routing information synchronization method. When the cluster management node performs a route change, it only needs to synchronize the updated routing information to all storage nodes and simultaneously push the corresponding storage node identifier to the client. This allows the client to obtain the updated routing information from the corresponding storage node based on the storage node identifier. In this way, the computational and network resources of the storage nodes are used to distribute the load on the cluster management node, improving routing synchronization performance. Furthermore, it greatly increases the scalability of the routing synchronization method, making it suitable for large-scale storage clusters. In addition, this application optimizes the process of storage nodes handling client routing synchronization requests. By estimating the response time of client routing synchronization requests, it determines whether to perform subsequent synchronization operations and controls the transmitted data traffic based on the node's own processing capabilities. This avoids request overload caused by storage nodes receiving too many routing synchronization requests, reduces the probability of network congestion and other anomalies, and thus improves the processing efficiency of storage nodes, achieving rapid synchronization of routing information.

[0041] Please see Figure 1 , Figure 1 This is a schematic diagram of an application environment provided in an embodiment of this application. The application environment may include a terminal device 11, a storage node 12, and a cluster management node 13. The terminal device 11 and the storage node 12 can communicate with each other through a communication network, which may be a local area network (LAN), a wide area network (WAN), or the like.

[0042] Terminal device 11 can be a physical device such as a smartphone, computer (e.g., desktop computer, tablet computer, laptop computer), augmented reality (AR) / virtual reality (VR) device, digital assistant, smart voice interaction device (e.g., smart speaker), smart wearable device, smart home appliance, in-vehicle terminal, etc., or it can be software running on the physical device, such as a computer program. The operating system corresponding to the client can be Android, iOS (a mobile operating system developed by Apple), Linux (an operating system), Microsoft Windows, etc.

[0043] Storage node 12 and cluster management node 13 can be independent physical servers, server clusters or distributed systems composed of multiple physical servers, or cloud servers providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. Servers may include network communication units, processors, and memory, etc. Storage node 12 and cluster management node 13 can provide backend services for terminal device 11.

[0044] For easier understanding, please refer to Figure 2 The process of synchronizing routing information provided in the embodiments of this application will be briefly described. Figure 2 This is a schematic diagram of a cloud storage environment provided in an embodiment of this application. The storage cluster includes client 1, client 2... client N, storage node 1, storage node 2, storage node 3... storage node N, and a cluster management node. The cluster management node is used to maintain the routing information of the cluster. Each storage node is used to store data. Each client is used to obtain the data it wants from the corresponding storage node according to the routing information.

[0045] When a storage node in the cluster experiences a hardware failure that necessitates its deletion or when storage expansion requires the addition of a new storage node, the cluster topology changes. In this case, the cluster management node needs to modify the routing information. For example, if storage node N experiences a hardware failure and needs to be deleted, the cluster management node needs to modify the routing information to change the path that originally pointed to storage node N. This will assign a new route to client 1, which previously obtained user data from storage node N, guiding client 1 to obtain user data from other storage nodes.

[0046] After updating the routing information, the cluster management node performs the following steps: ①: synchronize the updated routing information to each storage node; ②: send the storage node identifier to each client; then, the client performs the following step: ③: send a routing synchronization request to the corresponding storage node based on the corresponding storage node identifier; upon receiving the routing synchronization request, the corresponding storage node performs the routing information synchronization operation; finally, the node performs the following step: ④: return the updated routing information to the client, completing the routing information synchronization.

[0047] In this embodiment, the routing information synchronization operation performed by the storage node after receiving a routing synchronization request is optimized. In some possible embodiments, when the storage node receives a routing synchronization request sent by the client, it determines the estimated response time of the routing synchronization request based on the current pending request information; the estimated response time represents the time elapsed from the moment the routing synchronization request is received until the moment the routing information corresponding to the routing synchronization request is sent back; if the estimated response time is less than or equal to a preset time, the storage node obtains the routing information to be synchronized corresponding to the routing synchronization request; when the current network bandwidth value is less than or equal to a preset network bandwidth value, the storage node sends the routing information to be synchronized to the client; the preset network bandwidth value represents the maximum network bandwidth value when the local system is working normally.

[0048] For example, when storage node 1 receives a route synchronization request from client 1, if it determines that the estimated response time is less than or equal to the preset time, it will determine to perform the corresponding route information synchronization operation, that is, to obtain the route information to be synchronized corresponding to the route synchronization request. When the current network bandwidth value is less than or equal to the preset network bandwidth value, storage node 1 will send the route information to be synchronized to client 1. Thus, the route information synchronization process is completed.

[0049] The processing procedure for storage nodes will be described in detail below, but will not be repeated here.

[0050] In some possible implementations, the cluster management node can send multiple storage node identifiers to each client. For example, the cluster management node sends the identifiers of storage node 1, storage node 2, and storage node 3 to client 1. Client 1 first sends a route synchronization request to storage node 1 based on the identifier of storage node 1. If storage node 1 does not return routing information within a certain period of time, client 1 can execute step ⑤: send a route synchronization request to storage node 2 based on the identifier of storage node 2 to retry. If storage node 2 returns routing information within a certain period of time, the synchronization of routing information is completed; otherwise, client 1 can send a route synchronization request to storage node 3 based on the identifier of storage node 3... If all storage nodes fail to return routing information, client 1 can request routing information from the cluster management node.

[0051] It should be noted that, Figure 1 and Figure 2 The application scenario is just one example.

[0052] The following describes a specific embodiment of a routing information synchronization method according to this application, which can be applied to storage nodes in a cloud storage system. This application provides the operational steps of the method as described in the embodiments or flowcharts, but based on conventional or non-inventive methods, more or fewer operational steps may be included. The order of steps listed in the embodiments is merely one possible execution order among many steps and does not represent the only possible execution order. In actual system or product execution, the method can be executed sequentially according to the embodiments or accompanying drawings, or in parallel (e.g., in a parallel processor or multi-threaded processing environment). Figure 3 This is a flowchart illustrating a routing information synchronization method provided in an embodiment of this application, specifically as follows: Figure 3 As shown, the method may include:

[0053] S301: Upon receiving a route synchronization request from a client, determine the estimated response time of the route synchronization request based on the current pending request information.

[0054] The estimated response time represents the time elapsed from the moment the route synchronization request is received until the moment the corresponding route information packet is sent back after the route synchronization request is completed.

[0055] In this embodiment, the routing information synchronization process on the storage node side is optimized. First, when the storage node receives a routing synchronization request sent by the client, it determines the estimated response time of the routing synchronization request based on the current pending request information.

[0056] In some possible embodiments, the storage node and the client have a pre-signed Service Level Agreement (SLA). After receiving a user request from the client, the storage node can quantify the service to be provided according to the SLA. Under the terms of the SLA, the storage node will calculate the shortest method to complete the user task, such as estimating the response time of the client's routing synchronization request.

[0057] In some possible embodiments, the current pending request information includes the number of current pending requests and the amount of data in the routing information response packet; the storage node can determine the number of current pending requests and the amount of data in the routing information response packet from the current buffer queue; wherein, the current pending request may come from other clients in the cluster, and the routing information returned by the storage node to each client may be the full routing information, so that the amount of data in the routing information response packet corresponding to different clients is the same;

[0058] Accordingly, the estimated response time for determining the routing synchronization request based on the current pending request information can include, for example: Figure 4 The following steps are shown:

[0059] S3011: Determine the packet transmission duration based on the amount of data returned by the routing information and the current network bandwidth value.

[0060] Here, the current network bandwidth value represents the amount of data transmitted per unit time; the packet sending time refers to the time required to send a routing information return packet; the packet sending time can be obtained by dividing the amount of data in the routing information return packet by the current network bandwidth value; when the corresponding routing information is full routing information, the packet sending time corresponding to each currently pending request is equal.

[0061] S3013: Determine whether the packet sending time is greater than or equal to the preset local processing time. If the packet sending time is greater than or equal to the preset local processing time, proceed to step S3015; otherwise, proceed to step S3017.

[0062] The preset local processing time refers to the time required for the storage node to execute the corresponding processing logic for a user request. Here, the preset local processing time is the time required for the storage node to retrieve the corresponding routing information from its local memory. When the corresponding routing information is the full routing information, the preset local processing time for each currently pending request is equal. The sum of the packet sending time and the preset local processing time is the processing cycle for a currently pending request.

[0063] S3015: The first calculation method is used to obtain the estimated response time for the packet sending time, the number of currently pending requests, and the preset local processing time.

[0064] Please see Figure 5 , Figure 5 This is a schematic diagram illustrating an estimated response time provided in an embodiment of this application. Figure 5 In this context, if the packet transmission time is greater than or equal to the preset local processing time, it indicates that there is a bottleneck in the network of the current storage node. Therefore, in a specific embodiment, S3015 may include: determining the total packet transmission time of the current pending requests based on the packet transmission time and the number of pending requests; adding the total packet transmission time to the preset local processing time to obtain the estimated response time. Correspondingly, the first calculation method described above can be expressed by the following formula (1):

[0065] RT=t+(R+1)*P / X......(1)

[0066] Where RT represents the estimated response time; t represents the preset local processing time; R represents the number of requests currently pending processing; P / X represents the packet sending time, P represents the amount of data in the routing information return packet, and X represents the current network bandwidth value.

[0067] S3017: The second calculation method is used to obtain the estimated response time for the packet sending time, the number of currently pending requests, and the preset local processing time.

[0068] Please see Figure 6 , Figure 6 This is a schematic diagram illustrating another estimated response time provided in an embodiment of this application. Figure 6 If the packet sending time is less than the preset local processing time, it indicates that the processing capacity of the current storage node is bottlenecked. Therefore, in a specific embodiment, S3017 may include: determining the total processing time of the current pending requests based on the preset local processing time and the number of pending requests; adding the total processing time to the packet sending time to obtain the estimated response time. Correspondingly, the second calculation method described above can be expressed by the following formula (2):

[0069] RT=t*(R+1)+P / X......(2)

[0070] Where RT represents the estimated response time; t represents the preset local processing time; R represents the number of requests currently pending processing; P / X represents the packet sending time, P represents the amount of data in the routing information return packet, and X represents the current network bandwidth value.

[0071] In the above embodiments, the storage node analyzes whether the bottleneck is in the network or in the processing capacity by comparing the packet sending time with the preset local processing time. Under different bottleneck problems, different calculation methods are adopted to accurately predict the response time of the current routing synchronization request.

[0072] S303: Determine whether the estimated response time is less than or equal to the preset time. If the estimated response time is less than or equal to the preset time, proceed to steps S305 to S307; otherwise, proceed to step S313.

[0073] In this embodiment, after determining the estimated response time of the routing synchronization request, the storage node compares the estimated response time with a preset time, and determines the subsequent synchronization process based on the comparison result. The preset time can be the time during which the client initiates a request retry.

[0074] S305: Obtain the route information to be synchronized corresponding to the route synchronization request.

[0075] S313: Returns an indication message to the client that the route synchronization request is rejected.

[0076] In this embodiment of the application, if it is determined that the estimated response time is less than or equal to the preset time, it means that the storage node estimates that it can return the routing information packet to the client before the client initiates a request to retry. In this case, the storage node stores the routing synchronization request in the buffer queue. After the storage node has processed all the current pending requests, it reads the routing synchronization request from the buffer queue and obtains the routing information to be synchronized corresponding to the routing synchronization request.

[0077] In some possible embodiments, the maintenance of routing information by the cluster management node may include adding, deleting, and modifying routes. However, the routes added, deleted, and modified are usually partial routes, with some routes remaining unchanged. Therefore, to improve the efficiency of route synchronization and reduce the bandwidth consumed by route synchronization, the routing information to be synchronized in this embodiment can be incremental update information. This enables incremental updates of routing information.

[0078] In some possible embodiments, the route synchronization request includes a route version identifier; the process of obtaining the route information to be synchronized corresponding to the route synchronization request may include, for example... Figure 7 The following steps are shown:

[0079] S3051: Determine whether a route version identifier exists in the preset cache area. If the route version identifier exists in the preset cache area, proceed to step S3053; otherwise, proceed to step S3055.

[0080] S3053: Obtain the routing information corresponding to the routing version identifier from the preset cache area, and use the routing information as the routing information to be synchronized.

[0081] S3055: Retrieves the route information to be synchronized corresponding to the route version identifier from local memory.

[0082] The routing version identifier is used to distinguish incremental update information of different versions. Since the incremental update information generated each time the cluster management node maintains the routing information is different, the corresponding routing version identifier is generated synchronously when each incremental update information is generated. After each update of the routing information, the cluster management node sends the corresponding storage node identifier to the client, along with the corresponding routing version identifier, so that the client can obtain the corresponding incremental update information from the storage node based on the routing version identifier.

[0083] Data in storage nodes is typically stored in local memory. Storage nodes need to retrieve the corresponding routing information from local memory, but this process involves steps such as memory copying, which is very time-consuming. Therefore, considering that different clients may send routing synchronization requests to the same storage node, after processing a client's routing synchronization request, the storage node can store the incremental update information retrieved from local memory and the corresponding routing version identifier in a preset cache area. The next time the same routing version identifier is received, the corresponding incremental update information can be directly read from the preset cache area, thus saving the time of retrieving information from local memory.

[0084] In some possible embodiments, the preset cache area adopts a first-in-first-out (FIFO) cache replacement strategy. Specifically, when the preset cache area is full, that is, when it contains a certain number of different versions of routing information to be synchronized, no new data can be written, otherwise it will lead to data overflow; therefore, the routing information to be synchronized is deleted sequentially according to the order in which it is written to the preset cache area, so as to make room for the updated version of the routing information to be synchronized.

[0085] In the above embodiments, during the process of obtaining the routing information to be synchronized, the storage node first determines whether there is a routing version identifier in the preset cache area. If it exists, it means that other clients have obtained the same routing information in the past, and the routing information has been pre-stored in the preset cache area. At this time, the storage node does not need to access local memory and directly reads the routing information corresponding to the routing version identifier from the preset cache area and uses it as the routing information to be synchronized. In this way, local memory access can be saved, the acquisition speed of the routing information to be synchronized can be improved, and the time consumption of the entire routing synchronization process can be reduced.

[0086] S307: Determine whether the current network bandwidth value is less than or equal to the preset network bandwidth value. If the current network bandwidth value is less than or equal to the preset network bandwidth value, proceed to step S309; ​​otherwise, proceed to step S311.

[0087] S309: Send the routing information to be synchronized to the client.

[0088] S311: Store the routing information to be synchronized in the buffer area to be sent until the current network bandwidth value is less than or equal to the preset network bandwidth value.

[0089] The preset network bandwidth value represents the maximum network bandwidth value when the local system is working normally.

[0090] In this embodiment, the storage node obtains the current network bandwidth value in real time and uses the preset network bandwidth value as the traffic threshold. When the current network bandwidth value is greater than the preset network bandwidth value, it indicates that the current performance of the storage node has reached a bottleneck. If the transmission of the routing information to be synchronized is executed at this time, it may cause the performance of the storage node to crash. Therefore, the transmission of the routing information to be synchronized is temporarily suspended. After a period of time, when the current network bandwidth value is less than or equal to the preset network bandwidth value, the transmission of the delayed routing information to be synchronized is executed.

[0091] In some possible embodiments, prior to S307, the routing information synchronization method of this application embodiment may further include, as follows: Figure 8 The following steps are shown:

[0092] S3061: Get the client's timeout retry time.

[0093] The timeout retry time represents the time interval between when the client sends a route synchronization request again after not receiving a response within a certain period of time after the client first sends the route synchronization request.

[0094] S3063: Get the current and maximum occupancy values ​​of the pending request buffer.

[0095] The pending request buffer, also known as the buffer queue mentioned above, is used to store routing synchronization requests that the storage node has not yet processed. The maximum size of the pending request buffer is fixed and determined by the storage node's hardware.

[0096] In a specific embodiment, obtaining the current occupancy value of the pending request buffer in S3063 may include the following steps:

[0097] S30631: Determine the amount of unsent data in the routing information return packets corresponding to each pending request in the pending request buffer;

[0098] The current occupancy value of the pending request buffer occurs when a network bottleneck appears at the storage node, combined with... Figure 5 As shown, taking the routing information response packet corresponding to the first pending request as an example, when the second pending request is processed locally, there is still an unsent amount of P / Xt data, which will cause a corresponding occupancy value; it should be noted that, for ease of understanding, the unsent amount of data is represented by the corresponding duration.

[0099] S30633: Determine the current occupancy value based on the amount of unsent data in the routing information return packet corresponding to each pending request and the number of pending requests in the pending request buffer.

[0100] In a specific embodiment, the current occupancy value determined based on the amount of unsent data in the routing information return packet corresponding to each pending request and the number of pending requests in the pending request buffer can be expressed as (1-t / (P / X))*P*R.

[0101] S3065: Determine a preset network bandwidth value under the first constraint that the timeout retry time is greater than the estimated response time and / or the second constraint that the maximum occupancy value is greater than the current occupancy value, as well as under the network bandwidth limitation condition.

[0102] In a specific embodiment, the first constraint that the timeout retry time is greater than the estimated response time can be expressed as:

[0103] T>t+(R+1)*P / X

[0104] Where T represents the timeout retry time;

[0105] The second constraint that the maximum occupied value is greater than the current occupied value can be expressed as:

[0106] B>(1-t / (P / X))*P*R

[0107] Where B represents the maximum occupied value;

[0108] Network bandwidth limitations can be expressed as:

[0109] X < W

[0110] Where W represents the maximum network bandwidth value;

[0111] Based on the first constraint, the second constraint, and the network bandwidth limitation, the range of the preset network bandwidth value can be derived as follows:

[0112] max{P*(R+1) / (Tt),(1-B / (P*R))*P / t}<X<W

[0113] Therefore, the final preset network bandwidth value is selected from the aforementioned range of preset network bandwidth values. For example, if W is 90Mb / s and the maximum value calculated on the left is 80Mb / s, then X can be 85Mb / s.

[0114] In the above embodiments, the storage node determines the preset network bandwidth value by combining multiple constraints. By controlling the current network bandwidth value through the preset network bandwidth value, it can avoid anomalies such as avalanche caused by the excessive occupancy of the pending request buffer, provided that the response to the routing synchronization request does not time out.

[0115] In some possible embodiments, before sending the routing information to be synchronized to the client, the routing information synchronization method of this application embodiment may further include: deleting redundant information in the routing information to be synchronized; the redundant information includes the IP information of the storage node and / or cluster ID information; and compressing the routing information to be synchronized after deleting the redundant information.

[0116] Considering that the routing information to be synchronized may include multiple paths pointing to different target data storage addresses, and each path carries the same information (such as the storage node's IP address, cluster ID, etc.), and that when a storage node sends different routing information to the same client at different times, each piece of routing information will carry the aforementioned redundant information; therefore, in a specific embodiment, the redundant information in the routing information to be synchronized is extracted and sent to the client only once. Subsequent routing information can use preset identifiers to refer to this redundant information, thus reducing the routing packet size. Experiments have shown that this optimization can reduce the size of the routing information return packet by approximately 50%. Compression processing can employ algorithms such as LZ4 compression, which can significantly reduce the routing packet size. In experiments, using the LZ4 compression algorithm further reduced the routing packet size by approximately 50%.

[0117] In summary, in this embodiment, when a storage node receives a route synchronization request from a client, it can refer to steps S301 to S313 and their optional embodiments to perform corresponding route information synchronization operations. On the one hand, based on the current pending request information, the estimated response time of the route synchronization request is determined, and only requests that can return within the expected time are processed, while requests with long response times are rejected. This avoids the waiting time of the client at the storage node and prevents the request overload of a single storage node. Thus, the synchronization time of route information can be shortened and the synchronization efficiency improved. On the other hand, in order to avoid the avalanche and other anomalies caused by the excessive occupancy of the buffer due to the sending of a large number of route information return packets, which would render the storage node unusable, the storage node determines whether to perform flow control based on the current network bandwidth value before sending the route information return packet. When the current network bandwidth value exceeds the preset network bandwidth value, the sending of the route information to be synchronized is temporarily suspended. This improves the stability of the storage node and thus improves the success rate of route information synchronization.

[0118] Furthermore, in this embodiment, in addition to optimizing the routing information synchronization process on the storage node side, optimizations have also been made on the cluster management node side. In the cloud storage system, the cluster management node and the client communicate via heartbeat sessions to confirm the client's liveness. As mentioned above, after updating the routing information, the cluster management node sends a storage node identifier to the client so that the client can obtain the updated routing information from the corresponding storage node based on the storage node identifier.

[0119] Therefore, embodiments of this application also provide a routing information synchronization method, applied to cluster management nodes and clients, such as... Figure 9 As shown, it includes the following steps:

[0120] S901: When the cluster management node receives the heartbeat information sent by the client, it determines at least one storage node identifier corresponding to the client.

[0121] S903: The cluster management node returns at least one storage node identifier to the client.

[0122] In this embodiment of the application, after updating the routing information, the cluster management node assigns at least one storage node identifier to all clients in the cluster, so that each client can obtain the updated routing information from the assigned storage node. In order to prevent too many routing synchronization requests from a single storage node, the cluster management node tries to assign different storage nodes to different clients. When it receives the heartbeat information sent by the client periodically, it returns the at least one storage node identifier assigned to it.

[0123] S905: The client sends a route synchronization request to the storage node corresponding to any of the storage node identifiers in at least one storage node identifier.

[0124] In some possible embodiments, the at least one storage node identifier mentioned above can be multiple storage node identifiers, and the multiple storage nodes corresponding to these multiple storage node identifiers are a set of redundant replicas of each other, that is, the multiple storage nodes store the same data content. Thus, if one of the storage nodes does not respond to the client's route synchronization request, the client can resend the route synchronization request to the other storage nodes.

[0125] After receiving a route synchronization request from the client, the storage node can perform the route information synchronization operation in S301 to S313 of the above embodiments to complete the route information synchronization process with the client.

[0126] This application also provides a routing information synchronization device, such as... Figure 10 As shown, the routing information synchronization device 100 includes:

[0127] The first determining module 1001 is used to determine the estimated response time of the route synchronization request based on the current pending request information when receiving the route synchronization request sent by the client; the estimated response time represents the time elapsed from the moment the route synchronization request is received to the moment the route information corresponding to the route synchronization request is sent back.

[0128] The acquisition module 1002 is used to acquire the route information to be synchronized corresponding to the route synchronization request if the estimated response time is less than or equal to the preset time.

[0129] The sending module 1003 is used to send the routing information to be synchronized to the client when the current network bandwidth value is less than or equal to the preset network bandwidth value; the preset network bandwidth value represents the maximum network bandwidth value when the local system is working normally.

[0130] In some possible embodiments, the current pending request information includes the number of current pending requests and the amount of data in the routing information return packet;

[0131] The first determining module 1001 is further configured to determine the packet transmission duration based on the amount of data returned by the routing information and the current network bandwidth value; if the packet transmission duration is greater than or equal to the preset local processing duration, the first calculation method is used to calculate the packet transmission duration, the number of currently pending requests, and the preset local processing duration to obtain the estimated response time; or; if the packet transmission duration is less than the preset local processing duration, the second calculation method is used to calculate the packet transmission duration, the number of currently pending requests, and the preset local processing duration to obtain the estimated response time.

[0132] In some possible embodiments, the first determining module 1001 is further configured to determine the total packet transmission time of the current pending requests based on the packet transmission time and the number of current pending requests; and add the total packet transmission time to the preset local processing time to obtain the estimated response time.

[0133] In some possible embodiments, the first determining module 1001 is further configured to determine the total processing time of the current pending requests based on the preset local processing time and the number of current pending requests; and add the total processing time to the packet sending time to obtain the estimated response time.

[0134] In some possible implementations, the route synchronization request includes a route version identifier;

[0135] The acquisition module 1002 is also used to, if it is determined that a route version identifier exists in the preset cache area, obtain the route information corresponding to the route version identifier from the preset cache area and use the route information as the route information to be synchronized; or, if it is determined that a route version identifier does not exist in the preset cache area, obtain the route information to be synchronized corresponding to the route version identifier from the local memory.

[0136] In some possible embodiments, the apparatus further includes:

[0137] The second determining module is used to obtain the client's timeout retry time; obtain the current and maximum occupancy values ​​of the pending request buffer; and determine a preset network bandwidth value under the first constraint that the timeout retry time is greater than the estimated response time and / or the second constraint that the maximum occupancy value is greater than the current occupancy value, as well as under the network bandwidth limitation condition.

[0138] In some possible embodiments, the second determining module is further configured to determine the amount of unsent data in the routing information return packets corresponding to each pending request in the pending request buffer; and to determine the current occupancy value based on the amount of unsent data in the routing information return packets corresponding to each pending request and the number of pending requests in the pending request buffer.

[0139] In some possible embodiments, the sending module 1003 is further configured to store the routing information to be synchronized in the sending buffer area when the current network bandwidth value is greater than the preset network bandwidth value, until the current network bandwidth value is less than or equal to the preset network bandwidth value.

[0140] In some possible embodiments, the sending module 1003 is further configured to return an indication message to the client that the route synchronization request is rejected if the estimated response time is greater than a preset time.

[0141] This application also provides a routing information synchronization system, such as... Figure 11 As shown, the routing information synchronization system 110 includes:

[0142] The routing information management device 1101 is used to maintain routing information; after the routing information is updated, it sends the updated routing version identifier and routing information to the routing information synchronization device.

[0143] The routing information management device 1101 is also used to determine at least one routing information synchronization device identifier corresponding to the client when receiving heartbeat information sent by the client, and return at least one routing information synchronization device identifier to the client so that the client can send a routing synchronization request to the routing information synchronization device corresponding to any one of the at least one routing information synchronization device identifiers.

[0144] The routing information synchronization device 1102 includes: a first determining module, used to determine the estimated response time of the routing synchronization request based on the current pending request information when receiving a routing synchronization request sent by a client; the estimated response time represents the time elapsed from the moment the routing synchronization request is received to the moment the routing information corresponding to the routing synchronization request is sent back; an obtaining module, used to obtain the routing information to be synchronized corresponding to the routing synchronization request if the estimated response time is less than or equal to a preset time; and a sending module, used to send the routing information to be synchronized to the client when the current network bandwidth value is less than or equal to a preset network bandwidth value; the preset network bandwidth value represents the maximum network bandwidth value when the local system is working normally.

[0145] In this embodiment, the routing information management device 1101 can be the cluster management node in the above method embodiment; the routing information synchronization device 1102 can be the storage node in the above method embodiment.

[0146] It should be noted that the apparatus, system and method embodiments in the device embodiments are based on the same inventive concept.

[0147] This application provides an electronic device including a processor and a memory. The memory stores at least one instruction or at least one program segment, which is loaded and executed by the processor to implement the routing information synchronization method provided in the above method embodiments.

[0148] Furthermore, Figure 12 A schematic diagram of the hardware structure of an electronic device for implementing the routing information synchronization method provided in the embodiments of this application is shown. The electronic device may participate in or include the routing information synchronization apparatus provided in the embodiments of this application. Figure 12 As shown, the electronic device 100 may include one or more processors 1002 (shown as 1002a, 1002b, ..., 1002n in the figure) (processor 1002 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 1004 for storing data, and a transmission device 1006 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of the I / O interface), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 12 The structure shown is for illustrative purposes only and does not limit the structure of the electronic device described above. For example, the electronic device may also include components that are more... Figure 12 The more or fewer components shown, or having the same Figure 12 The different configurations shown.

[0149] It should be noted that the aforementioned one or more processors 1002 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be wholly or partially integrated into any other element within the electronic device 100 (or mobile device). As involved in the embodiments of this application, the data processing circuit serves as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0150] The memory 1004 can be used to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the routing information synchronization method described in this embodiment. The processor 1002 executes various functional applications and data processing by running the software programs and modules stored in the memory 1004, thereby implementing the aforementioned routing information synchronization method. The memory 1004 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 1004 may further include memory remotely located relative to the processor 1002, and these remote memories can be connected to the electronic device 100 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0151] The transmission device 1006 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the electronic device 100. In one example, the transmission device 1006 includes a network interface controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In one embodiment, the transmission device 1006 may be a radio frequency (RF) module for wireless communication with the Internet.

[0152] The display can be, for example, a touchscreen liquid crystal display (LCD) that allows a user to interact with the user interface of the electronic device 100 (or mobile device).

[0153] Embodiments of this application also provide a computer-readable storage medium, which can be disposed in an electronic device to store at least one instruction or at least one program related to implementing a routing information synchronization method in the method embodiment. The at least one instruction or the at least one program is loaded and executed by the processor to implement the routing information synchronization method provided in the above method embodiment.

[0154] Optionally, in this embodiment, the storage medium may be located in at least one of the multiple network servers in a computer network. Optionally, in this embodiment, the storage medium may include, but is not limited to, various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0155] It should be noted that the order of the embodiments described above is merely for descriptive purposes and does not represent the superiority or inferiority of the embodiments. Furthermore, the above description focuses on specific embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps described in the claims can be performed in a different order than that shown in the embodiments and still achieve the desired results. Additionally, the processes depicted in the drawings do not necessarily require a specific or sequential order to achieve the desired results. In some implementations, multitasking and parallel processing are also possible or may be advantageous.

[0156] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device and electronic device embodiments are basically similar to the method embodiments, so the descriptions are relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0157] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a program instructing related hardware. The program can be stored in a computer-readable storage medium, such as a read-only memory, a disk, or an optical disk.

[0158] The above description is only a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. A method for synchronizing routing information, characterized in that, include: Upon receiving a route synchronization request from a client, the packet transmission duration is determined based on the current network bandwidth value and the amount of data in the routing information response packet of the current pending request information. The information on currently pending requests also includes the number of currently pending requests; If the packet sending time is greater than or equal to the preset local processing time, the first calculation method is used to calculate the packet sending time, the number of currently pending requests, and the preset local processing time to obtain the estimated response time. If the packet sending time is less than the preset local processing time, a second calculation method is used to calculate the packet sending time, the number of currently pending requests, and the preset local processing time to obtain the estimated response time. The estimated response time represents the time elapsed from the moment the route synchronization request is received until the moment the route information response packet corresponding to the route synchronization request is sent. If the estimated response time is less than or equal to the preset time, obtain the route information to be synchronized corresponding to the route synchronization request; When the current network bandwidth value is less than or equal to the preset network bandwidth value, the routing information to be synchronized is sent to the client; The preset network bandwidth value represents the maximum network bandwidth value when the local system is working normally.

2. The routing information synchronization method according to claim 1, characterized in that, The step of calculating the estimated response time by using the first calculation method on the packet sending duration, the number of currently pending requests, and the preset local processing duration includes: The total packet transmission time for the current pending requests is determined based on the packet transmission duration and the number of requests currently pending. The estimated response time is obtained by adding the total packet sending time to the preset local processing time.

3. The routing information synchronization method according to claim 1, characterized in that, The second calculation method is used to obtain the estimated response time based on the packet sending duration, the number of currently pending requests, and the preset local processing duration, including: The total processing time for the current pending requests is determined based on the preset local processing time and the number of requests currently pending. The estimated response time is obtained by adding the total processing time to the packet sending time.

4. The routing information synchronization method according to claim 1, characterized in that, The route synchronization request includes a route version identifier; The step of obtaining the route information to be synchronized corresponding to the route synchronization request includes: If it is determined that the route version identifier exists in the preset cache area, the route information corresponding to the route version identifier is obtained from the preset cache area, and the route information is used as the route information to be synchronized; Alternatively, if it is determined that the route version identifier does not exist in the preset cache area, the route information to be synchronized corresponding to the route version identifier is obtained from local memory.

5. The routing information synchronization method according to claim 1, characterized in that, Before sending the routing information to be synchronized to the client when the current network bandwidth value is less than or equal to a preset network bandwidth value, the method further includes: Obtain the timeout retry time of the client; Get the current and maximum occupancy values ​​of the pending request buffer; The preset network bandwidth value is determined under the first constraint that the timeout retry time is greater than the estimated response time and / or the second constraint that the maximum occupancy value is greater than the current occupancy value, as well as under the network bandwidth limitation condition.

6. The routing information synchronization method according to claim 5, characterized in that, The step of obtaining the current occupancy value of the buffer for requests to be processed includes: Determine the amount of unsent data in the routing information return packets corresponding to each pending request in the pending request buffer; The current occupancy value is determined based on the amount of unsent data in the routing information return packet corresponding to each pending request and the number of pending requests in the pending request buffer.

7. The routing information synchronization method according to claim 1, characterized in that, The method further includes: When the current network bandwidth value is greater than the preset network bandwidth value, the routing information to be synchronized is stored in the buffer area to be sent until the current network bandwidth value is less than or equal to the preset network bandwidth value.

8. The routing information synchronization method according to claim 1, characterized in that, The method further includes: If the estimated response time is greater than the preset time, an indication message rejecting the route synchronization request is returned to the client.

9. A routing information synchronization device, characterized in that, The device includes: The first determining module is used to determine the packet transmission duration based on the current network bandwidth value and the amount of data in the routing information return packet in the current pending request information when a routing synchronization request is received from a client; the current pending request information also includes the number of current pending requests; if the packet transmission duration is greater than or equal to a preset local processing duration, a first calculation method is used to calculate the packet transmission duration, the number of current pending requests, and the preset local processing duration to obtain an estimated response time; if the packet transmission duration is less than the preset local processing duration, a second calculation method is used to calculate the packet transmission duration, the number of current pending requests, and the preset local processing duration to obtain the estimated response time. The acquisition module is used to acquire the route information to be synchronized corresponding to the route synchronization request if the estimated response time is less than or equal to the preset time. The sending module is used to send the routing information to be synchronized to the client when the current network bandwidth value is less than or equal to a preset network bandwidth value; the preset network bandwidth value represents the maximum network bandwidth value when the local system is working normally.

10. The apparatus according to claim 9, characterized in that, The first determining module is further configured to determine the total packet transmission time of the current pending requests based on the packet transmission time and the number of current pending requests; and to add the total packet transmission time to the preset local processing time to obtain the estimated response time.

11. The apparatus according to claim 9, characterized in that, The first determining module is further configured to determine the total processing time of the current pending requests based on the preset local processing time and the number of current pending requests; and to add the total processing time to the packet sending time to obtain the estimated response time.

12. The apparatus according to claim 9, characterized in that, The route synchronization request includes a route version identifier; the acquisition module is further configured to, if it is determined that the route version identifier exists in the preset cache area, acquire the route information corresponding to the route version identifier from the preset cache area and use the route information as the route information to be synchronized; or, if it is determined that the route version identifier does not exist in the preset cache area, acquire the route information to be synchronized corresponding to the route version identifier from local memory.

13. The apparatus according to claim 9, characterized in that, The device further includes: The second determining module is used to obtain the client's timeout retry time; obtain the current and maximum occupancy values ​​of the pending request buffer; and determine a preset network bandwidth value under the first constraint that the timeout retry time is greater than the estimated response time and / or the second constraint that the maximum occupancy value is greater than the current occupancy value, as well as under the network bandwidth limitation condition.

14. The apparatus according to claim 13, characterized in that, The second determining module is further configured to determine the amount of unsent data in the routing information return packets corresponding to each pending request in the pending request buffer; and to determine the current occupancy value based on the amount of unsent data in the routing information return packets corresponding to each pending request and the number of pending requests in the pending request buffer.

15. The apparatus according to claim 9, characterized in that, The sending module is further configured to store the routing information to be synchronized in the sending buffer area when the current network bandwidth value is greater than the preset network bandwidth value, until the current network bandwidth value is less than or equal to the preset network bandwidth value.

16. The apparatus according to claim 9, characterized in that, The sending module is also used to return an indication message to the client that the route synchronization request is rejected if the estimated response time is greater than a preset time.

17. A routing information synchronization system, characterized in that, The system includes a routing information synchronization device and a routing information management device as described in any one of claims 9-16; The routing information management device is used to maintain routing information; after the routing information is updated, it sends the updated routing version identifier and routing information to the routing information synchronization device. The routing information management device is further configured to, upon receiving heartbeat information sent by the client, determine at least one routing information synchronization device identifier corresponding to the client, and return the at least one routing information synchronization device identifier to the client, so that the client sends a routing synchronization request to the routing information synchronization device corresponding to any one of the at least one routing information synchronization device identifiers. The routing information synchronization device includes: a first determining module, configured to determine the estimated response time of the routing synchronization request based on the current pending request information when receiving a routing synchronization request sent by the client; the estimated response time represents the time elapsed from the moment the routing synchronization request is received until the moment the routing information return packet corresponding to the routing synchronization request is sent; an obtaining module, configured to obtain the routing information to be synchronized corresponding to the routing synchronization request if the estimated response time is less than or equal to a preset time; and a sending module, configured to send the routing information to be synchronized to the client when the current network bandwidth value is less than or equal to a preset network bandwidth value; the preset network bandwidth value represents the maximum network bandwidth value when the local system is working normally.

18. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory storing at least one instruction or at least one program, the at least one instruction or the at least one program being loaded and executed by the processor to implement the routing information synchronization method as described in any one of claims 1-8.

19. A computer storage medium, characterized in that, The storage medium stores at least one instruction or at least one program, which is loaded and executed by a processor to implement the routing information synchronization method as described in any one of claims 1-8.

20. A computer program product, characterized in that, The computer program product includes at least one instruction or at least one program segment, which is loaded and executed by a processor to implement the routing information synchronization method as described in any one of claims 1-8.

Images