ARP (Address Resolution Protocol) information processing method, device, equipment and medium

Abstract

The invention relates to the technical field of communication, in particular to an ARP (Address Resolution Protocol) information processing method and device, equipment and a medium, which are used for improving the efficiency of ARP information processing. The method comprises the following steps: a main node applied to a cluster sends an ARP information acquisition request to each proxy node in the cluster after a preset acquisition condition is met, so as to obtain ARP information of each proxy node; the acquisition condition comprises at least one of the following conditions: timed acquisition and response to an acquisition request of the object; updating a main database corresponding to the main node according to each piece of acquired ARP information; and sending the updated ARP information in the main database to each proxy node, so that each proxy node updates a proxy database corresponding to the proxy node according to the ARP information in the main database.

Description

Background Art

[0002] With the rapid development of data centers, cloud computing platforms, and high-performance computing clusters, the scale of networks is expanding. Especially in large-scale cluster environments, the Address Resolution Protocol (ARP) plays a vital role in the communication between network nodes. The ARP protocol is responsible for mapping Internet Protocol (IP) addresses to Media Access Control Address (MAC) addresses and is the basis of network communication. However, in large-scale cluster environments, especially when there are network failures or node changes, frequent generation of ARP requests may cause a surge in network load and even trigger large-scale path query requests. This frequent ARP update not only consumes a lot of bandwidth, but also puts great pressure on network equipment and services, affecting the stability and responsiveness of the network.

[0003] To solve this problem, the related art generally avoids frequent ARP requests by manually configuring static ARP information, thereby reducing network load. Since this method relies on Secure Shell (SSH) remote login and script operations, it faces the following challenges in large-scale clusters:

[0004] First, remote configuration using SSH requires password-free login, which brings certain security risks. Second, due to the large number of cluster nodes, static ARP configuration using scripts is slow, especially when the number of nodes surges, the configuration process becomes extremely time-consuming and inefficient. In addition, the SSH configuration method lacks flexibility and interactivity.

[0005] In summary, how to improve the efficiency of ARP information processing is a technical problem that needs to be solved urgently. Summary of the invention

[0006] Embodiments of the present application provide an ARP information processing method, device, electronic device, and storage medium to improve the efficiency of ARP information processing.

[0007] An ARP information processing method provided in an embodiment of the present application is applied to a master node in a cluster, including:

[0008] After the preset collection conditions are met, an ARP information collection request is sent to each proxy node in the cluster to obtain the ARP information of each proxy node; the collection conditions include at least one of the following: timed collection, in response to the collection request of the object;

[0009] According to each ARP information obtained, update the master database corresponding to the master node;

[0010] The updated ARP information in the main database is sent to each proxy node respectively, so that each proxy node updates the proxy database corresponding to the proxy node according to the ARP information in the main database.

[0011] Optionally, receiving an ARP information configuration request sent by a first proxy node in the cluster; the ARP information configuration is sent by the first proxy node after determining that the corresponding proxy database is not configured with ARP information;

[0012] According to the ARP information configuration request, the ARP information of each proxy node in the main database is queried, and the ARP information of each proxy node is sent to the first proxy node, so that the first proxy node configures the proxy database corresponding to the first proxy node according to the ARP information of each proxy node.

[0013] Through the above process, the master node can efficiently manage the ARP information of each proxy node in the cluster. When the proxy node is not configured with ARP information, the master node receives the configuration request of the first proxy node that is not configured with ARP information, and promptly queries and returns the latest ARP information in the master database to ensure that the proxy node that sends the configuration request can quickly update its local proxy database. This process can better maintain the synchronization of ARP information within the cluster, improve the stability and reliability of the network, and effectively reduce the risk of communication interruption or network unreachability caused by proxy nodes that are not configured with ARP information.

[0014] Optionally, receiving an ARP information change message sent by a second proxy node in the cluster; the ARP information change message includes: updated ARP information corresponding to the second proxy node;

[0015] updating the master database according to the updated ARP information, and querying a third proxy node related to the second proxy node;

[0016] Notify the second proxy node and the third proxy node to update corresponding proxy databases according to the updated ARP information.

[0017] Through the above process, the master node can timely receive and process the ARP information changes of the proxy node, ensuring the real-time update of the ARP database. When the ARP information of the second proxy node changes, the master node updates the master database according to the received change message, and queries other proxy nodes related to the second proxy node according to the changed ARP information. The master node further notifies the relevant proxy nodes to update the local proxy database according to the updated ARP information. This process can ensure the consistency and synchronization of the ARP information of each proxy node in the cluster, avoid network communication failures caused by inconsistent information, improve the reliability and stability of the entire network, and ensure smooth communication between the proxy nodes in the cluster.

[0018] Optionally, when sending ARP information to any of the proxy nodes, if it is detected that there is a task that fails to be sent, the task is added to a retry task queue;

[0019] According to the first duration, the tasks in the retry task queue are periodically triggered to resend the ARP information corresponding to the tasks.

[0020] Through the above process, the master node can effectively handle failures encountered when sending ARP information. When sending ARP information to the proxy node, if a sending failure is detected, the master node will add the failed task to the retry task queue, and trigger the retry mechanism according to the preset first duration, and retry to send the unsuccessful ARP information. This retry mechanism can ensure the reliable transmission of ARP information, avoid the failure to update ARP information in time due to network fluctuations or other problems, and ensure that the proxy node can successfully receive the latest ARP information and update its proxy database. In this way, the master node can improve the overall stability and fault tolerance, reduce communication problems caused by the failure to update ARP information, ensure efficient and reliable communication between proxy nodes in the cluster, and enhance the overall operation efficiency of the network.

[0021] Optionally, perform at least one of the following processing operations on the received ARP information:

[0022] De-duplicate the ARP information sent by the same proxy node;

[0023] For the same type of ARP information sent by different proxy nodes, the same type of ARP information is merged into one ARP information;

[0024] Discard the ARP information in the message queue that exceeds the preset threshold length;

[0025] Sort different ARP information by priority and process them in sequence.

[0026] Through the above process, the master node can efficiently manage and process the received ARP information. First, the ARP information sent by the same proxy node can be deduplicated to avoid redundant processing caused by duplicate data and improve overall efficiency; secondly, for the same type of ARP information from different proxy nodes, the master node can merge them into one message for processing, reduce the processing burden and optimize resource usage; in addition, the master node can also discard the ARP information in the message queue that exceeds the preset threshold to prevent invalid data from occupying resources and ensure the smoothness of the processing process; finally, the master node can also sort the ARP information according to its priority to ensure that important ARP information is processed first, thereby improving response speed and overall performance. Through these processing measures, the master node can improve the overall processing capacity and efficiency, ensure the timeliness and accuracy of ARP information processing, and further enhance the communication stability and network performance between proxy nodes in the cluster.

[0027] Optionally, the proxy nodes are grouped according to their IP addresses, and one proxy node is selected from each group of proxy nodes as a relay node;

[0028] The updated ARP information in the database is sent to the relay node, so that the ARP information in the database is forwarded to other proxy nodes in the same group through the relay node.

[0029] Through the above process, the master node groups the proxy nodes according to their IP addresses and selects a proxy node in each group as a relay node, reducing the burden of sending information directly to each proxy node individually. Then, the updated ARP information is sent to the relay node, which is responsible for forwarding the information to other proxy nodes in the same group. This relay forwarding mechanism not only reduces the network load and improves the efficiency of information transmission, but also ensures that each proxy node can receive the updated ARP information in a timely manner, further improving the synchronization and communication efficiency between proxy nodes in the cluster. Through the above process, the master node can better manage and optimize the distribution of ARP information within the cluster, enhance the stability and reliability of the network, and effectively improve the transmission efficiency of ARP information.

[0030] Another ARP information processing method provided in an embodiment of the present application is applied to a proxy node in a cluster, including:

[0031] After receiving the ARP information collection request sent by the master node in the cluster, the ARP information of the proxy node is obtained and sent to the master node, so that the master node updates the master database corresponding to the master node according to the obtained ARP information, and sends the updated ARP information in the master database to the proxy node respectively; the ARP information collection request is sent by the master node after satisfying at least one of the following preset collection conditions: timed collection, in response to the collection request of the object;

[0032] After receiving the ARP information in the main database sent by the master node, the corresponding proxy database is updated according to the ARP information.

[0033] Optionally, after determining that the corresponding proxy database is not configured with ARP information, sending an ARP information configuration request to the master node, so that the master node queries and returns the ARP information of each proxy node in the master database according to the ARP information configuration request;

[0034] According to the ARP information of each proxy node, a corresponding proxy database is configured.

[0035] Through the above process, the proxy node can actively send an ARP information configuration request to the master node when it finds that it has not configured ARP information. After receiving the request, the master node queries the latest ARP information in the master database and returns the latest ARP information in the master database to the proxy node. The proxy node updates the local proxy database based on the received ARP information, thereby ensuring that its ARP information is synchronized in time and avoiding network communication interruptions or errors caused by unconfigured ARP information. This mechanism helps the proxy node automatically solve the problem of missing ARP information, ensures stable communication between proxy nodes in the cluster, and improves the self-adaptation ability and network reliability of the proxy node in the cluster.

[0036] Optionally, if it is determined through a periodic check that the ARP information is not configured, before determining that the ARP information is not configured, a periodic check is performed according to a second time period to determine whether the ARP information is configured in the corresponding proxy database;

[0037] and, if the proxy database configuration fails, reducing the second duration;

[0038] If the proxy database is configured successfully, the second duration is increased.

[0039] Through the above process, the proxy node can regularly detect its own ARP information configuration status through the preset second duration. When the proxy node finds that it has not configured ARP information, it will send a configuration request to the master node to configure the proxy database. At the same time, the proxy node will dynamically adjust the inspection interval according to the progress of the proxy database configuration: if the configuration fails, the second duration will be shortened to speed up the re-acquisition of ARP information; if the configuration is successful, the second duration will be extended to reduce unnecessary inspections, reduce the load and resource consumption of the proxy node. This mechanism ensures the timely update of ARP information, avoids overly frequent inspection operations, optimizes resource usage, and improves the adaptive ability of the proxy node and the overall network stability of the cluster.

[0040] Optionally, after determining that its own ARP information has changed, sending updated ARP information to the master node through an ARP information change message, so that the master node updates the master database according to the updated ARP information, and notifies the relevant proxy nodes to update the corresponding proxy databases according to the updated ARP information;

[0041] According to the updated ARP information, the corresponding proxy database is updated.

[0042] Through the above process, the proxy node can send updated ARP information to the master node in a timely manner when the ARP information changes. This mechanism ensures that the master node can update the ARP information in the master database in a timely manner, and notify the relevant proxy nodes to synchronize and update according to the updated data. Through this information synchronization and update mechanism, the consistency of ARP information of each proxy node in the cluster is guaranteed, avoiding network communication problems caused by inconsistent ARP information. At the same time, the master node can respond to changes in the proxy node in a timely manner, enhancing the stability and reliability of the entire network, and effectively improving the ARP information management efficiency of the cluster.

[0043] Optionally, if the proxy node is a relay node, the ARP information is forwarded to other proxy nodes in the same group, so that the other proxy nodes update corresponding proxy databases according to the ARP information;

[0044] The proxy nodes in the same group are obtained by grouping the proxy nodes in the cluster by the master node according to the IP addresses of the proxy nodes, and the relay node in each group is a proxy node selected from the group.

[0045] Through the above process, the proxy node as a relay node can effectively forward the updated ARP information to other proxy nodes in the same group, thereby achieving efficient information dissemination and synchronization. The master node groups the proxy nodes according to their IP addresses and connects the proxy nodes in the same group, so that the relay nodes in each group can take on the forwarding task, reducing the unnecessary information transmission burden in the network. At the same time, this mechanism ensures that each proxy node can update its own proxy database in a timely manner, ensuring the consistency and timeliness of ARP information in the cluster, and effectively improving the stability and communication efficiency of the network.

[0046] An ARP information processing device provided in an embodiment of the present application is applied to a master node in a cluster, including:

[0047] A collection unit is used to send an address resolution protocol ARP information collection request to each proxy node in the cluster to obtain the ARP information of each proxy node after a preset collection condition is met; the collection condition includes at least one of the following: timed collection in response to a collection request of an object;

[0048] A first updating unit, configured to update a master database corresponding to the master node according to each acquired ARP information;

[0049] The first sending unit is used to send the updated ARP information in the main database to each of the proxy nodes, so that each proxy node updates the proxy database corresponding to the proxy node according to the ARP information in the main database.

[0050] Another ARP information processing device provided in an embodiment of the present application is applied to a proxy node in a cluster, including:

[0051] The second sending unit is used to obtain the ARP information of the proxy node and send it to the master node after receiving the ARP information collection request sent by the master node in the cluster, so that the master node updates the master database corresponding to the master node according to the obtained ARP information, and sends the updated ARP information in the master database to the proxy node respectively; the ARP information collection request is sent by the master node after satisfying at least one of the following preset collection conditions: timed collection, in response to the collection request of the object;

[0052] The second updating unit is configured to update the corresponding proxy database according to the ARP information received from the master node in the master database.

[0053] An ARP information processing system provided in an embodiment of the present application includes a master node and a proxy node:

[0054] The master node is used to send an ARP information collection request to each proxy node in the system after the preset collection conditions are met to obtain the ARP information of each proxy node; update the corresponding master database according to each ARP information obtained; send the updated ARP information in the master database to each proxy node respectively; the collection conditions include at least one of the following: timed collection, in response to the collection request of the object;

[0055] Each of the proxy nodes is used to obtain the corresponding ARP information and send it to the master node after receiving the ARP information collection request; and update the corresponding proxy database according to the ARP information received from the master database.

[0056] An electronic device provided by an embodiment of the present application includes a processor and a memory, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of any one of the above-mentioned ARP information processing methods.

[0057] An embodiment of the present application provides a computer-readable storage medium, which includes a computer program. When the computer program is executed on an electronic device, the computer program is used to enable the electronic device to execute the steps of any one of the above-mentioned ARP information processing methods.

[0058] An embodiment of the present application provides a computer program product, which includes a computer program, and the computer program is stored in a computer-readable storage medium; when a processor of an electronic device reads the computer program from the computer-readable storage medium, the processor executes the computer program, so that the electronic device performs the steps of any one of the above-mentioned ARP information processing methods.

[0059] The beneficial effects of this application are as follows:

[0060] The embodiment of the present application provides an ARP information processing method, device, electronic device and storage medium. First, the master node can obtain the ARP information of each proxy node in real time by sending an ARP information collection request to each proxy node in the cluster, ensuring that the ARP information of all proxy nodes remains up to date, avoiding communication errors or routing problems caused by information lag. In this way, the master node can timely grasp the changes in the network topology of the entire cluster, and provide accurate data support for subsequent network management and troubleshooting.

[0061] Next, the master node updates the master database based on the ARP information of each proxy node obtained. This step ensures that the ARP information stored in the master database is the latest data of each node in the cluster, thereby improving the consistency and reliability of the data.

[0062] Finally, the master node sends the updated ARP information to each proxy node, ensuring that each proxy node updates its local database based on the latest information in the master database. This process can effectively ensure the synchronization of the proxy node's ARP information with the master node, allowing each proxy node to promptly obtain and apply address change information from other nodes in the network, avoiding access failures, network congestion, or other communication problems caused by outdated local ARP information. At the same time, this operation eliminates the data inconsistency problems that may exist between the proxy nodes, allowing the ARP information of the entire cluster to remain synchronized, reducing network failures and performance bottlenecks caused by data inconsistencies.

[0063] In summary, through the method of the present application, the master node realizes centralized management and real-time update of ARP information, ensures the data consistency of each proxy node in the cluster and the stability of network communication, and improves the response speed and reliability of the overall network.

[0064] Other features and advantages of the present application will be described in the following description, and partly become apparent from the description, or be understood by practicing the present application. The purpose and other advantages of the present application can be realized and obtained by the structures specifically pointed out in the written description, claims, and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0066] Figure 1 A schematic diagram of an application scenario provided for an embodiment of the present application;

[0067] Figure 2 An implementation flow chart of an ARP information processing method provided in an embodiment of the present application;

[0068] Figure 3 A schematic diagram of a process for collecting ARP information provided in an embodiment of the present application;

[0069] Figure 4 A schematic diagram of a master node ARP information processing method provided in an embodiment of the present application;

[0070] Figure 5 A flowchart of another ARP information processing method provided in an embodiment of the present application;

[0071] Figure 6 A schematic diagram of processing of ARP information configuration of a proxy node provided in an embodiment of the present application;

[0072] Figure 7 A schematic diagram of processing ARP information changes of a proxy node provided in an embodiment of the present application;

[0073] Figure 8 A schematic diagram of the structure of an ARP information processing device in an embodiment of the present application;

[0074] Fig. 9 A schematic diagram of the structure of another ARP information processing device in an embodiment of the present application;

[0075] Fig.10 The figure is a schematic diagram of the structure of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0076] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the technical solution of the present application, rather than all of the embodiments. Based on the embodiments recorded in the application documents, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the technical solution of the present application.

[0077] The preferred embodiments of the present application are described below in conjunction with the drawings in the specification. It should be understood that the preferred embodiments described herein are only used to illustrate and explain the present application, and are not used to limit the present application. In addition, the embodiments and features in the embodiments of the present application may be combined with each other if there is no conflict.

[0078] like Figure 1 As shown, it is a schematic diagram of an application scenario provided in an embodiment of the present application.

[0079] In the embodiment of the present application, the cluster 100 includes a master node 101, a proxy node 102, and a standby master node 103. The master node 101 is responsible for coordinating and managing the collection and update of ARP information. The master node 101 sends an ARP information collection request to each proxy node 102, collects the ARP information of the proxy node 102, and updates the main ARP database to ensure the timeliness and consistency of the data. Subsequently, the master node 101 sends the updated ARP information to each proxy node 102 to synchronize its ARP information and avoid communication problems caused by outdated information.

[0080] After receiving the ARP information collection request from the master node, each proxy node 102 will obtain local ARP information from the proxy node and return it to the master node, ensuring that the master node can obtain the latest proxy node information.

[0081] It should be noted here that the local ARP information obtained from the proxy node and the ARP information in the proxy database of the proxy node mentioned below are different concepts. Local ARP information refers to the dynamic ARP information generated in real time in the current operating environment of the proxy node, such as the ARP table data cached in the network interface in use, which may change dynamically with changes in the network environment. The ARP information in the proxy database refers to the static ARP information stored by the proxy node after being updated by the ARP information sent by the master node, which is usually used to ensure consistency with the master database of the master node.

[0082] In addition, it should be noted that the present application does not impose any specific restrictions on the number of master nodes and proxy nodes in the cluster.

[0083] In an embodiment of the present application, the master node is implemented by deploying a master node program (such as a Master program) on a specific node. The master node can be deployed on a management node or a control node to undertake the coordination and management tasks of the entire cluster ARP information. The master node is responsible for sending ARP information collection requests to the proxy node, updating the main database, and sending the updated ARP information to each proxy node to ensure the consistency and accuracy of the ARP information of the entire cluster. The number of master nodes can be one or more, but not all nodes need to be master nodes. Generally, the master node is deployed in a master-slave mode to ensure high availability of the service. When a master node fails, the master-slave switching mechanism can be used to ensure that the service is not interrupted, further improving the reliability of the system.

[0084] In an optional implementation, in order to ensure high availability, the present application provides a master-standby mechanism for the master node. A standby master node 103 is deployed next to the master node 102. The standby master node serves as a backup node for the master node. Once the master node fails or fails to operate normally, the standby master node can take over the tasks of the master node through the master-standby switching mechanism to ensure the continuity of the service and the normal synchronization of the cluster ARP information. Real-time status monitoring and data synchronization will be performed between the standby master node and the master node to ensure a smooth transition of the master-standby switching process. The present application does not impose specific restrictions on the number of master nodes and standby master nodes, and one or more master nodes and standby master nodes can be configured according to actual needs. For example, in a small cluster, only one master node and two standby master nodes can be deployed, while in a large-scale cluster with high reliability requirements, three master nodes and three standby master nodes can be deployed.

[0085] In the embodiment of the present application, the proxy node is responsible for receiving the ARP information in the master database of the master node, updating the proxy database, and feeding back the changed local ARP information to the master node when necessary. The number of proxy nodes is determined according to the specific number of working nodes in the cluster.

[0086] Optionally, the proxy node is not an independent entity, but is implemented by deploying a proxy program (e.g., Agent) on a working node (e.g., computing node, storage node, etc.) in the cluster. Therefore, the proxy node is a working node with an agent program deployed. In other words, the working node in the cluster becomes a proxy node by running the agent program, and cooperates with the master node to complete the ARP information processing task.

[0087] This deployment method makes the number of proxy nodes directly related to the number of working nodes in the cluster. As the cluster scales, the number of working nodes such as computing nodes and storage nodes increases, and the number of proxy nodes will also increase accordingly. It should be noted that working nodes refer to nodes that undertake actual computing, storage and other tasks, and the proxy program is deployed on these working nodes as a software component, giving them the function of proxy nodes.

[0088] In an optional implementation, the master node 110 and the proxy node 120 may communicate with each other via a communication network.

[0089] In an optional implementation, the communication network is a wired network or a wireless network.

[0090] In an optional implementation, the master node and the proxy node communicate via HyperText Transfer Protocol (HTTP) messages. The master node sends an ARP information collection request to the proxy node using an HTTP request, and the proxy node returns its ARP information via an HTTP response. HTTP requests typically use the GET or POST methods, where GET is used to request ARP information and POST is used to submit ARP information. Each request and response contains relevant header information and data content, such as the content type Content-Type and the actual ARP data. In this way, the master node and the proxy node can efficiently exchange ARP information to ensure timely updating and synchronization of ARP information.

[0091] It should be noted that Figure 1 The figure is only an example. In fact, the number of master nodes and proxy nodes is not limited and is not specifically limited in the embodiments of the present application.

[0092] The following describes the ARP information processing method provided by the exemplary embodiment of the present application in combination with the application scenario described above and with reference to the accompanying drawings. It should be noted that the above application scenario is only shown to facilitate understanding of the spirit and principles of the present application, and the implementation of the present application is not limited in this respect.

[0093] See also Figure 2As shown, it is an implementation flow chart of an ARP information processing method provided in an embodiment of the present application, which is applied to the master node in the cluster. The specific implementation process of the method is as follows:

[0094] S21: After the preset collection conditions are met, an ARP information collection request is sent to each proxy node in the cluster to obtain the ARP information of each proxy node.

[0095] In the embodiment of the present application, ARP information includes but is not limited to: IP address, MAC address, and network card name. Among them: IP address is the network identifier of each proxy node, which is used for data packet addressing; MAC address is the physical address associated with the IP address, which is the unique identifier used by the data link layer to locate the network device; network card name refers to the name of the network interface used by the proxy node, which helps to distinguish the ARP information of multiple network interfaces.

[0096] Optionally, the collection condition includes at least one of the following: timed collection, in response to a collection request of the object.

[0097] Among them, scheduled collection means that the master node sends ARP information collection requests to the proxy node regularly according to a preset time interval. The time interval can be set according to one or more of the cluster scale, network status, ARP information change frequency or business needs. For example, the master node can send collection requests regularly every day, every hour or according to other business needs to ensure that the ARP information remains real-time and accurate and avoids outdated information. Scheduled collection is suitable for a stable network environment to ensure that the ARP table of each node is updated synchronously.

[0098] Responding to the collection request of the object means that in addition to the scheduled collection, the master node can also respond to the collection request of the object (such as the user, which can be the operation and maintenance personnel). In actual applications, users can actively trigger the collection request to collect ARP information under specific circumstances. For example, when the network is abnormal, the operation and maintenance personnel can manually trigger the ARP information collection to quickly diagnose the network failure; or when system maintenance, configuration changes or optimization are required, users can actively initiate the collection of ARP information to ensure the accuracy and timeliness of the information. In addition, this responsive collection request mechanism can help the operation and maintenance personnel quickly obtain the ARP information of the proxy nodes in the cluster without waiting for the scheduled tasks, thereby improving the efficiency of network troubleshooting and maintenance.

[0099] In the embodiment of the present application, when the proxy node receives the ARP information collection request sent by the master node, the proxy node program deployed on the working node extracts the local ARP information from the current running state of the working node, including its IP address, MAC address, network card name, etc., and returns this information to the master node through the communication network after packaging it in a predetermined format. This processing process of the proxy node ensures that the master node can quickly obtain the latest proxy node ARP information, which is convenient for further analysis by the master node.

[0100] S22: Update the master database corresponding to the master node according to the acquired ARP information.

[0101] In the embodiment of the present application, after the master node collects the ARP information from each proxy node, it aggregates and updates the information to the master database (i.e., the ARP database of the master node), ensuring that the ARP information in the master database is the latest and that all ARP information remains consistent. In this way, the master node can manage the ARP information of the entire cluster and ensure that real-time and accurate ARP information is used in network communications.

[0102] S23: Send the updated ARP information in the main database to each proxy node respectively, so that each proxy node updates the proxy database corresponding to the proxy node according to the ARP information in the main database.

[0103] In the embodiment of the present application, for each proxy node, after receiving the updated ARP information in the main database, the proxy node needs to update its corresponding proxy database (ie, the ARP database of the proxy node) according to the ARP information in the main database.

[0104] See also Figure 3 As shown, it is a schematic diagram of a process of ARP information collection provided by an embodiment of the present application. Figure 3 As shown, it mainly includes the following steps:

[0105] S31: Sending an ARP information collection request to the proxy node.

[0106] The master node sends an ARP information collection request to each proxy node in the cluster according to a preset collection condition (eg, timed collection or in response to a user request) to trigger the proxy node to collect and report its local ARP information.

[0107] S32A, S32B: collect local ARP information.

[0108] Proxy node A and proxy node B receive the collection request from the master node respectively and collect their local ARP information. The local ARP information includes but is not limited to the IP address, MAC address and network card name. The proxy node collects the ARP information during operation from the working node corresponding to its current proxy node.

[0109] It should be noted here that proxy node A and proxy node B are just examples. The proxy nodes in other clusters are not shown in the figure, but they will also respond to the collection request of the master node and collect local ARP information in the above manner.

[0110] S33A, S33B: Send local ARP information.

[0111] Each proxy node in the cluster returns the collected local ARP information to the master node. For example, proxy node A and proxy node B send local ARP information to the master node through HTTP response for subsequent processing by the master node.

[0112] S34: Update the received ARP information to the main database.

[0113] After receiving the ARP information returned by all proxy nodes, the master node summarizes and updates it to the master database. The master node adds, modifies, or deletes the master database based on the received information to ensure that the ARP information in the master database is always up-to-date, accurate, and complete.

[0114] S35: Send the updated ARP information in the main database to the proxy node.

[0115] The master node sends the updated ARP information in the master database to the proxy node. Based on the master database, the master node sends the updated ARP information to each proxy node in the cluster to ensure the synchronization of ARP information within the cluster.

[0116] S36A, S36B: Update the proxy database according to the ARP information in the received master data.

[0117] After receiving the ARP information sent by the master node, the proxy node A and the proxy node B update their respective proxy databases according to the latest ARP information in the master database. The proxy node compares and operates the local proxy database based on the received information, such as adding new records, updating inconsistent records, and clearing outdated records to ensure that the local proxy database is consistent with the master database.

[0118] S37: Update completed.

[0119] After the update is completed, the process of the master node in the entire cluster collecting ARP information from the proxy node is completed, and the ARP information of the master node and the proxy node is synchronized and updated in real time.

[0120] It should be noted that steps S31, S34, and S35 are operations on the master node side, mainly involving the sending of ARP information collection requests, receiving and processing, updating of the master database, and distribution of updated information; while steps S32, S33, and S36 are operations on the proxy node side, including receiving collection requests, reporting local ARP information, and synchronizing the proxy database according to the updated information sent by the master node. The two coordinate to achieve efficient collection and synchronous update of cluster ARP information.

[0121] Through the above process, the master node can not only efficiently manage the ARP information of all proxy nodes in the cluster, but also realize real-time synchronization and update of ARP information within the entire cluster, effectively avoiding network communication problems caused by outdated or inconsistent ARP information, while improving the stability and communication efficiency of the cluster network.

[0122] In the process of sending updated ARP information from the master node to each proxy node, when the cluster is large and the number of nodes is too large, the master node needs to send update messages to a large number of proxy nodes at the same time, which will cause the communication load of the master node to be too high, thereby affecting its processing performance. Therefore, in order to improve the communication efficiency during ARP information processing and reduce the load of the master node, in an optional implementation, a grouping and relay mechanism is introduced. Through a preset node number threshold, if the number of nodes in the current cluster exceeds the preset node number threshold, it is confirmed to start the relay forwarding mode.

[0123] Optionally, the proxy nodes are grouped according to their IP addresses, and one proxy node is selected from each group of proxy nodes as a relay node;

[0124] The updated ARP information in the database is sent to the relay node, so that the ARP information in the database is forwarded to other proxy nodes in the same group through the relay node.

[0125] In an optional implementation, in order to improve the communication efficiency between the master node and the proxy node, especially in a large-scale cluster scenario, the master node can reduce the number of direct communications with all proxy nodes by introducing a grouping and relay mechanism. Specifically, the master node first divides the proxy nodes into several groups according to the IP addresses or other grouping rules of each proxy node, and selects a proxy node in each group as a relay node. The ARP information in the updated database is first sent to the relay node, which forwards the information to other proxy nodes in the same group, thereby completing the ARP information synchronization of the proxy nodes in the group.

[0126] Among them, the relay node refers to the proxy node selected in each group of proxy nodes to receive the ARP information sent by the master node and forward it to other proxy nodes in the same group. The selection of relay nodes is usually based on its network connection status, computing resource load and other conditions. The proxy node in the same group refers to the proxy node that is divided into the same group with a relay node during the grouping process.

[0127] In an embodiment of the present application, the master node groups the proxy nodes according to the grouping rules of the proxy nodes, and the grouping rules include but are not limited to: division by geographical location and division by P address segment.

[0128] In each group, the master node selects a proxy node as a relay node. The master node sends the updated ARP information to the relay nodes of each group, and the relay nodes are responsible for forwarding the ARP information to other proxy nodes in the same group.

[0129] For example, in a cluster containing 50 proxy nodes, the master node can divide them into 5 groups, each containing 10 proxy nodes, and each group selects a relay node. The master node only needs to send updated ARP information to the 5 relay nodes, without directly communicating with all proxy nodes, reducing the communication pressure on the master node.

[0130] The above description is based on the example that the number of proxy nodes contained in each group is the same. In addition, it should be noted that the number of proxy nodes contained in each group may also vary according to the actual situation. The specific division can be flexibly adjusted according to one or more of the preset grouping rules, the network load of the proxy node, the IP address range, the geographical location or other related factors. The specific implementation method may vary depending on the application scenario, and this article will not go into details one by one.

[0131] In order to further ensure the integrity and reliability of ARP information synchronization, in an optional implementation, the present application also provides a failed task retry mechanism, which can effectively handle abnormal situations in the process of the master node sending ARP information, ensuring the final completion of the task and the synchronous update of ARP information.

[0132] Optionally, when sending ARP information to any proxy node, if a task that fails to send is detected, the task is added to the retry task queue;

[0133] According to the first duration, the tasks in the retry task queue are periodically triggered to resend the ARP information corresponding to the tasks.

[0134] Specifically, when the master node sends ARP information to any proxy node, if it detects that the task is unsuccessful during the sending process (such as network failure, node unreachable or other abnormal conditions), the master node will not terminate the operation immediately, but record the task and add it to the retry task queue.

[0135] The master node will trigger the tasks in the retry task queue according to the preset first duration, and try to resend the ARP information corresponding to the failed task. Through this mechanism, even if the initial transmission fails, the master node can still complete the task through multiple attempts, thereby ensuring the final delivery and synchronization of the ARP information.

[0136] In an optional implementation, the master node needs to send the updated ARP information to the proxy node. When the master node sends the ARP information to a proxy node, it is detected that the sending fails due to a network failure or node unreachability. The master node will not directly abandon the task, but will record the sending task and add it to the retry task queue. The master node regularly triggers the task in the retry task queue according to the preset first duration (e.g., 30 seconds) and tries to send the ARP information again.

[0137] When the next retry is triggered, the master node tries to send the ARP information to the proxy node again. If the network failure has been restored and the transmission is successful, the proxy node updates the ARP information in its proxy database based on the received ARP information, thereby completing the information synchronization. If the retry task fails again, the master node will continue to keep the task in the queue and try to send it again when the next retry is triggered until the task is successfully completed or the preset maximum number of retries is reached.

[0138] Through this mechanism, even if the initial transmission fails, the master node can still ensure the final delivery of the ARP information, avoiding information loss due to temporary network problems or other abnormalities, and further ensuring the synchronization and consistency of ARP information within the cluster.

[0139] In the method provided in the present application, the master node can not only send ARP information collection requests to the proxy nodes in the cluster to obtain the latest ARP information, but also receive requests sent by the proxy nodes to realize the configuration and synchronization of ARP information.

[0140] Optionally, the master node may also receive an ARP information configuration request sent by a first proxy node in the cluster; the ARP information configuration is sent by the first proxy node after determining that the corresponding proxy database is not configured with ARP information;

[0141] According to the ARP information configuration request, the ARP information of each proxy node in the main database is queried, and the ARP information of each proxy node is sent to the first proxy node, so that the first proxy node configures the proxy database corresponding to the first proxy node according to the ARP information of each proxy node.

[0142] In an optional implementation, the master node and the proxy node may also communicate via an ARP information configuration request, to ensure that when the proxy node is not configured with ARP information, information synchronization is performed via the master node.

[0143] Among them, the ARP information configuration request can be a request triggered by an event, or a request triggered by a timing; event triggering includes but is not limited to being triggered when the proxy node newly joins the cluster, or being triggered after the proxy node is restarted, or being triggered by the proxy node when the network is restarted; timing-triggered requests include being triggered when it is detected that the proxy node is not configured with ARP information within a preset second time period. The specific triggering mechanism of the ARP information configuration request will be specifically introduced on the proxy node side below, and will not be repeated here.

[0144] In the embodiment of the present application, not configuring ARP information means that the ARP information in the proxy database of the proxy node is empty. The first proxy node refers to a proxy node that detects that its proxy database is not configured with ARP information and sends an ARP information configuration request to the master node.

[0145] In an embodiment of the present application, the master node receives an ARP information configuration request from the first proxy node in the cluster, and the trigger condition of the request is that the proxy node detects that the ARP information in its proxy database is not configured (that is, the ARP information is empty). At this time, the first proxy node, as a specific triggering node, initiates a configuration request to the master node so as to synchronize the ARP information of other proxy nodes through the master node. Specifically, after receiving the ARP information configuration request, the master node will query the master database, obtain the ARP information of other proxy nodes, and return this information to the requesting first proxy node.

[0146] It should be noted here that the first proxy node is a proxy node when it is determined that its corresponding proxy database is not configured with ARP information. This is just a trigger node for facilitating management and processing of specific situations. In essence, the first proxy node is still an ordinary proxy node in the cluster.

[0147] The master node can not only receive ARP information configuration requests sent by the proxy node, but also receive ARP information change messages sent by the proxy node, which is used to update and synchronize the ARP information in the cluster in real time.

[0148] Optionally, the master node receives an ARP information change message sent by a second proxy node in the cluster; the ARP information change message includes: updated ARP information corresponding to the second proxy node;

[0149] Update the main database according to the updated ARP information, and query the third proxy node related to the second proxy node;

[0150] The second proxy node and the third proxy node are notified to update the corresponding proxy database according to the updated ARP information.

[0151] In an optional implementation, the master node and the proxy node may also communicate via ARP information change messages to ensure that when the ARP information of the proxy node changes, the master node can synchronize and coordinate the update of the relevant proxy nodes in a timely manner.

[0152] Among them, the ARP information change message is a message actively sent by the second proxy node after detecting that its own ARP information has been updated, and is used to inform the main node of the changed ARP information. The second proxy node is a node whose ARP information has changed, for example, the ARP information is updated due to a change in the node's IP address or MAC address. The third proxy node is a related proxy node that has a communication or interaction relationship with the second proxy node, and it needs to update its own proxy database according to the changed ARP information of the second proxy node to maintain the consistency and reliability of network communication. The specific triggering mechanism of the ARP information change message will be specifically introduced on the proxy node side below, and will not be repeated here.

[0153] In the embodiment of the present application, after the second proxy node finds that its own ARP information has changed, it will send the updated ARP information to the master node through an ARP information change message. After receiving the message, the master node first updates the ARP information in the master database to record the latest proxy node ARP data; then, the master node finds the third proxy node that has a communication relationship with the second proxy node through query, and sends an update notification to these related third proxy nodes, so that they synchronize their own proxy databases according to the updated ARP information. At the same time, the master node will also notify the second proxy node to confirm that its ARP information has been synchronized and updated and update its corresponding proxy database.

[0154] Through the above process, the master node can efficiently manage and synchronize the ARP information in the cluster, ensuring that when the ARP information of the proxy node changes, the master node records and updates it in time, and coordinates the proxy databases corresponding to the changed proxy nodes and related proxy nodes to synchronize and update them.

[0155] In an optional implementation, the master node not only receives ARP information configuration requests and ARP information change messages from the proxy nodes, but also receives other related messages sent by each proxy node in the cluster, such as confirmation messages for completion of proxy node configuration, error report messages for configuration failures, etc. Since the master node needs to process a large number of messages from multiple proxy nodes, in order to ensure the efficiency and accuracy of message processing, it is necessary to process these received messages to avoid duplication or omission, thereby ensuring smooth synchronization and updating of ARP information.

[0156] Optionally, the master node performs at least one of the following processing operations on the received ARP information:

[0157] Processing operation 1: deduplicate the ARP information sent by the same proxy node.

[0158] In an optional implementation, when a proxy node sends the same ARP information to the master node multiple times due to network jitter or other reasons, the master node will compare the content of the ARP information from the same proxy node. If it finds messages with completely identical content, it will only retain the latest message and discard the remaining duplicate messages. For example, if the proxy node continuously sends multiple ARP messages with the content of "IP = 192.168.1.1, MAC = 00:11:22:33:44:55", the master node will only retain one of them for processing to avoid resource waste and processing delays caused by duplicate data.

[0159] Processing operation 2: For the same type of ARP information sent by different proxy nodes, merge the same type of ARP information into one ARP information.

[0160] In an optional implementation, when the ARP information sent by multiple proxy nodes contains records of the same type (such as the same target IP address, but from different proxy nodes), the master node will merge these ARP information of the same type into a unified record. For example, proxy node A sends "IP = 192.168.1.1, MAC = 00:11:22:33:44:55", and proxy node B sends "IP = 192.168.1.1, MAC = 00:11:22:33:44:55". The master node merges these two ARP information with the same content into one to reduce the storage and processing of redundant information.

[0161] Processing operation three: discard the ARP information in the message queue that exceeds the preset threshold length.

[0162] In an optional implementation, the message queue maintained by the master node has a preset capacity limit (for example, a preset threshold length of 100). When the number of ARP messages received exceeds the preset threshold length upper limit, the master node will discard messages exceeding the threshold length. For example, when the message queue has stored 100 messages and a new ARP message arrives, the master node will directly discard the excess messages and no longer enter the queue. By controlling the length of the message queue, excessive memory usage or processing delays can be prevented.

[0163] Processing operation four: sort different ARP information according to priority and process them in sequence.

[0164] In an optional implementation, after receiving different types of ARP information, the master node will prioritize them according to the task type or importance of the message. For example, a changing ARP message may affect real-time network communication, so it has the highest priority and the master node will process it first; unconfigured ARP information is a message that the proxy node requests configuration, which requires a timely response and has the second highest priority; ARP information collected at regular intervals usually does not change and has the lowest priority. Through this sorting mechanism, the master node can reasonably schedule resources, ensure that high-priority tasks are processed first, and ensure the timeliness and stability of network communication.

[0165] See also Figure 4 As shown, it is a schematic diagram of a master node ARP information processing method provided in an embodiment of the present application.

[0166] like Figure 4 As shown, after receiving the ARP information sent by the proxy node, the master node can perform one or more of the following processing operations on it as needed: deduplication (corresponding to processing operation 1), aggregation (corresponding to processing operation 2), flow control (corresponding to processing operation 3) and sorting (corresponding to processing operation 4). These processing operations can be performed independently or in combination to meet the ARP information management needs in different scenarios.

[0167] The above process mainly introduces the process of the master node sending an ARP information collection request, the master node receiving the ARP configuration request and ARP information change message from the proxy node, and the master node processing the received ARP information. The following will introduce the process of the proxy node receiving the ARP information collection request sent by the master node:

[0168] See also Figure 5 As shown, it is an implementation flow chart of another ARP information processing method provided in an embodiment of the present application, which is applied to a proxy node in a cluster. The specific implementation process of the method is as follows:

[0169] S51: After receiving the ARP information collection request sent by the master node in the cluster, obtain the ARP information of the proxy node and send it to the master node, so that the master node updates the master database corresponding to the master node according to the obtained ARP information, and sends the updated ARP information in the master database to the proxy nodes respectively.

[0170] The ARP information collection request is sent by the master node after at least one of the following preset collection conditions is met: timed collection, in response to a collection request of the object.

[0171] It should be noted here that the ARP information collection request has been specifically introduced on the master node side, and this application will not repeat it.

[0172] In the embodiment of the present application, taking a certain proxy node as an example, after receiving the scheduled ARP information collection request sent by the master node, the proxy node extracts the local ARP information it is running, including its IP address (such as 192.168.1.10), MAC address (such as 00:1A:2B:3C:4D:5E) and network card name (such as eth0). The proxy node encapsulates this information in a predetermined format and sends it to the master node. After the master node collects the information of all proxy nodes, it updates the master database to ensure that the ARP information in the master database is comprehensive and accurate.

[0173] S52: After receiving the ARP information in the main database sent by the master node, the corresponding proxy database is updated according to the ARP information.

[0174] In an optional implementation, for the proxy node, when all the records of ARP information in the proxy database and the received ARP information in the main database are the same, the proxy node will not make any modifications and retain the existing records; when a certain record of ARP information in the proxy database and the received ARP information in the main database is inconsistent (for example, the MAC address corresponding to the IP address changes), the proxy node will update the ARP information record in the proxy database to the ARP information in the main database; for records that exist in the proxy database but do not exist in the received ARP information in the main database (i.e., redundant or outdated records), the proxy node will delete these records to ensure that the ARP information in the proxy database is consistent with that in the main database.

[0175] In an embodiment of the present application, during the update process, the proxy node receives the ARP information in the main database sent by the master node, which contains the complete ARP record of the network to which the proxy node belongs. For example, the ARP information sent by the master node includes the IP-MAC mapping records of other proxy nodes. The proxy node compares its proxy database and finds that some records are inconsistent, and then updates the proxy database according to the latest information sent by the master node. For example, if the ARP information sent by the master node contains the MAC address corresponding to the IP address 192.168.1.20 as 00:1A:2B:3C:4D:5F, and the proxy database record is 00:1A:2B:3C:4D:5E, the proxy node will be modified to 00:1A:2B:3C:4D:5F. In addition, if there are some outdated records stored locally in the ARP information sent by the master node, such as the IP record of 192.168.1.30, the proxy node will automatically clean up these redundant information to ensure that the ARP information in the proxy database is consistent with the main database.

[0176] Through the above process, the proxy node can send the local ARP information to the master node in time after receiving the ARP information collection request sent by the master node, ensuring that the master node can fully grasp the ARP information of all proxy nodes in the cluster. At the same time, when the proxy node receives the updated ARP information from the master node, it ensures that the ARP information in the proxy database is consistent with the ARP information in the master database through operations such as comparison, update, and cleanup, thereby effectively improving the real-time, accuracy, and consistency of the ARP information in the cluster, and avoiding network communication problems caused by outdated or erroneous ARP information.

[0177] The above mainly introduces that the proxy node can send the local ARP information to the master node in time after receiving the ARP information collection request sent by the master node. The proxy node can also actively initiate a request to the master node to ensure the integrity and accuracy of its own proxy database.

[0178] Optionally, after determining that the corresponding proxy database is not configured with ARP information, an ARP information configuration request is sent to the master node, so that the master node queries and returns the ARP information of each proxy node in the master database according to the ARP information configuration request;

[0179] Configure the corresponding proxy database according to the ARP information of each proxy node.

[0180] When the proxy node finds that the ARP information in its proxy database is not configured, it actively sends a configuration request to the master node, and then configures the proxy database of the proxy node that is not configured with ARP information through the ARP information of each proxy node sent by the master node.

[0181] In the embodiment of the present application, the ARP information configuration request may be a request triggered by an event or a request triggered by a timing.

[0182] Event triggers include but are not limited to those triggered when a proxy node newly joins a cluster, when a proxy node is restarted, or when a network is restarted.

[0183] When a new proxy node is added to the cluster, its proxy database has not yet been configured with ARP information (the initial ARP information in the proxy database is 0), so the newly added proxy node will actively send an ARP information configuration request so that the master node can send the ARP information in the master database to it for configuration. This is to ensure that the new node can quickly complete the initialization of ARP information and join the cluster's network communication.

[0184] When a proxy node is restarted due to a failure, maintenance, or other reasons, the ARP information in its local proxy database may disappear (for example, the data in the memory fails to persist). At this time, the proxy node detects that the ARP information is not configured, and actively sends a configuration request to the master node to resynchronize the ARP information in the master database to ensure the normal recovery of its network communication.

[0185] If the cluster's network service is restarted due to an exception or maintenance, the proxy node's network stack may be reinitialized, which may cause the loss of ARP information. When the proxy node detects this situation, it will also send an ARP information configuration request to the master node through an event trigger mechanism to ensure that the ARP information is synchronized and complete after the network service is restored.

[0186] The proxy node will periodically check the local proxy database to determine whether its ARP information has been configured. If it detects that the ARP information is not configured, the proxy node will actively send a configuration request to the master node to obtain and update the local proxy database.

[0187] Optionally, if it is determined through a periodic check that the ARP information is not configured, then a periodic check is performed according to a second time period to determine whether the corresponding proxy database is configured with the ARP information; and,

[0188] If the proxy database configuration fails, the second duration is reduced;

[0189] If the proxy database is configured successfully, the second duration is increased.

[0190] The second duration refers to the time interval for the proxy node to check whether the ARP information is configured in its own proxy database. Specifically, the proxy node will periodically check the proxy node according to the second duration. If it is found during the check that the proxy node's proxy database does not have ARP information configured, it will initiate a request to the master node to try to configure it.

[0191] In an optional implementation, the timing trigger mechanism is introduced to deal with some special scenarios, such as the event trigger mechanism may not be executed in time for some reason, or the proxy node loses ARP information during operation but cannot be perceived through events. Through the timing trigger method, the proxy node can actively check its own ARP information configuration status at a certain frequency to ensure that even if the event is not triggered, the ARP information can still be restored and synchronized within a reasonable time range, thereby further improving the reliability and timeliness of the proxy node ARP information configuration.

[0192] If the configuration request fails (for example, due to network problems that prevent the master node from connecting or configuration errors), the proxy node will shorten the second time period to speed up the subsequent check cycle and detect and retry the configuration as soon as possible. This is to deal with configuration failures and ensure that the ARP information is configured into the proxy database of the proxy node as soon as possible.

[0193] In an embodiment of the present application, when the proxy database configuration fails, the proxy node can reduce the second duration. In an optional implementation, the proxy node can reduce the second duration in fixed steps, for example, by 10 seconds each time, until the second duration reaches the minimum value set by the system (such as 10 seconds); in another optional implementation, the proxy node can also directly set the second duration to a fixed smaller value, such as 20 seconds, so as to quickly enter the next round of inspection process; in another optional implementation, the proxy node can adopt a proportional reduction method, taking the current second duration as the benchmark, and reduce it to 50% of the original, for example, if the current second duration is 60 seconds, it will be reduced to 30 seconds after the configuration fails, so as to flexibly adjust the inspection frequency.

[0194] If the configuration is successful, it means that the ARP information of the proxy node has been correctly configured and synchronized to the proxy database. In this case, the proxy node is unlikely to be unconfigured again in a short period of time. Therefore, the second time period will be increased and the time interval for the next check will be extended, thereby reducing unnecessary frequent checks and improving efficiency.

[0195] In an embodiment of the present application, when the proxy database is successfully configured, the proxy node will increase the second duration in order to reduce the system load. In an optional implementation, a fixed step increase method can be used, such as increasing by 30 seconds each time the configuration is successful, until the second duration reaches the set maximum value (such as 30 minutes); in another optional implementation, the second duration can also be directly set to a fixed larger value, such as 5 minutes, to reduce the frequency of inspections; in another optional implementation, a proportional increase method can also be used, with the current second duration as the benchmark, and adjusted to 150% of the original, for example, the current second duration is 2 minutes, and after the configuration is successful, it is adjusted to 3 minutes, thereby dynamically optimizing the inspection interval.

[0196] See also Figure 6 As shown, it is a schematic diagram of a processing of proxy node ARP information configuration provided by an embodiment of the present application. Figure 6 As shown, the whole process includes the following steps:

[0197] S61: Check whether the proxy database is configured with ARP information.

[0198] The proxy node checks its local proxy database to determine whether there is any configured ARP information. If the ARP information in the proxy database is empty (i.e., no ARP information is configured), the proxy node triggers the subsequent ARP information configuration process. It should be noted here that the proxy node confirms whether the proxy database is configured with ARP information through the event triggering and timing triggering described above, which has been specifically introduced in the above process and will not be repeated here.

[0199] S62: If it is found that no ARP information is configured in the proxy database, the following steps S63 to S67 are executed:

[0200] If it is found that the proxy database is not configured with ARP information, the proxy node will enter the active configuration request process to ensure that its proxy database can obtain the latest ARP information in a timely manner.

[0201] S63: Send an ARP information configuration request.

[0202] The proxy node sends an ARP information configuration request to the master node, informing the master node that no ARP information is currently configured in the proxy database. The ARP information configuration request usually includes the identification information of the proxy node so that the master node can query and issue data for the proxy node.

[0203] S64: Query the ARP information of all proxy nodes in the main database.

[0204] After receiving the ARP information configuration request from the proxy node, the master node will query the ARP information of all proxy nodes stored in the master database, extract the complete ARP information data, and send it to the requesting proxy node. This operation ensures that the data sent by the master node is the latest and can meet the proxy node's needs for ARP information.

[0205] S65: Send the ARP information of all proxy nodes in the main database.

[0206] The master node sends the complete ARP information to the proxy node that issued the configuration request, ensuring that the proxy node can obtain the ARP information of all proxy nodes in the cluster so as to update its local proxy database.

[0207] S66: Configure the proxy database according to the received ARP information of all proxy nodes.

[0208] After receiving the ARP information sent by the master node, the proxy node will configure the proxy database according to the information to ensure that the proxy database is consistent with the master database.

[0209] S67: Configuration completed.

[0210] After the proxy node completes the ARP information configuration, the entire process ends. At this point, the proxy database of the proxy node is synchronized with the ARP information in the main database, and the proxy node can normally participate in the network communication within the cluster.

[0211] Through the above steps, when the proxy node finds that the proxy database is not configured with ARP information, it can actively interact with the master node to obtain and configure complete ARP information, thereby ensuring the normal communication function of the proxy node in the cluster and ensuring the consistency and reliability of the ARP information in the cluster.

[0212] The above mainly introduces the operation of the proxy node when it detects that its proxy database is not configured with ARP information. The proxy node can also actively notify the master node when it detects that its ARP information has changed, triggering the relevant update process. The following will introduce it in detail.

[0213] Optionally, after determining that its own ARP information has changed, the proxy node sends updated ARP information to the master node through an ARP information change message, so that the master node updates the master database according to the updated ARP information, and notifies the relevant proxy nodes to update the corresponding proxy database according to the updated ARP information;

[0214] According to the updated ARP information, the corresponding proxy database is updated.

[0215] In the embodiment of the present application, when the proxy node determines that its own ARP information has changed, it will actively send the updated ARP information to the master node through an ARP information change message. After receiving the message, the master node updates the master database according to the updated ARP information, and notifies the relevant proxy nodes to update their respective proxy databases according to the latest ARP information. At the same time, the proxy node will also update its own proxy database according to the updated ARP information.

[0216] In an optional implementation, the scenarios in which the ARP information of the proxy node may change include but are not limited to the following: First, the MAC address may change after the node is restarted. This is because the network configuration of some nodes dynamically generates ARP information, and the original MAC address may not be retained after the restart, resulting in changes in ARP information; second, the restart of the network service or driver may cause the ARP information to change. For example, the restart of the network service will cause the ARP table to be reloaded or cleared, and then the relevant ARP information needs to be regenerated; third, replacing the network card device will cause the MAC address to change, because the new network card has a different physical MAC address, which is inconsistent with the original configuration; fourth, the IP address change may cause the ARP information to change, for example, when the network administrator or system modifies the IP address of a node through the configuration tool, the original IP-MAC correspondence will be updated; fifth, ARP conflicts or ARP table timeouts in the network may also trigger changes in ARP information. For example, when two devices try to use the same IP address, the ARP information needs to be updated to resolve the conflict.

[0217] Optionally, the proxy node periodically collects the local ARP information of the node through a preset third time period, and compares it with the previous ARP information recorded in its corresponding proxy database. Through the comparison result, a judgment result of whether the ARP information of the proxy node has changed is obtained. The judgment results of all proxy nodes in the cluster are collected. If there is a proxy node whose ARP information has changed, the above-mentioned ARP information change message is used to actively send the updated ARP information to the master node. Among them, the configuration of the third time period should ensure that the ARP information changes of the proxy node can be discovered in time and synchronized to the master node.

[0218] In an optional implementation, the third duration can be set to a time range from seconds to minutes, such as 10 seconds, 30 seconds or 1 minute. The specific configuration period can be adjusted according to the dynamics of the network environment and the frequency of ARP information updates. In a more dynamic network environment, the third duration can be set to a shorter period (such as 10 seconds) to increase the frequency of detection; while in a more stable network environment, the third duration can be set to a longer period (such as 1 minute) to reduce resource consumption.

[0219] It should be noted here that the proxy node that sends the ARP information change message is the second proxy node mentioned on the master node side, which actively notifies the master node to trigger the subsequent update process; the relevant proxy node is the third proxy node mentioned above, and other proxy nodes that have an interactive relationship with the proxy node or rely on its ARP information have different names, but their roles and functions are consistent in different scenarios.

[0220] See also Figure 7 As shown, it is a schematic diagram of processing the change of the ARP information of a proxy node provided in an embodiment of the present application, which specifically includes the following steps:

[0221] S71: Collect local ARP information.

[0222] Agent node A collects the ARP information of the current runtime from its local environment, including IP address, MAC address, network card name, etc. This information will be used as the basis for comparison with the ARP information in the agent master database of the agent node.

[0223] S72: Compare the local ARP information with the ARP information of the proxy node in the proxy database.

[0224] The proxy node A compares the collected local ARP information with the ARP information of the proxy node A in its proxy database.

[0225] S73: If the local ARP information is inconsistent with the ARP information of the proxy node in the proxy database, the following steps S74 to S716 are executed.

[0226] If the local ARP information is consistent with the record in the proxy database, no processing is performed; if there is inconsistency, the subsequent change message sending process is triggered, that is, S74 to S716.

[0227] S74: Send an ARP information change message to the master node.

[0228] When the proxy node A finds that the ARP information has changed, it will actively send an ARP information change message to the master node, attach the updated ARP information to the message, and notify the master node to process it.

[0229] The proxy node A sends the ARP information change message to the master node through HTTP message or other communication methods, ensuring that the master node can receive the latest change information in time.

[0230] S75: Receive the updated ARP information of the proxy node A and update the main database.

[0231] After receiving the ARP information change message, the master node updates the master database according to the content of the updated ARP information to ensure that the ARP information in the master database reflects the latest network status.

[0232] S76: Put the message into the queue for asynchronous processing.

[0233] The master node will add the change messages to the message queue and gradually process these change messages through an asynchronous processing mechanism to ensure overall processing efficiency and stability.

[0234] S77: Message received.

[0235] While processing the message, the master node will send a confirmation message to the proxy node A, informing the proxy node A that the ARP information change message it sent has been successfully received by the master node. This operation prevents the proxy node A from sending messages repeatedly due to failure to receive confirmation.

[0236] S78: Query the nodes related to the proxy node A.

[0237] The master node determines the relevant proxy nodes (such as proxy node B) that are in communication with the proxy node A by querying the master database, so as to determine the scope of the proxy nodes that need to be synchronously updated.

[0238] S79: Send the updated ARP information of the proxy node A to the nodes related to the proxy node A.

[0239] The master node notifies the proxy node B of the updated ARP information from the proxy node A, and sends the updated ARP information to ensure that the proxy node B can synchronize its proxy database in time.

[0240] S710: According to the updated ARP information of the proxy node A, the proxy database of the related proxy node B is updated.

[0241] After receiving the update information sent by the master node, the proxy node B performs an update operation on B's proxy database according to the notification of the master node, including adding, modifying or deleting records.

[0242] S711: Update completed.

[0243] After the proxy node B completes the update of the ARP information, it achieves synchronization and consistency of the ARP information with the master node and other proxy nodes.

[0244] S712: Send the updated ARP information of the proxy node A to the proxy node A.

[0245] The master node returns the updated ARP information to the proxy node A, ensuring that the proxy database record of the proxy node A is consistent with the master database. This operation prevents the ARP information of the proxy node A from being deviated due to the update of the master database.

[0246] S713: Update the proxy database of proxy node A according to the updated ARP information.

[0247] The master node eventually updates the master database based on the confirmation information to ensure that the content of the master database is consistent with the status of all proxy nodes in the cluster.

[0248] S714: Update completed.

[0249] Proxy node A completes the update of ARP information.

[0250] S715: Receive information indicating that there is a proxy node that has not been successfully updated.

[0251] If the master node detects that some proxy nodes have failed to complete the update successfully (for example, due to network anomalies or node unavailability) when sending updated ARP information to proxy nodes (such as proxy node B), the master node will record the proxy node tasks that have not been successfully updated.

[0252] S716: Put the proxy node tasks that have not been successfully updated into a failure retry queue.

[0253] The master node will add these failed tasks to the failed retry queue and manage and process the tasks in the queue according to the retry mechanism. The specific mechanism and implementation of the failed retry queue refer to the introduction of the master node above, and this application will not repeat it here.

[0254] Through the above method, the proxy node can promptly notify the master node when the local ARP information changes, and trigger the master node to coordinate the update of related proxy nodes in the cluster, ensuring efficient synchronization of ARP information and stability of network communication in the cluster. This mechanism improves the collaboration between the proxy node and the master node, while reducing the communication risk caused by inconsistent ARP information.

[0255] In a large-scale cluster scenario, when there are a large number of proxy nodes, directly sending ARP information from the master node to all proxy nodes may cause the master node's communication load to be too high, increase the risk of message sending failure, and put a lot of pressure on the master node's performance. On the master node side, this application introduces a grouping and relay mechanism. The following will introduce the operation of the proxy node under the relay mechanism.

[0256] For the relay node, optionally, the ARP information is forwarded to other proxy nodes in the same group, so that the other proxy nodes update the corresponding proxy database according to the ARP information;

[0257] The proxy nodes in the same group are obtained by grouping the proxy nodes by the master node according to the IP addresses of the proxy nodes in the cluster, and the relay node in each group is a proxy node selected from the group.

[0258] In an optional implementation, while completing the update of its own proxy database, the relay node can also efficiently complete the ARP information synchronization task for other proxy nodes in the group, ensuring that the ARP information of all proxy nodes in the group is consistent, thereby further improving the communication efficiency of the cluster and the ARP information management capabilities.

[0259] In an embodiment of the present application, after the relay node receives the ARP information sent by the master node, it first updates its own proxy database according to the received ARP information, including adding, modifying or deleting ARP records in the proxy database to ensure that its own ARP information is consistent with the master node. After completing its own update, the relay node will forward the received ARP information to other proxy nodes in the same group. The specific operation is to send the ARP information to each proxy node in the same group in turn according to the grouping rules issued by the master node. After receiving the ARP information forwarded by the relay node, each proxy node in the same group will update its own proxy database according to the information. Still taking the above as an example, in a cluster containing 50 proxy nodes, the master node divides the proxy nodes into 5 groups according to the IP address range of the proxy nodes, each group contains 10 proxy nodes, and selects a proxy node with good network connection status and sufficient computing resources in each group as a relay node. The master node sends the updated ARP information to the relay nodes of each group, for example, to relay node A of group 1.

[0260] Subsequently, relay node A forwards the received ARP information to the other 9 proxy nodes in group 1 according to the grouping rules within the group. After receiving the ARP information, these proxy nodes will perform the update operation of the proxy database according to the content forwarded by the relay node to ensure that the ARP information of all nodes in the same group is consistent. Through this grouping and relay mechanism, the master node only needs to communicate directly with 5 relay nodes, instead of communicating with all 50 proxy nodes separately, which greatly reduces the communication pressure of the master node.

[0261] The design of this grouping and relay mechanism can optimize the communication efficiency between the master node and the proxy node in large-scale cluster scenarios, while ensuring that all proxy nodes can synchronize and update their ARP information in a timely and accurate manner, thereby improving the stability and management capabilities of the network.

[0262] Based on the same inventive concept, the embodiment of the present application also provides an ARP information processing device 800, which is applied to a master node in a cluster. Figure 8 As shown, it is a schematic diagram of the structure of the ARP information processing device 800, which may include:

[0263] The collection unit 801 is used to send an ARP information collection request to each proxy node in the cluster to obtain the ARP information of each proxy node after a preset collection condition is met; the collection condition includes at least one of the following: timed collection, in response to a collection request of an object;

[0264] A first updating unit 802 is used to update the master database corresponding to the master node according to each acquired ARP information;

[0265] The first sending unit 803 is used to send the updated ARP information in the main database to each of the proxy nodes, so that each proxy node updates the proxy database corresponding to the proxy node according to the ARP information in the main database.

[0266] Optionally, the ARP information processing device 800 further includes:

[0267] The configuration request processing unit 804 is used to receive an ARP information configuration request sent by the first proxy node in the cluster; the ARP information configuration is sent by the first proxy node after determining that the corresponding proxy database is not configured with ARP information;

[0268] According to the ARP information configuration request, the ARP information of each proxy node in the main database is queried, and the ARP information of each proxy node is sent to the first proxy node, so that the first proxy node configures the proxy database corresponding to the first proxy node according to the ARP information of each proxy node.

[0269] Optionally, the ARP information processing device 800 further includes:

[0270] The change message processing unit 805 is used to receive an ARP information change message sent by the second proxy node in the cluster; the ARP information change message includes: updated ARP information corresponding to the second proxy node;

[0271] updating the master database according to the updated ARP information, and querying a third proxy node related to the second proxy node;

[0272] Notify the second proxy node and the third proxy node to update corresponding proxy databases according to the updated ARP information.

[0273] Optionally, the ARP information processing device 800 further includes:

[0274] The retry unit 806 is used for adding the task to the retry task queue if it is detected that there is a task that fails to send when sending the ARP information to any of the proxy nodes;

[0275] According to the first duration, the tasks in the retry task queue are periodically triggered to resend the ARP information corresponding to the tasks.

[0276] Optionally, the ARP information processing device 800 further includes:

[0277] The processing unit 807 is configured to perform at least one of the following processing operations on the received ARP information:

[0278] De-duplicate the ARP information sent by the same proxy node;

[0279] For the same type of ARP information sent by different proxy nodes, the same type of ARP information is merged into one ARP information;

[0280] Discard the ARP information in the message queue that exceeds the preset threshold length;

[0281] Sort different ARP information by priority and process them in sequence.

[0282] Optionally, the first sending unit 803 is further configured to:

[0283] Grouping the proxy nodes according to their IP addresses, and selecting a proxy node in each group of proxy nodes as a relay node;

[0284] The updated ARP information in the database is sent to the relay node, so that the ARP information in the database is forwarded to other proxy nodes in the same group through the relay node.

[0285] Based on the same inventive concept, the embodiment of the present application also provides another ARP information processing device 900, which is applied to a proxy node in a cluster. Fig. 9 As shown, it is a schematic diagram of the structure of the ARP information processing device 900, which may include:

[0286] The second sending unit 901 is used to obtain the ARP information of the proxy node and send it to the master node after receiving the ARP information collection request sent by the master node in the cluster, so that the master node updates the master database corresponding to the master node according to the obtained ARP information, and sends the updated ARP information in the master database to the proxy node respectively; the ARP information collection request is sent by the master node after satisfying at least one of the following preset collection conditions: timed collection, in response to the collection request of the object;

[0287] The second updating unit 902 is configured to update the corresponding proxy database according to the ARP information received from the master node in the master database.

[0288] Optionally, the ARP information processing device 900 further includes:

[0289] A configuration request unit 903 is used to send an ARP information configuration request to the master node after determining that the corresponding proxy database is not configured with ARP information, so that the master node queries and returns the ARP information of each proxy node in the master database according to the ARP information configuration request;

[0290] According to the ARP information of each proxy node, a corresponding proxy database is configured.

[0291] Optionally, if it is determined through the periodic check that the ARP information is not configured, before determining that the ARP information is not configured, the configuration request unit 903 is further used to:

[0292] According to the second time period, periodically check whether the corresponding proxy database is configured with ARP information;

[0293] And, the configuration request unit 903 is further used for:

[0294] If the proxy database configuration fails, reducing the second time length;

[0295] If the proxy database is configured successfully, the second duration is increased.

[0296] Optionally, the ARP information processing device 900 further includes:

[0297] The change message sending unit 904 is used to send the updated ARP information to the master node through an ARP information change message after determining that its own ARP information has changed, so that the master node updates the master database according to the updated ARP information, and notifies the relevant proxy nodes to update the corresponding proxy database according to the updated ARP information;

[0298] According to the updated ARP information, the corresponding proxy database is updated.

[0299] Optionally, the proxy node is a relay node, and the ARP information processing device 900 further includes:

[0300] The relay forwarding unit 905 is used to forward the ARP information to other proxy nodes in the same group, so that the other proxy nodes update the corresponding proxy database according to the ARP information;

[0301] The proxy nodes in the same group are obtained by grouping the proxy nodes in the cluster by the master node according to the IP addresses of the proxy nodes, and the relay node in each group is a proxy node selected from the group.

[0302] For the convenience of description, the above parts are divided into modules (or units) according to their functions and described separately. Of course, when implementing this application, the functions of each module (or unit) can be implemented in the same or multiple software or hardware.

[0303] In the embodiments of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program with a predetermined function, and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be part of an overall module or unit that includes the function of the module or unit.

[0304] After introducing the ARP information processing method and device according to the exemplary embodiment of the present application, next, an electronic device according to another exemplary embodiment of the present application is introduced.

[0305] Those skilled in the art will appreciate that various aspects of the present application may be implemented as a system, method or program product. Therefore, various aspects of the present application may be specifically implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to as "circuit", "module" or "system" herein.

[0306] Based on the same inventive concept as the above method embodiment, an electronic device is also provided in the embodiment of the present application. In one embodiment, the electronic device can be a master node or a proxy node. In this embodiment, the structure of the electronic device can be as follows: Fig.10 As shown, it includes a memory 1001 , a communication module 1003 and one or more processors 1002 .

[0307] The memory 1001 is used to store computer programs executed by the processor 1002. The memory 1001 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system and programs required for running the instant messaging function, etc.; the data storage area may store various instant messaging information and operation instruction sets, etc.

[0308] The memory 1001 may be a volatile memory, such as a random-access memory (RAM); the memory 1001 may also be a non-volatile memory, such as a read-only memory, a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD); or the memory 1001 may be any other medium that can be used to carry or store a desired computer program in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 1001 may be a combination of the above memories.

[0309] The processor 1002 may include one or more central processing units (CPU) or a digital processing unit, etc. The processor 1002 is configured to implement the above-mentioned ARP information processing method when calling the computer program stored in the memory 1001 .

[0310] The communication module 1003 is used to communicate with terminal devices and other servers.

[0311] The specific connection medium between the memory 1001, the communication module 1003 and the processor 1002 is not limited in the embodiment of the present application. Fig.10 In the embodiment, the memory 1001 and the processor 1002 are connected via a bus 1004. The bus 1004 is connected to the processor 1002 via a bus 1004. Fig.10 The connections between the other components are only for illustration and are not intended to be limiting. The bus 1004 can be divided into an address bus, a data bus, a control bus, etc. For ease of description, Fig.10 The diagram shows that only one thick line is used, but this does not mean that there is only one bus or only one type of bus.

[0312] The memory 1001 stores a computer storage medium, and the computer storage medium stores computer executable instructions, and the computer executable instructions are used to implement the ARP information processing method of the embodiment of the present application. The processor 1002 is used to execute the above-mentioned ARP information processing method, such as Figure 2 or Figure 5 shown.

[0313] In some possible implementations, various aspects of the ARP information processing method provided in the present application may also be implemented in the form of a program product, which includes a computer program. When the program product is run on an electronic device, the computer program is used to enable the electronic device to execute the steps of the ARP information processing method according to various exemplary implementations of the present application described above in this specification. For example, the electronic device may execute the following steps: Figure 2 or Figure 5 Follow the steps shown in .

[0314] The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0315] It should be noted that, although several units or subunits of the device are mentioned in the above detailed description, this division is merely exemplary and not mandatory. In fact, according to the embodiments of the present application, the features and functions of two or more units described above can be embodied in one unit. Conversely, the features and functions of one unit described above can be further divided into multiple units to be embodied.

[0316] In addition, although the operations of the method of the present application are described in a specific order in the drawings, this does not require or imply that the operations must be performed in this specific order, or that all the operations shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0317] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain a computer-usable computer program.

[0318] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program commands. These computer program commands can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the commands executed by the processor of the computer or other programmable data processing device generate commands for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0319] Although the preferred embodiments of the present application have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications falling within the scope of the present application.

[0320] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. An ARP information processing method, applied to a master node in a cluster, the method comprising: After the preset collection conditions are met, an address resolution protocol ARP information collection request is sent to each proxy node in the cluster to obtain the ARP information of each proxy node; the collection conditions include at least one of the following: timed collection, in response to the collection request of the object; According to each ARP information obtained, update the master database corresponding to the master node; The updated ARP information in the main database is sent to each proxy node respectively, so that each proxy node updates the proxy database corresponding to the proxy node according to the ARP information in the main database.

2. The method according to claim 1, characterized in that The method further comprises: Receiving an ARP information configuration request sent by a first proxy node in the cluster; the ARP information configuration is sent by the first proxy node after determining that the corresponding proxy database is not configured with ARP information; According to the ARP information configuration request, the ARP information of each proxy node in the main database is queried, and the ARP information of each proxy node is sent to the first proxy node, so that the first proxy node configures the proxy database corresponding to the first proxy node according to the ARP information of each proxy node.

3. The method according to claim 1, characterized in that The method further comprises: Receiving an ARP information change message sent by a second proxy node in the cluster; the ARP information change message includes: updated ARP information corresponding to the second proxy node; updating the master database according to the updated ARP information, and querying a third proxy node related to the second proxy node; Notify the second proxy node and the third proxy node to update corresponding proxy databases according to the updated ARP information.

4. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: When sending ARP information to any of the proxy nodes, if it is detected that there is a task that fails to send, the task is added to the retry task queue; According to the first duration, the tasks in the retry task queue are periodically triggered to resend the ARP information corresponding to the tasks.

5. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: Perform at least one of the following processing operations on the received ARP information: De-duplicate the ARP information sent by the same proxy node; For the same type of ARP information sent by different proxy nodes, the same type of ARP information is merged into one ARP information; Discard the ARP information in the message queue that exceeds the preset threshold length; Different ARP information is sorted by priority and processed in sequence.

6. The method according to any one of claims 1 to 3, characterized in that: The updating of the ARP information in the database is sent to each proxy node respectively, including: Grouping the proxy nodes according to their IP addresses, and selecting a proxy node in each group of proxy nodes as a relay node; The updated ARP information in the database is sent to the relay node, so that the ARP information in the database is forwarded to other proxy nodes in the same group through the relay node.

7. An ARP information processing method, applied to a proxy node in a cluster, the method comprising: After receiving the ARP information collection request sent by the master node in the cluster, the ARP information of the proxy node is obtained and sent to the master node, so that the master node updates the master database corresponding to the master node according to the obtained ARP information, and sends the updated ARP information in the master database to the proxy node respectively; the ARP information collection request is sent by the master node after satisfying at least one of the following preset collection conditions: timed collection, in response to the collection request of the object; After receiving the ARP information in the main database sent by the master node, the corresponding proxy database is updated according to the ARP information.

8. The method according to claim 7, characterized in that The method further comprises: After determining that the corresponding proxy database is not configured with ARP information, sending an ARP information configuration request to the master node, so that the master node queries and returns the ARP information of each proxy node in the master database according to the ARP information configuration request; According to the ARP information of each proxy node, a corresponding proxy database is configured.

9. The method according to claim 8, characterized in that If it is determined through the periodic check that the ARP information is not configured, before determining that the ARP information is not configured, the method further includes: According to the second time period, periodically check whether the corresponding proxy database is configured with ARP information; And, the method further comprises: If the proxy database configuration fails, reducing the second time length; If the proxy database is configured successfully, the second duration is increased.

10. The method according to claim 7, characterized in that The method further comprises: After determining that its own ARP information has changed, sending updated ARP information to the master node through an ARP information change message, so that the master node updates the master database according to the updated ARP information, and notifies the relevant proxy nodes to update the corresponding proxy database according to the updated ARP information; According to the updated ARP information, the corresponding proxy database is updated.

11. The method according to any one of claims 7 to 10, characterized in that: If the proxy node is a relay node, the method further includes: Forwarding the ARP information to other proxy nodes in the same group, so that the other proxy nodes update corresponding proxy databases according to the ARP information; The proxy nodes in the same group are obtained by grouping the proxy nodes in the cluster by the master node according to the IP addresses of the proxy nodes, and the relay node in each group is a proxy node selected from the group.

12. An ARP information processing device, applied to a master node in a cluster, characterized in that: include: A collection unit, configured to send an ARP information collection request to each proxy node in the cluster to obtain the ARP information of each proxy node after a preset collection condition is met; the collection condition includes at least one of the following: timed collection in response to a collection request of an object; A first updating unit, configured to update a master database corresponding to the master node according to each acquired ARP information; The first sending unit is used to send the updated ARP information in the main database to each of the proxy nodes, so that each proxy node updates the proxy database corresponding to the proxy node according to the ARP information in the main database.

13. An ARP information processing device, applied to a proxy node in a cluster, characterized in that: include: The second sending unit is used to obtain the ARP information of the proxy node and send it to the master node after receiving the ARP information collection request sent by the master node in the cluster, so that the master node updates the master database corresponding to the master node according to the obtained ARP information, and sends the updated ARP information in the master database to the proxy node respectively; the ARP information collection request is sent by the master node after satisfying at least one of the following preset collection conditions: timed collection, in response to the collection request of the object; The second updating unit is configured to update the corresponding proxy database according to the ARP information received from the master node in the master database.

14. An electronic device, characterized in that: The method comprises a processor and a memory, wherein the memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of any one of the methods of claims 1 to 11.

Images