CN105245361A - Data high availability system, method and device for Linux system - Google Patents

Abstract

The embodiment of the invention provides a data high availability system for a Linux system, a method and a device. The system comprises a distributed file system, fault transfer equipment, at least two pieces of middleware and clients, wherein the distributed file system comprises at least two server nodes, and the server nodes are bound by a network card; one end of the fault transfer equipment is connected with all server nodes and the other end is connected with all pieces of middleware for monitoring whether fault happens to currently-used server nodes and currently-used middleware and switching failed server nodes and failed middleware; each piece of middleware is connected with all clients; and the clients perform data interaction with the server nodes in the distributed file system via the middleware and the fault transfer equipment. As the distributed file system and multiple pieces of middleware are adopted, as long as one normal server node and one normal piece of middleware exist, data interaction can be carried out, data high availability is ensured, and continuity of upper service can be further ensured.

Description

Data high availability system, method and device for Linux system

technical field

The invention relates to the technical field of data transmission in a Linux system, in particular to a high data availability system, method and device for a Linux system.

Background technique

At present, in minicomputers and other similar linux systems, the client usually interacts with the storage device through a single middleware and a single server node. When the middleware and/or server node fails during the data interaction, the The data interaction process cannot be continued, the high availability of data cannot be guaranteed, and the continuity of upper-layer business cannot be guaranteed.

Contents of the invention

In view of this, the embodiment of the present invention provides a high data availability system, method and device for Linux system to solve the problem that in the prior art, the client usually interacts with the storage device through a single middleware and a single server node, When the middleware and/or server nodes fail during the data interaction process, the data interaction process cannot be continued, the high availability of data cannot be guaranteed, and the continuity of upper-layer business cannot be guaranteed.

In order to achieve the above purpose, embodiments of the present invention provide the following technical solutions:

A high-availability data system for Linux systems, including: a distributed file system, a failover device, at least two middleware and a client; wherein,

The distributed file system includes at least 2 server nodes, and a network card binding mode is adopted between each of the server nodes;

One end of the failover device is connected to all the server nodes, and the other end is connected to all the middleware, and is used to monitor whether the currently used server node and the currently used middleware fail, and when a failure of the currently used server node is detected, Select another server node among all server nodes as the currently used server node, and select another middleware among all the middleware as the currently used middleware when detecting a failure of the currently used middleware;

each said middleware is connected to all said clients;

The client performs data interaction with the server node in the distributed file system through the middleware and the failover device.

Wherein, the distributed file system further includes a storage device, and all the storage devices are mounted on each of the server nodes, so as to realize data interaction between the storage device and the server nodes.

Wherein, the storage device exchanges data with the server node through an optical fiber switch.

A data high availability method for a Linux system, based on the above-mentioned high data availability system for a Linux system, comprising:

Determine the currently used server node and the currently used middleware;

Monitoring whether the currently used server node fails, if so, selecting another server node among all server nodes as the currently used server node;

Monitor whether the currently used middleware breaks down, and if so, select another middleware among all middlewares as the currently used middleware to ensure that the client computer communicates with the current middleware in the distributed file system through the currently used middleware and the failover device. Use server nodes for normal data interaction.

Among them, before determining the currently used server node and the currently used middleware, it also includes:

Determine the directory where the distributed file system is mounted;

Configure all middleware, and mount all the middleware under the directory.

Among them, before determining the currently used server node and the currently used middleware, it also includes:

Configure a public IP address for all server nodes;

Configure floating IP addresses for all said server nodes.

Wherein, another server node is selected among all server nodes according to the floating IP address as the currently used server node.

A high data availability device for a Linux system, comprising: a determination module, a first monitoring module and a second monitoring module; wherein,

The determining module is used to determine the currently used server node and the currently used middleware;

The first monitoring module is used to monitor whether the currently used server node fails, and if so, select another server node among all server nodes as the currently used server node;

The second monitoring module is used to monitor whether the currently used middleware breaks down, and if it occurs, select another middleware among all middlewares as the currently used middleware to ensure that the client passes through the currently used middleware and the failure. The transfer device interacts with the normal data of the currently used server nodes in the distributed file system.

Wherein, the high data availability device for the Linux system also includes: a first configuration module, configured to determine the directory mounted by the distributed file system, configure all middleware, and mount all the middleware on the directory Down.

Wherein, the high data availability device for the Linux system further includes: a second configuration module, configured to configure a public IP address for all server nodes, and configure floating IP addresses for all the server nodes.

Based on the above technical solution, the embodiment of the present invention provides a system, method and device for high data availability of Linux systems, wherein the system is composed of a distributed file system, a failover device, at least two middleware and a client computer, wherein the distributed The file system includes at least 2 server nodes, and the network card binding mode is adopted between the server nodes. One end of the failover device is connected to all server nodes, and the other end is connected to all middleware, which is used to monitor the currently used server nodes and the currently used middleware. Whether there is a failure, when the failure of the currently used server node is detected, another server node is selected as the currently used server node among all server nodes, and another middleware is selected among all middleware when a failure of the currently used middleware is detected As the currently used middleware, each middleware is connected to all the clients, and the clients perform data interaction with the server nodes in the distributed file system through the middleware and the failover device. Collect the distributed file system, disperse the data in each server node, and use multiple middleware at the same time. When the failover device monitors that the server node currently in use fails, use another server node to continue data interaction with the client. Failover device monitoring When the currently used middleware fails, another middleware is used to enable the client to continue data interaction with the distributed branch system, that is, as long as there is a normal server node and a normal middleware, the client can continue Data interaction with the distributed file system ensures high data availability and further ensures the continuity of upper-layer business.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only It is an embodiment of the present invention, and those skilled in the art can also obtain other drawings according to the provided drawings without creative work.

Fig. 1 is the system block diagram of the data high availability system that is used for Linux system that the embodiment of the present invention provides;

Fig. 2 is the flowchart of the data high availability method for Linux system provided by the embodiment of the present invention;

Fig. 3 is the flow chart of the method for configuring middleware in the data high availability method for Linux system provided by the embodiment of the present invention;

Fig. 4 is the flow chart of the method for configuring server nodes in the data high availability method for the Linux system provided by the embodiment of the present invention;

Fig. 5 is a system block diagram of a data high availability device for a Linux system provided by an embodiment of the present invention;

FIG. 6 is another system block diagram of a data high availability device for a Linux system provided by an embodiment of the present invention;

FIG. 7 is another system block diagram of a data high availability device for a Linux system provided by an embodiment of the present invention.

detailed description

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without making creative efforts belong to the protection scope of the present invention.

Fig. 1 is a system block diagram of a data high availability system for a Linux system provided by an embodiment of the present invention, which collects a distributed file system, disperses the data in each server node, and uses multiple middleware at the same time, when the failover device monitors the current When the server node in use fails, use another server node to continue data interaction with the client, and when the failover device monitors that the middleware currently in use fails, use another middleware to continue the client computer and the distributed branch system Data interaction, that is, as long as there is a normal server node and a normal middleware, the client can continue to perform data interaction with the distributed file system, ensuring high data availability and further ensuring the continuity of upper-layer business; refer to Figure 1, The data high availability system for Linux system may include: a distributed file system 10 , a failover device 20 , at least two middleware 30 and a client 40 . in,

The distributed file system 10 includes at least two server nodes 11, and the network card binding mode is adopted between the server nodes 11, that is, the physical network cards of each server node are bound into a virtual network card to provide load balancing or redundancy and increase bandwidth. When any faulty network card in all server nodes 11 is unavailable, it will not affect the normal operation of other server nodes 11 .

Using a distributed file system, in addition to ensuring high availability of data and further ensuring the continuity of upper-layer business, compared with the local file system, there is no need to remount the data disk when a failover occurs, which will greatly reduce the cost of The time for server switchover when a failure occurs.

Optionally, the distributed file system 10 may also include a storage device 12, and all storage devices 12 are mounted on each server node 11 to realize data interaction between the storage device 12 and the server node 11, that is, each All storage devices 12 are hung on the server nodes 11, ensuring that the data in each server node 11 is the same, no matter which server node 11 in the distributed file system 10 the client 40 performs data interaction with, there is no difference.

Optionally, the storage device 12 may perform data interaction with the server node 11 through an optical fiber switch. Optionally, the optical fiber switch used may be an FC optical fiber switch.

One end of the failover device 200 is connected to all server nodes 11 in the distributed file system 10 , and the other end is connected to all middleware 30 .

When the client performs data interaction with the distributed branch system, for example, the client 40 reads the data information in the distributed branch system 10, or the client 40 writes data information into the distributed branch system 10, the device can be failed over 200 monitors whether the currently used server node (that is, the server node currently being used during the data interaction process) and the currently used middleware (that is, the currently used middleware during the data interaction process) are faulty.

If the failover device 200 detects that the currently used server node fails, then select another server node except the failed server node among all server nodes, and use the selected server node as the currently used server node, and use the replaced The currently used server node continues data interaction.

If the failover device 200 monitors the fault of the currently used middleware, select another middleware in all middlewares except the middleware of the failure as the currently used middleware, and the selected middleware as the currently used middleware, to The replaced currently used middleware continues to perform data interaction.

In addition to providing the failover device switching function, the failover device 200 also provides a unified interface address for upper-layer services, reducing application complexity.

Each middleware 300 is connected to all clients 400, and the clients 40 perform data interaction with the distributed file system 10 through the middleware 30 and the failover device 20. Specifically, the clients 40 pass through a middleware 30 and a failover device 20 performs data interaction with a server node 11 in the distributed file system 10 .

Optionally, all middleware 300 may include the same database, and when all middleware 300 include the same database, high availability of the database may be realized.

Optionally, the middleware 300 and the distributed file system 100 can be mounted in the same directory

Based on the above technical solution, the high availability data system for Linux system provided by the embodiment of the present invention is composed of a distributed file system, a failover device, at least 2 middleware and a client computer, wherein the distributed file system includes at least 2 Each server node adopts the network card binding mode. One end of the failover device is connected to all server nodes, and the other end is connected to all middleware to monitor whether the currently used server node and the currently used middleware are faulty. When monitoring When the currently used server node fails, select another server node among all server nodes as the currently used server node, and when detecting the failure of the currently used middleware, select another middleware among all the middleware as the currently used middleware, Each middleware is connected to all the clients, and the clients perform data interaction with the server nodes in the distributed file system through the middleware and the failover device. Collect the distributed file system, disperse the data in each server node, and use multiple middleware at the same time. When the failover device monitors that the server node currently in use fails, use another server node to continue data interaction with the client. Failover device monitoring When the currently used middleware fails, another middleware is used to enable the client to continue data interaction with the distributed branch system, that is, as long as there is a normal server node and a normal middleware, the client can continue Data interaction with the distributed file system ensures high data availability and further ensures the continuity of upper-layer business.

The following is an introduction to the high data availability method for the Linux system provided by the embodiment of the present invention. The high data availability method for the Linux system described below is based on the high data availability system for the Linux system described above.

Fig. 2 is the flow chart of the data high availability method for Linux system that the embodiment of the present invention provides, with reference to Fig. 2, this data high availability method for Linux system can include:

Step S100: Determine the currently used server node and the currently used middleware;

The currently used server node refers to the currently used server node when the client computer and the server node of the distributed branch system perform data interaction through middleware and failover equipment.

The currently used middleware refers to the middleware currently being used when the client computer and the distributed branch system perform data interaction through middleware and failover devices.

Optionally, before determining the currently used server node and currently used middleware, you can also determine the directory mounted by the distributed file system, configure all middleware, and mount all middleware under this directory, that is, the intermediate The file and the distributed file system are mounted in the same directory.

Optionally, before determining the currently used server node and the currently used middleware, a public IP address can also be configured for all server nodes, and a floating IP address can be configured for all server nodes. , according to the floating IP address, another server node can be selected among all server nodes as the currently used server node.

Step S110: Monitor whether the currently used server node fails, and if so, select another server node among all server nodes as the currently used server node;

After the currently used server node is determined, real-time monitoring of the determined currently used server node can be carried out. When it is detected that the currently used server node fails, it will immediately select all server nodes except the failed server node. Another server node, the selected server node is used as the currently used server node, and data exchange is continued with the replaced currently used server node.

If it is detected that another selected server node also fails, it will continue to select another server node in all server nodes except the known failed server node as the currently used middleware, and the selected Another server node is used as the currently used server node to continue data interaction.

By analogy, as long as the currently used server node is a failed server node, the failed server node is replaced until the currently used server node is a normal server node.

Step S120: Monitor whether the currently used middleware fails, and if so, select another middleware among all the middleware as the currently used middleware.

After determining the currently used middleware, the failover device will monitor the determined currently used middleware in real time. Another middleware is used as the currently used middleware, the selected middleware is used as the currently used middleware, and data interaction is continued with the replaced currently used middleware.

Similarly, if it is detected that another selected middleware also fails, the failover device will continue to select another middleware as the currently used middleware among all middleware except the middleware of known failure , and use another selected middleware as the currently used middleware to continue data interaction.

By analogy, as long as the currently used middleware is a faulty middleware, the faulty middleware is replaced until the currently used middleware is a normal middleware.

Wherein, there is no logical sequence relationship between step S210 and step S220, step S210 may be executed first and then step S220 may be executed, or step S220 may be executed first and then step S210 may be executed, and if conditions permit, step S210 and step S220 may also be executed at the same time .

Through steps S200, S210, and S220, it can be guaranteed at any time that the currently used server node is a normal server node, and the currently used middleware is a normal middleware, so that the client can be connected to the distributed file through the currently used middleware and failover equipment. The system currently uses server nodes for normal data interaction.

Optionally, FIG. 3 shows a flow chart of a method for configuring middleware in a data high availability method for a Linux system provided by an embodiment of the present invention. With reference to FIG. 3 , the method for configuring middleware may include:

S200: Determine the directory mounted by the distributed file system;

If you need to mount all middleware and the distributed file system in the same directory, you need to determine the directory where the distributed file system is mounted.

S210: Configure all the middleware, and mount all the middleware in the directory.

After determining the directory mounted by the distributed file system, all middleware can be configured, and all middleware will be deployed in the directory mounted by the distributed file system.

Optionally, FIG. 4 shows a flow chart of a method for configuring a server node in a data high availability method for a Linux system provided by an embodiment of the present invention. Referring to FIG. 4, the method for configuring a server node may include:

S300: configure a public IP address for all server nodes;

S310: Configure floating IP addresses for all the server nodes.

Optionally, another server node among all server nodes may be selected as the currently used server node through the set floating IP address.

When the currently used server node is server node 1, the floating IP address points to the server node 1. When the server node 1 fails, the floating IP address will automatically switch to another server node, such as server node 2. , the floating IP address points to the server node 2, and the server node 2 will be used as the currently used server node.

Optionally, when the middleware uses a proxy server to interact with the server node for communication data, the IP address of the proxy server of the middleware can be set as the floating IP address, so that no matter what the server node is currently used, the currently used middleware Both can perform normal data interaction with the currently used server node.

In the high data availability method for Linux systems provided by the embodiments of the present invention, when a fault occurs in the currently used server node, another server node is used to continue data interaction with the client, and when the failover device monitors the currently used middleware When a failure occurs, another middleware is used to enable the client to continue data interaction with the distributed branch system. As long as there is a normal server node and a normal middleware, the client can continue to perform data interaction with the distributed file system, ensuring This ensures high data availability and further ensures the continuity of upper-layer services.

The following is an introduction to the high data availability device for the Linux system provided by the embodiment of the present invention. The high data availability device for the Linux system described below and the high data availability method for the Linux system described above can be referred to each other.

Fig. 5 is a system block diagram of a data high availability device for a Linux system provided by an embodiment of the present invention. Referring to Fig. 5, the data high availability device for a Linux system may include: a determination module 100, a first monitoring module 200 and a first monitoring module 200 Two monitoring modules 300 . in,

A determining module 100, configured to determine the currently used server node and the currently used middleware;

The first monitoring module 200 is used to monitor whether the currently used server node fails, and if so, select another server node among all server nodes as the currently used server node;

The second monitoring module 300 is used to monitor whether the currently used middleware breaks down, and if it occurs, select another middleware among all middlewares as the currently used middleware to ensure that the client passes through the currently used middleware and failover The device interacts with the normal data of the currently used server nodes in the distributed file system.

Optionally, FIG. 6 shows another system block diagram of a data high availability device for a Linux system provided by an embodiment of the present invention. Referring to FIG. 6, the data high availability device for a Linux system may also include: a first Configuration module 400 .

The first configuration module 400 is configured to determine the directory mounted by the distributed file system, configure all middleware, and mount all the middleware under the directory.

Optionally, FIG. 7 shows another system block diagram of a data high availability device for a Linux system provided by an embodiment of the present invention. Referring to FIG. 7, the data high availability device for a Linux system may also include: a second Configuration module 500 .

The second configuration module 500 is configured to configure a public IP address for all server nodes, and configure floating IP addresses for all the server nodes.

The high availability device for Linux system provided by the embodiment of the present invention uses another server node to continue data interaction with the client when a fault occurs in the currently used server node. When the failover device monitors the current middleware When a failure occurs, another middleware is used to enable the client to continue data interaction with the distributed branch system. As long as there is a normal server node and a normal middleware, the client can continue to perform data interaction with the distributed file system, ensuring This ensures high data availability and further ensures the continuity of upper-layer services.

Each embodiment in this specification is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same and similar parts of each embodiment can be referred to each other. As for the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and for the related part, please refer to the description of the method part.

The above description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the present invention will not be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (10)

1. A data high availability system for use in a Linux system, comprising: a distributed file system, a failover device, at least 2 pieces of middleware, and a client; wherein,

the distributed file system comprises at least 2 server nodes, and a network card binding mode is adopted among the server nodes;

one end of the fault transfer equipment is connected with all the server nodes, the other end of the fault transfer equipment is connected with all the middleware and is used for monitoring whether the currently used server node and the currently used middleware have faults or not, when the faults of the currently used server node are monitored, another server node is selected from all the server nodes as the currently used server node, and when the faults of the currently used middleware are monitored, another middleware is selected from all the middleware as the currently used middleware;

each middleware is connected with all the clients;

the client performs data interaction with the server nodes in the distributed file system through the middleware and the failover device.

2. The data high availability system for the Linux system of claim 1, wherein the distributed file system further comprises a storage device, all the storage devices are mounted on each of the server nodes, and data interaction between the storage devices and the server nodes is realized.

3. The data high availability system for the Linux system of claim 2, wherein the storage device interacts data with the server nodes through a fabric switch.

4. A data high availability method for Linux system, based on the data high availability system for Linux system of claim 1, comprising:

determining a currently used server node and currently used middleware;

monitoring whether the currently used server node fails or not, and if so, selecting another server node from all the server nodes as the currently used server node;

and monitoring whether the currently used middleware fails or not, if so, selecting another middleware from all the middleware as the currently used middleware, and ensuring that the client interacts with normal data of the currently used server node in the distributed file system through the currently used middleware and the failover equipment.

5. The method of claim 4, wherein determining the currently used server node and the currently used middleware further comprises:

determining a mounted directory of the distributed file system;

and configuring all the middleware, and mounting all the middleware under the directory.

6. The method of claim 4, wherein determining the currently used server node and the currently used middleware further comprises:

configuring a public IP address for all the server nodes;

and configuring floating IP addresses for all the server nodes.

7. The data high availability method for the Linux system according to claim 6, wherein another server node is selected from all server nodes as the currently used server node according to the floating IP address.

8. A data high availability apparatus for use in a Linux system, comprising: the monitoring system comprises a determining module, a first monitoring module and a second monitoring module; wherein,

the determining module is used for determining a currently used server node and currently used middleware;

the first monitoring module is used for monitoring whether the currently used server node fails or not, and if so, selecting another server node from all the server nodes as the currently used server node;

and the second monitoring module is used for monitoring whether the currently used middleware fails or not, and if so, selecting another middleware from all the middleware as the currently used middleware to ensure that the client interacts with normal data of the currently used server node in the distributed file system through the currently used middleware and the failover equipment.

9. The data high availability device for Linux system according to claim 8, further comprising: the first configuration module is used for determining a directory for mounting the distributed file system, configuring all the middleware and mounting all the middleware in the directory.

10. The data high availability device for Linux system according to claim 8, further comprising: and the second configuration module is used for configuring a public IP address for all the server nodes and configuring a floating IP address for all the server nodes.