CN116938881B - Method, system, equipment and readable storage medium for realizing dynamic IP pool - Google Patents

Abstract

The invention provides a method, system, equipment and readable storage medium for realizing a dynamic IP pool, and relates to the field of communication processing technology, including: each node competes for the ETCD distributed lock to elect a master node at the same time; the master node and the slave node pass gRPC Perform periodic interactions to detect whether the primary node and secondary node are abnormal. If the primary node is abnormal, re-elect the primary node; if the secondary node is abnormal, the primary node takes over the secondary node IP or assigns the secondary node IP to other normal secondary nodes to take over. ; The primary node and the secondary node execute the preset detection cycle script respectively. If their own business execution is abnormal, the node will be processed according to the preset IP change. The present invention is based on the gRPC+ETCD architecture, and ETCD performs master node election and status monitoring; through gRPC communication, the business detection content is planned, and various types of abnormal IP takeovers are clarified, so that when a node fails or the IP is lost, the present invention can still be implemented NAS high availability business.

Description

A method, system, device and readable storage medium for implementing a dynamic IP pool

Technical field

The present invention relates to the technical field of communication processing, and specifically to a method, system, equipment and readable storage medium for realizing a dynamic IP pool.

Background technique

The existing network-attached storage (NAS) high-availability design architecture based on unified distributed storage (UDS) is highly dependent on the distributed key-value storage system (ETCD), and during the cluster deployment process, the ETCD database and NAS storage will be deployed in a mixed manner. On the same node, when ETCD fails, the cluster node becomes abnormal, and the drift and takeover of the NAS high-availability business and high-availability NAS IP cannot be fully realized. Moreover, this architecture is highly bound to ETCD. After discovering ETCD failure or cluster node abnormality, it is difficult to add and modify related services.

Contents of the invention

The purpose of the present invention is to provide a method, system, equipment and readable storage medium for realizing a dynamic IP pool, so as to solve the above problems. In order to achieve the above objects, the technical solutions adopted by the present invention are as follows:

In the first aspect, this application provides a method for implementing a dynamic IP pool for the node side, including: cluster nodes are connected to a distributed key-value storage system, and each node simultaneously competes for the distributed lock of the distributed key-value storage system to elect the master. Node, the node that obtains the distributed lock is the master node, and the other nodes are the slave nodes; through the Google remote procedure call protocol, the master node and the slave node interact periodically to detect whether the master node and the slave node are abnormal. If the master node is abnormal, then Re-elect the primary node to obtain a new primary node; if the secondary node is abnormal, the primary node takes over the secondary node IP or assigns the secondary node IP to other normal secondary nodes to take over; the primary node and the secondary node execute the preset detection cycle scripts respectively. Determine whether its own business execution is abnormal. If its own business execution is abnormal, the node will be processed according to the preset IP change.

In the second aspect, this application also provides a system for realizing a dynamic IP pool, including: a node election unit, a node interaction unit, an interface unit and a service detection unit. The node election unit is used for each node to simultaneously compete for the distributed lock of the distributed key-value storage system to elect the master node. The node interaction unit is used for periodic interaction between the primary node and the secondary node through the Google remote procedure call protocol. The interface unit is used to input a preset detection cycle script. The business detection unit is used for the primary node and the secondary node to respectively execute preset detection loop scripts to determine whether their own business execution is abnormal.

In the third aspect, this application also provides a device for implementing a dynamic IP pool, including:

Memory, used to store computer programs;

A processor, configured to implement the steps of the method for implementing a dynamic IP pool when executing the computer program.

In a fourth aspect, the present application also provides a readable storage medium, including a computer program stored on the readable storage medium, and when the computer program is executed by a processor, the steps of the method for implementing a dynamic IP pool are implemented. .

The beneficial effects of the present invention are:

This invention uses a distributed key-value storage system (ETCD) architecture based on Google Remote Procedure Call Protocol (gRPC), and uses ETCD to perform master node election, status monitoring, service discovery, and load balancing; through the gRPC framework, the business detection content is planned , clearly solves various types of abnormal takeover problems. When a node fails or the IP is lost, the present invention can still realize NAS high-availability services.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of embodiments of the invention. The objectives and other advantages of the invention may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Description of drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required to be used in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and therefore do not It should be regarded as a limitation of the scope. For those of ordinary skill in the art, other relevant drawings can be obtained based on these drawings without exerting creative efforts.

Figure 1 is a flow chart of step S100 of the method for implementing a dynamic IP pool in the implementation of the present invention;

Figure 2 is a flow chart of step S200 of the method for implementing a dynamic IP pool in the implementation of the present invention;

Figure 3 is a flow chart of step S300 of the method for implementing a dynamic IP pool in the implementation of the present invention;

Figure 4 is a schematic structural diagram of a system for realizing a dynamic IP pool in the implementation of the present invention;

Figure 5 is a schematic structural diagram of a device for implementing a dynamic IP pool in the implementation of the present invention.

Markings in the picture:

400. Node election unit; 500. Node interaction unit; 600. Interface unit; 700. Business detection unit; 410. Rent creation unit; 420. Revision unit; 430. First comparison unit; 440. Lease renewal unit; 510. Reporting Unit; 520, role improvement unit; 530, second comparison unit; 540, third comparison unit; 550, notification unit; 560, collection unit; 570, distribution unit; 580, return unit; 710, detection unit; 711, business Planning unit; 720, first judgment unit; 730, second judgment unit; 731, IP change unit; 800, device for realizing dynamic IP pool; 801, processor; 802, memory; 803, instruction input port; 804, I /O interface; 805, communication component.

Detailed ways

In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments These are some embodiments of the present invention, rather than all embodiments. The components of the embodiments of the invention generally described and illustrated in the figures herein may be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of the invention provided in the appended drawings is not intended to limit the scope of the claimed invention, but rather to represent selected embodiments of the invention. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without making creative efforts fall within the scope of protection of the present invention.

It should be noted that similar reference numerals and letters represent similar items in the following figures, therefore, once an item is defined in one figure, it does not need further definition and explanation in subsequent figures. Meanwhile, in the description of the present invention, the terms "first", "second", etc. are only used to differentiate the description and cannot be understood as indicating or implying relative importance.

Example 1:

This embodiment provides a method for implementing a dynamic IP pool, which is used on the node side and includes:

S100, the cluster nodes are connected to the distributed key-value storage system, and each node competes for the distributed lock of the distributed key-value storage system at the same time to elect the master node. The node that obtains the distributed lock is the master node, and the other nodes are deputy nodes. The master node is unique among the cluster nodes and has synchronization, scheduling and distribution privileges. After the master node is elected, each node starts to perform its own business.

S200. Through the Google remote procedure call protocol, the primary node and the secondary node interact periodically to detect whether the primary node and the secondary node are abnormal. If the primary node is abnormal, the primary node will be re-elected to obtain a new primary node; if the secondary node is abnormal, Then the primary node takes over the secondary node IP or assigns the secondary node IP to other normal secondary nodes to take over;

S300, the primary node and the secondary node respectively execute the preset detection cycle script to determine whether their own business execution is abnormal. If their own business execution is abnormal, the node will be processed according to the preset IP change.

As shown in Figure 1, in some specific embodiments, step S100 includes step S110, step S120, step S130 and step S140.

S110. Use the machine ID of each node as the corresponding unique identifier, and each node creates a lease for its own unique identifier;

S120. Each node writes its own identifier and lease into the distributed key-value storage system, obtains the returned revised value according to the revision mechanism of the distributed key-value storage system, and each node records its own revised value;

S130. Compare the revision values of each node, and select the node with the smallest revision value to obtain the distributed lock. This node is the primary node and the other nodes are secondary nodes;

S140. The master node renews the lease through the heartbeat mechanism.

The periodic interaction described in step S200 includes the secondary node regularly reporting its own information to the primary node and the primary node regularly collecting secondary node information. As shown in Figure 2, in some specific embodiments, step S200 includes step S210, step S220, step S230, step S240, step S250, step S260, step S270 and step S280.

S210. When the secondary node periodically reports to the primary node through the Google remote procedure call protocol that its role is the secondary node and is online, if the report times out, it is determined that the primary node is abnormal and the secondary node initiates an election;

S220. The deputy node promotes its role to a candidate, adds 1 to the term number, and obtains an updated term number;

S230. Obtain the term number of other nodes, and compare whether the updated term number is consistent with the term number of other nodes. If they are inconsistent, the candidate will be the new primary node;

S240. If they are consistent, the candidate compares the IP size with other nodes and selects the node with the larger IP as the new primary node. The node with the smaller IP automatically reduces its role to the deputy node;

It should be noted that the architecture of this application is an asynchronous model. There are situations where multiple nodes become candidates at the same time and the other party has not updated the term number. Therefore, when this happens, the cluster nodes need to compete for the distributed lock again to avoid the occurrence of Multiple master nodes.

S250. After the new master node is elected, the new master node informs other nodes of the term number of the new master node and synchronizes the terms of other nodes;

S260, the primary node regularly collects secondary node information through the Google remote procedure call protocol;

S270. If the master node times out in collecting a certain slave node information in step S260, it is determined that the slave node is abnormal, and the master node takes over the slave node IP or assigns the slave node IP to other normal slave nodes to take over;

S280. The master node collects the secondary node information again through step S260. If the collection of the secondary node information is normal, the secondary node IP is automatically returned by the taken over node.

As shown in Figure 3, in some specific embodiments, step S300 includes step S310, step S320 and step S330.

S310. Detect node roles, and call the corresponding Google remote procedure call protocol according to different roles to perform cyclic detection of node services; the detection includes high-availability service node status, high-availability configuration network card status, physical device status, network file system processes, and Information service block process.

S320. If the detection on the master node in step S310 is abnormal, it is determined that the service execution of the master node is abnormal, and the master node is re-elected;

S330. If the detection on the secondary node in step S310 is abnormal, it is determined that the service execution of the secondary node is abnormal, and the primary node processes the secondary node according to the preset IP change.

It should be noted that the preset IP changes specifically include:

When the high-availability service node is suspended, the node IP is taken over by other normal nodes; when the high-availability service node is restored, the node IP is automatically returned by the taken-over node; when the high-availability configured network card is disconnected, the node IP is taken over by other normal nodes; When the high-availability configuration network card is reconnected, the node IP is automatically returned by the node that took over; when the physical device corresponding to the node is shut down, restarted, or powered off, the node IP is taken over by other normal nodes; when the physical device corresponding to the node is powered on and running normally, the node IP The node IP is automatically returned by the node that is taken over; when the network file system process stops or becomes abnormal, the node IP is taken over by other normal nodes; when the information service block process stops or becomes abnormal, the node IP is taken over by other normal nodes.

In some specific embodiments, step S140 includes step S141 and step S142.

S141. When the master node holds the distributed lock, the node crashes, the heartbeat mechanism stops, the unique identifier will be deleted due to the expiration of the lease, and the master node releases the distributed lock to avoid deadlock;

S142. The remaining nodes compete for the distributed lock and select a new master node.

Example 2:

As shown in Figure 4, this embodiment provides a system for implementing a dynamic IP pool, including:

The node election unit 400 is used for each node to simultaneously compete for the distributed lock election master node of the distributed key-value storage system;

The node interaction unit 500 is used for periodic interaction between the primary node and the secondary node through the Google remote procedure call protocol;

The interface unit 600 is used to input a preset detection cycle script;

The service detection unit 700 is used for the primary node and the secondary node to respectively execute preset detection loop scripts to determine whether their own services are abnormally executed.

In some specific embodiments, the node election unit 400 includes:

The rent creation unit 410 is used to use the machine ID of each node as the corresponding unique identifier, and each node creates a lease for its own unique identifier;

The revision unit 420 is used for each node to write its own identifier and lease into the distributed key-value storage system, obtain the returned revision value according to the revision mechanism of the distributed key-value storage system, and each node records its own revision value;

The first comparison unit 430 is used to compare the size of the revised value of each node, and select the node with the smallest revised value to obtain the distributed lock. This node is the primary node and the other nodes are secondary nodes;

The lease renewal unit 440 is used by the master node to renew the lease through the heartbeat mechanism.

In some specific embodiments, the node interaction unit 500 includes:

The reporting unit 510 is used for the secondary node to periodically report to the primary node through the Google remote procedure call protocol that its role is a secondary node and that it is online;

The role promotion unit 520 is used by the deputy node to promote its own role to a candidate, and the term number is increased by 1 to obtain an updated term number;

The second comparison unit 530 is used to obtain the term number of other nodes, and compare whether the updated term number is consistent with the term number of other nodes. If they are inconsistent, the candidate will be regarded as the new master node;

The third comparison unit 540 is used to compare the IP size of the candidate with other nodes when the results of the second comparison unit are consistent, and select the node with the larger IP as the new primary node. The node with the smaller IP automatically reduces its role to a secondary node. ;

The notification unit 550 is used to notify other nodes of the term number of the new master node after the new master node is elected, and synchronize the terms of other nodes;

Collection unit 560, used by the primary node to regularly collect secondary node information through the Google remote procedure call protocol;

The allocation unit 570 is used for when the master node times out to collect a certain slave node information, the master node takes over the slave node IP or allocates the slave node IP to other normal slave nodes to take over;

The return unit 580 is used by the master node to collect the secondary node information again through the Google remote procedure call protocol. When the collection of the secondary node information is normal, the secondary node IP is automatically returned to the taken over node.

In some specific embodiments, the service detection unit 700 includes:

The detection unit 710 is used to detect node roles, and call the corresponding Google remote procedure call protocol according to different roles to perform cyclic detection of node services;

The first judgment unit 720 is used to judge that when the detection on the master node is abnormal, the service execution of the master node is abnormal, and the master node is re-elected;

The second judgment unit 730 is used to judge that the service execution of the slave node is abnormal when the detection on the slave node is abnormal, and the master node processes the slave node according to the preset IP change.

In some specific real-time examples, the detection unit 710 includes:

The business planning unit 711 is used to plan detection content. The detection includes high availability service node status, high availability configuration network card status, physical device status, network file system process and information service block process;

In some specific real-time examples, the second judgment unit 730 includes:

IP change unit 731 is used to when the high availability service node is suspended, the node IP is taken over by other normal nodes; when the high availability service node is restored, the node IP is automatically returned by the taken over node; when the high availability configuration network card is disconnected, the node IP is automatically returned The IP is taken over by other normal nodes; when the high-availability configured network card is reconnected, the node IP is automatically returned by the node that took over; when the physical device corresponding to the node is shut down or restarted or powered off, the node IP is taken over by other normal nodes; the node's corresponding physical When the device is powered on and running normally, the node IP will be automatically returned by the node that has taken over; when the network file system process stops or becomes abnormal, the node IP will be taken over by other normal nodes; when the information service block process stops or becomes abnormal, the node IP will be taken over by other normal nodes.

Example 3:

Corresponding to the above method embodiment, this embodiment also provides a device for implementing a dynamic IP pool. The device for implementing a dynamic IP pool described below and the method for implementing a dynamic IP pool described above may correspond to each other.

FIG. 5 is a block diagram of a device for implementing a dynamic IP pool according to an exemplary embodiment. As shown in Figure 5, the device 800 for implementing a dynamic IP pool includes: a processor 801 and a memory 802. The device for implementing a dynamic IP pool may also include one or more of an instruction input port 803, an I/O interface 804, and a communication component 805.

The processor 801 is used to control the overall operation of the device that implements the dynamic IP pool, so as to complete all or part of the steps in the above method for implementing the dynamic IP pool. The memory 802 is used to store various types of data to support operations on the device implementing the dynamic IP pool, which data may include, for example, instructions for any application or method operating on the device implementing the dynamic IP pool, and Application-related data. The memory 802 can be implemented by any type of volatile or non-volatile storage device or their combination, such as static random access memory (Static Random Access Memory, SRAM for short), electrically erasable programmable read-only memory (Electrically erasable programmable read-only memory) ErasableProgrammable Read-Only Memory (EEPROM for short), Erasable Programmable Read-Only Memory (EPROM for short), Programmable Read-Only Memory (PROM for short), Read-Only Memory (Read -Only Memory (ROM for short), magnetic memory, flash memory, magnetic disk or optical disk. The instruction input port 803 may include a screen and a keyboard. The screen may be a touch screen, for example, and the keyboard is used to output and/or input program instructions. The received program instructions may be further stored in memory 802 or sent via communications component 805 . The I/O interface 804 provides an interface between the processor 801 and other interface modules. The other interface modules may be mice, buttons, etc. These buttons can be virtual buttons or physical buttons. The communication component 805 is used for wired or wireless communication between the device that implements the dynamic IP pool and other devices. Wireless communication, such as Wi-Fi, Bluetooth, Near Field Communication (NFC), 2G, 3G or 4G, or one or a combination of them, so the corresponding communication component 805 can include: Wi -Fi module, Bluetooth module, NFC module.

In an exemplary embodiment, the device 800 that implements the dynamic IP pool may be configured by one or more Application Specific Integrated Circuits (ASICs for short), Digital Signal Processors (Digital Signal Processors for short, DSPs for short), digital signal processing Equipment (Digital Signal Processing Device, DSPD for short), Programmable Logic Device (PLD for short), Field Programmable Gate Array (FPGA for short), controller, microcontroller, microprocessor or others Electronic components are implemented for executing the above method of implementing a dynamic IP pool.

Example 4:

Corresponding to the above method embodiment, this embodiment also provides a storage medium, the storage medium is a readable storage medium, a readable storage medium described below and the method for implementing a dynamic IP pool described above can be referenced to each other.

A readable storage medium. A computer program is stored on the readable storage medium. When the computer program is executed by the processor 801, the steps of the method for implementing a dynamic IP pool in the above method embodiment are implemented.

The readable storage medium can specifically be a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk that can store program codes. readable storage media.

The above descriptions are only preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention shall be included in the protection scope of the present invention.

The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any person familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed by the present invention. should be covered by the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims (8)

1. A method for implementing a dynamic IP pool, for a node, comprising:

the cluster nodes are connected with the distributed key value storage system, all nodes compete for the distributed lock of the distributed key value storage system to elect a master node, the node for obtaining the distributed lock is the master node, and other nodes are slave nodes;

periodically interacting the master node and the slave node through a Google remote procedure call protocol, detecting whether the master node and the slave node are abnormal, and reelecting the master node if the master node is abnormal to obtain a new master node; if the auxiliary node is abnormal, the main node takes over the auxiliary node IP or distributes the auxiliary node IP to other normal auxiliary nodes to take over;

the main node and the auxiliary node execute a preset detection cycle script respectively, and judge whether own business is abnormal or not, comprising the following steps:

detecting node roles, and calling corresponding google remote procedure call protocols according to different roles to circularly detect node services; the detection comprises a high-availability service node state, a high-availability configuration network card state, a physical equipment state, a network file system process and an information service block process;

if the detection on the main node is abnormal, judging that the service execution of the main node is abnormal, and reelecting the main node;

if the detection on the auxiliary node is abnormal, judging that the service execution of the auxiliary node is abnormal, and processing the auxiliary node by the main node according to the preset IP change, wherein the preset IP change specifically comprises:

when the high available service node pauses, the node IP is taken over by other normal nodes; when the high available service node is recovered, the node IP is automatically returned by the takeover node; when the high-availability configuration network card is disconnected, the node IP is taken over by other normal nodes; when the high-availability configuration network card is reconnected, the node IP is automatically returned by the takeover node; when the physical equipment corresponding to the node is shut down, restarted or powered off, the node IP is taken over by other normal nodes; when the physical equipment corresponding to the node is started and normally operates, the node IP is automatically returned by the takeover node; when the network file system process stops or is abnormal, the node IP is taken over by other normal nodes; the node IP is taken over by other normal nodes when the information service block process stops or is abnormal.

2. The method for implementing a dynamic IP pool of claim 1, wherein each node simultaneously contends for a distributed lock of a distributed key value storage system, the node that obtains the distributed lock being a primary node, and the other nodes being secondary nodes, comprising:

taking the machine ID of each node as a corresponding unique identifier, and each node respectively creates leases for the unique identifiers of the nodes;

each node writes the identifier and lease of the node into a distributed key value storage system, obtains a returned revision value according to a revision mechanism of the distributed key value storage system, and records the revision value of the node;

comparing the sizes of the revisions of the nodes, and selecting the node with the smallest revisions to obtain a distributed lock, wherein the node is a main node, and other nodes are auxiliary nodes;

the master node renews the lease through a heartbeat mechanism.

3. The method for implementing a dynamic IP pool according to claim 1, wherein the master node performs periodic interaction with the slave node through a google remote procedure call protocol, and detects whether the master node and the slave node are abnormal, the periodic interaction includes the slave node periodically reporting own information to the master node and the master node periodically collecting slave node information, including:

when the slave node periodically reports the role of the slave node to the master node through the Google remote procedure call protocol and is online, if the report is overtime, the master node is judged to be abnormal, and the slave node initiates election;

the auxiliary node promotes the role of the auxiliary node to be an competitor, and adds 1 to the tenn to obtain an updated tenn;

acquiring the tenure numbers of other nodes, comparing whether the updated tenure numbers are consistent with the tenure numbers of other nodes, and if not, using the competitor as a new master node;

if the nodes are consistent, the competitor compares the IP size with other nodes, selects the node with large IP as a new main node, and the node with small IP automatically reduces the role to a secondary node;

after the new master node is selected, the new master node informs other nodes of the tening period number of the new master node and synchronizes the tening period of other nodes;

the main node periodically collects information of the auxiliary node through a google remote procedure call protocol;

if the information of a certain auxiliary node collected by the main node is overtime, judging that the auxiliary node is abnormal, and the main node takes over the auxiliary node IP or distributes the auxiliary node IP to other normal auxiliary nodes to take over;

and the main node collects the information of the auxiliary node again through the google remote procedure call protocol, and if the information of the auxiliary node is collected normally, the auxiliary node IP is automatically returned by the take-over node.

4. A system for implementing a dynamic IP pool, comprising:

the node election unit is used for simultaneously competing the distributed lock election master node of the distributed key value storage system by each node;

the node interaction unit is used for periodically interacting the main node and the auxiliary node through a google remote procedure call protocol;

the interface unit is used for inputting a preset detection cycle script;

the service detection unit is used for respectively executing a preset detection cycle script by the main node and the auxiliary node and judging whether the own service is abnormal;

the service detection unit includes:

the detection unit is used for detecting node roles, and calling corresponding google remote procedure call protocols according to different roles to carry out cyclic detection on node services;

the first judging unit is used for judging that the service execution of the main node is abnormal when the detection on the main node is abnormal, and reelecting the main node;

the second judging unit is used for judging that the service execution of the auxiliary node is abnormal when the detection on the auxiliary node is abnormal, and the main node processes the auxiliary node according to the preset IP change;

the detection unit includes:

the service planning unit is used for planning detection contents, wherein the detection comprises a high-availability service node state, a high-availability configuration network card state, a physical equipment state, a network file system process and an information service block process;

the second judging unit includes:

an IP change unit, configured to take over, when a high available service node is suspended, the node IP by other normal nodes; when the high available service node is recovered, the node IP is automatically returned by the takeover node; when the high-availability configuration network card is disconnected, the node IP is taken over by other normal nodes; when the high-availability configuration network card is reconnected, the node IP is automatically returned by the takeover node; when the physical equipment corresponding to the node is shut down, restarted or powered off, the node IP is taken over by other normal nodes; when the physical equipment corresponding to the node is started and normally operates, the node IP is automatically returned by the takeover node; when the network file system process stops or is abnormal, the node IP is taken over by other normal nodes; the node IP is taken over by other normal nodes when the information service block process stops or is abnormal.

5. The system for implementing a dynamic IP pool of claim 4 wherein said node election unit comprises:

the lease creating unit is used for taking the machine ID of each node as a corresponding unique identifier, and each node creates lease for the unique identifier of each node;

the revising unit is used for writing the identifier and lease of each node into the distributed key value storage system, obtaining a returned revised value according to a revising mechanism of the distributed key value storage system, and recording the revised value of each node;

the first comparison unit is used for comparing the sizes of the revisions of the nodes, selecting the node with the smallest revisions to obtain a distributed lock, wherein the node is a main node, and other nodes are auxiliary nodes;

and the renewing unit is used for renewing the lease by the master node through a heartbeat mechanism.

6. The system for implementing a dynamic IP pool of claim 4 wherein said node interaction unit comprises:

the reporting unit is used for periodically reporting the role of the slave node to the master node through the Google remote procedure call protocol as the slave node and is online;

the role lifting unit is used for lifting the role of the auxiliary node to be an competitor, and adding 1 to the tenn number to obtain an updated tenn number;

the second comparison unit is used for acquiring the tenure numbers of other nodes, comparing whether the updated tenure numbers are consistent with the tenure numbers of other nodes or not, and if not, using the competitor as a new master node;

the third comparison unit is used for comparing the IP size of the competitor with other nodes when the results of the second comparison unit are consistent, selecting the node with large IP as a new main node, and automatically reducing the role to a secondary node by the node with small IP;

the notification unit is used for notifying other nodes of the tening period number of the new master node after the new master node is elected, and synchronizing the tening periods of other nodes;

the collecting unit is used for periodically collecting auxiliary node information by the main node through a google remote procedure call protocol;

the distribution unit is used for taking over the auxiliary node IP by the main node or distributing the auxiliary node IP to other normal auxiliary nodes when the main node collects certain auxiliary node information overtime;

and the return unit is used for collecting the information of the auxiliary node again by the main node through the google remote procedure call protocol, and when the information of the auxiliary node is collected normally, the auxiliary node IP is automatically returned by the take-over node.

7. An apparatus for implementing a dynamic IP pool, comprising:

a memory for storing a computer program;

a processor for implementing the steps of the method of implementing a dynamic IP pool according to any of claims 1 to 3 when said computer program is executed.

8. A readable storage medium, comprising a computer program stored thereon, which when executed by a processor, implements the steps of the method of implementing a dynamic IP pool according to any of claims 1 to 3.