A cluster mode configuration management method and system

Abstract

The application provides a cluster mode configuration management method, comprising the following steps: configuring one of a plurality of device nodes in a cluster as a master device, and configuring other device nodes as slave devices; the master device establishes a connection with the slave devices through a built-in relay; when the master device receives a configuration request from a user, a general configuration message is obtained by preprocessing; then, it is judged whether the configuration message is a configuration message of the master device itself: if yes, the master device configures according to the configuration message; if no, the master device issues the configuration message to the corresponding slave device through a publish-subscribe mode, and the slave device configures according to the configuration message. Advantageous effects: only the high-performance master device needs to receive and respond to the Web UI request of the user, and there is no need to cache the request, the master device sends the request to other device nodes in the cluster in real time for processing, thereby reducing the burden of other device nodes, ensuring the accuracy and consistency of the configuration information, and improving the performance and efficiency of the system.

Description

Technical Field

[0001] This invention relates to the field of cluster configuration management technology, and in particular to a configuration management method and system for cluster mode. Background Technology

[0002] Cluster mode is an architectural pattern that connects multiple computers or server devices together to form a unified pool of computing resources. In cluster mode, multiple computer devices can work together to process tasks, providing higher computing power and availability.

[0003] Cluster configuration management refers to the process of uniformly managing and adjusting the configurations of various device nodes within a cluster. The purpose of configuration management is to ensure that all nodes in the cluster have the same configuration, thereby achieving high availability and performance optimization for the cluster.

[0004] Current configuration management methods rely on a web user interface (UI) to manage cluster device nodes. Typically, each device node in the cluster handles configurations from the web UI via its own command-line tool (http-server) and Common Gateway Interface (CGI). This approach requires each device node to maintain a complete web UI process, and the configuration takes effect after a lengthy page access process. This consumes significant space resources and reduces operational efficiency, increasing the cost of network deployment for enterprises or individuals, and negatively impacting economic value and user experience.

[0005] The known solution is for the master device in the cluster to accept configuration requests from the web UI, cache these requests, and then periodically synchronize the configuration to other device nodes within the cluster. However, this approach has some drawbacks: for example, the amount of configuration data synchronized each time is relatively large, leading to untimely synchronization; and when the master device in the cluster switches, the configuration management of the entire cluster becomes complex. Summary of the Invention

[0006] To address the above technical problems, this invention provides a configuration management method and system in cluster mode.

[0007] The technical problem solved by this invention can be achieved by the following technical solutions:

[0008] A cluster-mode configuration management method includes:

[0009] Step S1: Configure one of the multiple device nodes in the cluster as the master device and the other device nodes as slave devices;

[0010] Step S2: The master device establishes a connection with the slave device in the cluster by activating the built-in relay for message distribution;

[0011] Step S3: When the master device receives a configuration request from the user, it preprocesses the configuration request to obtain a general configuration message.

[0012] Step S4: Determine whether the message is the configuration message of the main device itself.

[0013] If so, the master device configures itself according to the preprocessed configuration message;

[0014] If not, the master device will send the preprocessed configuration message to the corresponding slave device through a publish-subscribe pattern, and the slave device will perform configuration according to the received configuration message.

[0015] Preferably, it further includes:

[0016] Step S5: After the master device is switched, the relay is turned off in the original master device and started in the new master device. The new master device re-establishes a connection with the slave device in the cluster through the relay.

[0017] Preferably, the functional modules of each device node include: a web server, a message processing module, a publishing module, a subscription module, a relay, a unified configuration management interface, a flow module, and a storage module;

[0018] The web server is used to receive the configuration request from the user; the message processing module is used to process the configuration request and extract it to the flow module for corresponding operations; the publishing module and the subscription module establish a connection through a relay to publish or subscribe to the configuration message; the unified configuration management interface is used to configure according to the configuration message; the storage module is used to store the configuration file generated by the configuration.

[0019] Step S1 includes:

[0020] The web server, message processing module, publishing module, and relay are shut down in the slave device, and the remaining functional modules are started; and

[0021] In the main device, disable the subscription module and enable the remaining functional modules.

[0022] Preferably, step S2 includes:

[0023] The relay of the master device establishes connections with the publishing module of the master device and the subscription module of the slave device, respectively.

[0024] Preferably, step S3 includes:

[0025] When the master device receives a configuration request from the user, it preprocesses the configuration request through the message processing module and converts it into a general configuration message.

[0026] The present invention also provides a cluster-mode configuration management system for implementing the cluster-mode configuration management method described above, comprising:

[0027] The device configuration module is used to configure one of the device nodes in the cluster as a master device and the other device nodes as slave devices.

[0028] The main device includes:

[0029] A connection establishment module is used by the master device to establish a connection with the slave device in the cluster by activating a built-in relay for message distribution;

[0030] The preprocessing module is used to preprocess the configuration request received from the user when the master device receives the configuration request, obtain a general configuration message, determine whether it is the configuration message of the master device itself, and obtain a determination result;

[0031] A configuration module, connected to the preprocessing module, is used to configure the main device according to the preprocessed configuration message when the judgment result determines that it is the configuration message of the main device itself;

[0032] The distribution module, connected to the preprocessing module, is used to, when the judgment result determines that the configuration message is not from the master device itself, allow the master device to distribute the preprocessed configuration message to the corresponding slave device via a publish-subscribe pattern.

[0033] The slave device performs configuration based on the received configuration message.

[0034] Preferably, the device configuration module further includes:

[0035] A switching unit is used to shut down the relay in the original master device and start the relay in the new master device after the master device is switched. The new master device re-establishes a connection with the slave device in the cluster through the relay.

[0036] Preferably, the functional modules of each device node include: a web server, a message processing module, a publishing module, a subscription module, a relay, a unified configuration management interface, a flow module, and a storage module;

[0037] The web server is used to receive the configuration request from the user; the message processing module is used to process the configuration request and extract it to the flow module for corresponding operations; the publishing module and the subscription module establish a connection through a relay to publish or subscribe to the configuration message; the unified configuration management interface is used to configure according to the configuration message; and the storage module is used to store the configuration file generated by the configuration.

[0038] Preferably, the device configuration module includes:

[0039] The first configuration unit is used to shut down the web server, the message processing module, the publishing module, and the relay in the slave device, and start the remaining functional modules.

[0040] The second configuration unit is used to disable the subscription module and start the remaining functional modules in the main device.

[0041] Preferably, in the connection establishment module, the relay of the master device establishes connections with the publishing module of the master device and the subscription module of the slave device, respectively.

[0042] The advantages or beneficial effects of the technical solution of this invention are as follows:

[0043] This invention only requires the high-performance master device to receive and respond to user Web UI requests. The master device then sends configuration messages to other device nodes in the cluster, eliminating the need for all device nodes to process Web UI requests, thus reducing the burden on other device nodes and ensuring the accuracy and consistency of configuration information. The master device does not need to cache Web UI configuration requests. When it receives a Web UI configuration request, it sends it to other device nodes in the cluster in real time for processing, and the changes take effect immediately on other device nodes in the cluster, improving the system's performance and efficiency. Attached Figure Description

[0044] Figure 1 In a preferred embodiment of the present invention, a structural topology diagram of device nodes in cluster mode is shown.

[0045] Figure 2 In a preferred embodiment of the present invention, the structural topology diagram is shown when the device nodes are configured as master devices and slave devices;

[0046] Figure 3 This is a flowchart illustrating the configuration management method in cluster mode, as shown in a preferred embodiment of the present invention.

[0047] Figure 4 This is a schematic diagram of the process after the master device is switched in a preferred embodiment of the present invention;

[0048] Figure 5 This is a structural block diagram of a cluster-mode configuration management system in a preferred embodiment of the present invention.

[0049] Figure 6 This is a structural block diagram illustrating the specific implementation of the device configuration module in a preferred embodiment of the present invention.

[0050] Figure 7 This is a structural block diagram illustrating the specific implementation of the device configuration module in a preferred embodiment of the present invention. Detailed Implementation

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

[0052] It should be noted that, unless otherwise specified, the embodiments and features described in the present invention can be combined with each other.

[0053] The present invention will be further described below with reference to the accompanying drawings and specific embodiments, but this is not intended to limit the scope of the invention.

[0054] In this embodiment of the invention, the cluster mode includes multiple device nodes 10. For example... Figure 1 As shown, the functional modules of each device node 10 include: web server 100, message processing module 101, publishing module 102, subscription module 103, relay 104, unified configuration management interface 105, flow module 106 and storage module 107.

[0055] The web server 100 is used to receive configuration requests from users; the message processing module 101 is used to process configuration requests and extract them to the flow module 106 for corresponding operations; the publishing module 102 and the subscription module 103 establish a connection through the relay 104 to publish or subscribe to configuration messages; the unified configuration management interface 105 is used to configure according to the configuration messages; the flow module 106 includes modules A, B, C, etc., which perform different operations; and the storage module 107 is used to store the configuration files generated by the configuration.

[0056] like Figure 2As shown, when device node 10 in the cluster is configured as master device 20, the subscription module 103 in device node 10 is turned off, and all other functional modules are started.

[0057] Master device 20, acting as the manager in cluster mode, has the following functions:

[0058] Web server 100 starts the network service (web server), general gateway interface CGI and other related processes, and is responsible for handling all configuration requests for the web user interface (web UI);

[0059] The message processing module 101 processes messages from the web UI through the unified configuration management interface 105 and extracts them into the flow module 106 to execute the corresponding module operations.

[0060] Relay 104 starts the broker message middleware, and the master device 20 and the slave device 30 establish a message connection through the broker to publish messages;

[0061] The publishing module 102 establishes a connection with the broker, allowing the master device 20 to publish configuration messages;

[0062] Subscribing to module 103 does not establish a connection with the broker. The master device 20 does not need to subscribe to configuration messages and directly handles the configuration requests of the web UI through the master device 20 itself.

[0063] The unified configuration management interface 105 adopts the App-MGR application manager interface, which is a tool or service for managing and monitoring applications. It provides functions such as application deployment, startup, shutdown, and monitoring to help administrators better manage applications in the cluster.

[0064] Storage module 107 is used for the system to save configuration files.

[0065] Furthermore, when device node 10 in the cluster is not configured as the master device 20, i.e., device node 10 is a slave device 30 (or a regular device root node), the web server 100, message processing module 101, publishing module 102, and relay 104 in device node 10 are shut down, while the remaining functional modules are started. The unified configuration management interface 105, flow module 106, and storage module 107 have the same functions as those of the master device 20, and will not be described again here. Slave device 30 also has the following functions:

[0066] Web server 100 shuts down all web server-related processes and does not process web user interface (webUI) configuration requests.

[0067] The message processing module 101 does not need to process messages from the web UI;

[0068] Relay 104, disable the broker message middleware;

[0069] The publishing module 102 does not establish a connection with the broker, and the slave device 30 does not need to publish configuration messages;

[0070] The subscription module 103 establishes a connection with the broker of the master device 20 to subscribe to messages; it subscribes to configuration messages published by the master device 20. Since the master device 20 has already performed unified web UI message processing, the slave device 30 can directly use the subscribed configuration messages and extract them through the unified configuration management interface 105 to the flow module 106 to execute the corresponding module operations.

[0071] See Figure 3 In a preferred embodiment of the present invention, based on the above-mentioned problems existing in the prior art, a cluster mode configuration management method is provided, comprising:

[0072] Step S1: Configure one of the multiple device nodes 10 in the cluster as the master device 20, and configure the other device nodes 10 as slave devices 30.

[0073] In step S2, the master device 20 establishes a connection with the slave device 30 in the cluster by activating the built-in relay 104 for message distribution.

[0074] Step S3: When the master device 20 receives a configuration request from the user, it preprocesses the configuration request to obtain a general configuration message.

[0075] Step S4: Determine if it is a configuration message from the master device 20 itself.

[0076] If so, the master device 20 will configure itself according to the preprocessed configuration message;

[0077] If not, the master device 20 will send the preprocessed configuration message to the corresponding slave device 30 through the publish-subscribe mode, and the slave device 30 will configure according to the received configuration message.

[0078] Specifically, in this embodiment, after the master and slave devices 30 are configured on each device node 10 in the cluster, real-time configuration message distribution in the cluster is achieved through the relay 104 (broker) established in the master device 20. The specific steps are as follows: During cluster mode startup, the master device 20 starts the message distribution relay 104; the sending configuration program of the master device 20 establishes a connection with the relay 104 of the master device 20, and at the same time, the receiving configuration program of the slave device 30 also establishes a connection with the relay 104; when a configuration request is passed from the web UI, it is processed by the http-server and general gateway interface CGI of the master device 20 and converted into a configuration message for other devices. If it is a configuration message of the master device 20 itself, the master device 20 directly processes the configuration; if it is determined that it is a configuration message that needs to be sent to other device nodes 10 in the cluster, the master device 20 forwards it through the connection established by the relay 104 using a publish-subscribe method; the corresponding slave device 30 in the cluster receives the configuration message and performs configuration processing.

[0079] This configuration management approach eliminates the need for caching Web UI configurations. Instead, it transforms configuration requests into generic configurations in real-time via a unified configuration interface and sends them directly to other devices in the cluster for processing, thus achieving real-time effectiveness. Furthermore, even after a switchover of the master device 20 in the cluster, connections between devices can be quickly re-established, ensuring users are unaware of these configuration management changes.

[0080] In a preferred embodiment, such as Figure 4 As shown, it also includes:

[0081] Step S5: After the master device 20 is switched, the relay 104 is turned off in the original master device 20 and the relay 104 is turned on in the new master device 20. The new master device 20 re-establishes a connection with the slave device 30 in the cluster through the relay 104.

[0082] Specifically, in this embodiment, when the master device 20 in the cluster is switched, firstly, the relay 104 needs to be shut down in the original master device 20 to ensure that the original master device 20 no longer handles any communication with the slave device 30, and to free up resources for the new master device 20; next, the relay 104 is started in the new master device 20, and the new master device 20 re-establishes a connection with the slave device 30 in the cluster through the relay 104, so that communication between each device node 10 in the cluster can be quickly re-established, and the user can continue to use the system normally without any interference, and will be completely unaware of the changes in configuration management.

[0083] In a preferred embodiment, step S1 includes:

[0084] Shutting down the web server 100, message processing module 101, publishing module 102, and relay 104 from device 30, and starting the remaining functional modules; and

[0085] In the main device 20, disable the subscription module 103 and enable the remaining functional modules.

[0086] Specifically, in this embodiment, multiple device nodes 10 in the cluster are configured to configure the master device 20 and slave devices 30. One of the device nodes 10 in the cluster is configured as the master device 20. That is, the subscription module 103 is turned off in the master device 20, and the other functional modules, such as the web server 100, message processing module 101, publishing module 102, relay 104, unified configuration management interface 105, flow module 106 and storage module 107, are started. The master device 20 realizes the reception of Web UI requests, unified message processing and the publication of configuration messages. When the Web UI requests the configuration of the master device 20 itself, the corresponding configuration management is performed; otherwise, the configuration message is published to the corresponding slave device 30.

[0087] Furthermore, all other device nodes 10 are configured as slave devices 30. Specifically, slave devices 30 have functional modules such as the subscription module 103, the unified configuration management interface 105, the flow module 106, and the storage module 107 enabled. Slave devices 30 only need to perform configuration management directly after subscribing to configuration messages. In some implementations, the web server 100, message processing module 101, publishing module 102, and relay 104 are disabled in slave devices 30. By disabling unused functional modules, the energy consumption of slave devices 30 can be reduced, the device's lifespan extended, and the device's performance improved, while also simplifying the user interface.

[0088] Furthermore, during the subsequent master-slave device 30 switchover process, the master-slave device 30 can be configured by turning off or on some corresponding functional modules.

[0089] In a preferred embodiment, step S2 includes:

[0090] The repeater 104 of the master device 20 establishes connections with the publishing module 102 of the master device 20 and the subscription module 103 of the slave device 30, respectively.

[0091] Specifically, in this embodiment, a broker 104 is established in the master device 20. The broker 104 is connected to the sending configuration program in the publishing module 102 of the master device 20 to realize message publishing of the master device 20. At the same time, the broker 104 is connected to the receiving configuration program of the subscription module 103 of all slave devices 30 in the cluster to realize message subscription of the slave devices 30, thereby realizing real-time distribution of configuration messages in the cluster.

[0092] In a preferred embodiment, step S3 includes:

[0093] When the master device 20 receives a configuration request from the user, it preprocesses the configuration request through the message processing module 101 and converts it into a general configuration message.

[0094] In some implementations, embodiments of the present invention employ a unified web UI message processing and configuration interface management model. The master device 20 centrally processes all web UI requests and transforms them into configuration messages that can be directly used by all device nodes 10 in the cluster. The advantage of this implementation is that other devices in the cluster do not need to occupy memory space and system processing time to process web UI requests, thereby improving the overall system efficiency.

[0095] Meanwhile, the system of this invention employs a unified configuration management interface 105. After receiving Web UI messages, the master device 20 transforms them into concise configuration messages through the unified configuration management interface 105, greatly improving the efficiency of message transmission within the cluster. The configuration message also extracts the message's flow path within the system, module 106, and performs corresponding query and modification operations, enabling direct configuration management of the module. This configuration management mode not only improves the real-time performance of configuration management applications but also enhances the user experience.

[0096] See Figure 5 The present invention also provides a cluster-mode configuration management system for implementing the cluster-mode configuration management method described above, comprising:

[0097] The device configuration module 40 is used to configure one of the multiple device nodes 10 in the cluster as the master device 20, and the other device nodes 10 as slave devices 30.

[0098] The main equipment 20 includes:

[0099] The connection establishment module 201 is used by the master device 20 to establish a connection with the slave device 30 in the cluster by starting the built-in relay 104 for message distribution.

[0100] The preprocessing module 202 is used to preprocess the configuration request when the master device 20 receives the configuration request from the user, obtain a general configuration message, determine whether it is the configuration message of the master device 20 itself, and obtain the determination result.

[0101] Configuration module 203, connected to preprocessing module 202, is used to configure the master device 20 according to the preprocessed configuration message when the judgment result determines that it is a configuration message of the master device 20 itself;

[0102] The distribution module 204 is connected to the preprocessing module 202. When the judgment result determines that the message is not a configuration message of the master device 20 itself, the master device 20 distributes the preprocessed configuration message to the corresponding slave device 30 through the publish-subscribe mode, and the slave device 30 performs configuration according to the received configuration message.

[0103] In a preferred embodiment, such as Figure 6 As shown, the device configuration module 40 also includes:

[0104] The switching unit 401 is used to shut down the relay 104 in the original master device 20 and start the relay 104 in the new master device 20 after the master device 20 is switched. The new master device 20 re-establishes a connection with the slave device 30 in the cluster through the relay 104.

[0105] In a preferred embodiment, such as Figure 7 As shown, the device configuration module 40 includes:

[0106] The first configuration unit 402 is used to shut down the web server 100, message processing module 101, publishing module 102 and relay 104 in the slave device 30, and start the remaining functional modules.

[0107] The second configuration unit 403 is used to disable the subscription module 103 and start the remaining functional modules in the main device 20.

[0108] In some implementations, the configuration of master and slave devices can be automated to enable and disable corresponding functional modules in device node 10, thus configuring the master and slave devices. As an example, and not a limitation, each device node 10 may be configured with a master mode and a slave mode. In master mode, the subscription module 103 in device node 10 is disabled, while all other functional modules are enabled. In slave mode, the web server 100, message processing module 101, publishing module 102, and relay 104 in device node 10 are disabled, while all other functional modules are enabled. By switching modes, the corresponding functions are automatically enabled and disabled.

[0109] In some implementations, after a switchover of the master device, the automation mechanism can automatically shut down the repeater of the original master device and start the repeater in the new master device, ensuring the accuracy and efficiency of the operation.

[0110] In a preferred embodiment, in the connection establishment module 201, the repeater 104 of the master device 20 establishes connections with the publishing module 102 of the master device 20 and the subscription module 103 of the slave device 30, respectively.

[0111] Further implementation details of this system have been disclosed and will not be repeated in this embodiment.

[0112] The advantages or beneficial effects of adopting the above technical solution are as follows: This invention only needs to receive and respond to the user's Web UI request on a high-performance master device, and then the master device sends the configuration message to other device nodes in the cluster. It does not require all device nodes to process the Web UI request, which reduces the burden on other device nodes, while ensuring the accuracy and consistency of the configuration information. The master device does not need to cache the Web UI configuration request. When it receives the Web UI configuration request, it sends it to other device nodes in the cluster in real time for processing, and it takes effect immediately on other device nodes in the cluster, which improves the performance and efficiency of the system.

[0113] The above are merely preferred embodiments of the present invention and are not intended to limit the implementation methods and protection scope of the present invention. Those skilled in the art should recognize that any equivalent substitutions and obvious changes made using the content of this specification and illustrations should be included within the protection scope of the present invention.

Claims

1. A configuration management method in cluster mode, characterized in that, include: Step S1: Configure one of the multiple device nodes in the cluster as the master device and the other device nodes as slave devices; Step S2: The master device establishes a connection with the slave device in the cluster by activating the built-in relay for message distribution; Step S3: When the master device receives a configuration request from the user, it preprocesses the configuration request to obtain a general configuration message; wherein, the configuration request is a Web UI request, and the Web UI request is only received and responded to on the master device; Step S4: Determine whether the message is the configuration message of the main device itself. If so, the master device configures itself according to the preprocessed configuration message; If not, the master device will send the preprocessed configuration message to the corresponding slave device through a publish-subscribe pattern, and the slave device will perform configuration according to the received configuration message.

2. The cluster mode configuration management method according to claim 1, characterized in that, Also includes: Step S5: After the master device is switched, the relay is turned off in the original master device and started in the new master device. The new master device re-establishes a connection with the slave device in the cluster through the relay.

3. The cluster mode configuration management method according to claim 1, characterized in that, Each of the device nodes includes the following functional modules: web server, message processing module, publishing module, subscription module, relay, unified configuration management interface, flow module, and storage module. The web server is used to receive the configuration request from the user; the message processing module is used to process the configuration request and extract it to the flow module for corresponding operations; the publishing module and the subscription module establish a connection through a relay to publish or subscribe to the configuration message; the unified configuration management interface is used to configure according to the configuration message; the storage module is used to store the configuration file generated by the configuration. Step S1 includes: The web server, message processing module, publishing module, and relay are shut down in the slave device, and the remaining functional modules are started; and In the main device, disable the subscription module and enable the remaining functional modules.

4. The cluster mode configuration management method according to claim 3, characterized in that, Step S2 includes: The relay of the master device establishes connections with the publishing module of the master device and the subscription module of the slave device, respectively.

5. The cluster mode configuration management method according to claim 3, characterized in that, Step S3 includes: When the master device receives a configuration request from the user, it preprocesses the configuration request through the message processing module and converts it into a general configuration message.

6. A cluster-mode configuration management system, characterized in that, A configuration management method for implementing the cluster mode as described in any one of claims 1-5, comprising: The device configuration module is used to configure one of the device nodes in the cluster as a master device and the other device nodes as slave devices. The main device includes: A connection establishment module is used by the master device to establish a connection with the slave device in the cluster by activating a built-in relay for message distribution; The preprocessing module is used to preprocess the configuration request received from the user when the master device receives the configuration request, obtain a general configuration message, determine whether it is the configuration message of the master device itself, and obtain a determination result; A configuration module, connected to the preprocessing module, is used to configure the main device according to the preprocessed configuration message when the judgment result determines that it is the configuration message of the main device itself; The distribution module, connected to the preprocessing module, is used to, when the judgment result determines that the configuration message is not the configuration message of the master device itself, the master device distributes the preprocessed configuration message to the corresponding slave device through a publish-subscribe mode, and the slave device performs configuration according to the received configuration message.

7. The cluster-mode configuration management system according to claim 6, characterized in that, The device configuration module also includes: A switching unit is used to shut down the relay in the original master device and start the relay in the new master device after the master device is switched. The new master device re-establishes a connection with the slave device in the cluster through the relay.

8. The cluster-mode configuration management system according to claim 6, characterized in that, Each of the device nodes includes the following functional modules: web server, message processing module, publishing module, subscription module, relay, unified configuration management interface, flow module, and storage module. The web server is used to receive the configuration request from the user; the message processing module is used to process the configuration request and extract it to the flow module for corresponding operations; the publishing module and the subscription module establish a connection through a relay to publish or subscribe to the configuration message; the unified configuration management interface is used to configure according to the configuration message; and the storage module is used to store the configuration file generated by the configuration.

9. The cluster-mode configuration management system according to claim 8, characterized in that, The device configuration module includes: The first configuration unit is used to shut down the web server, the message processing module, the publishing module, and the relay in the slave device, and start the remaining functional modules. The second configuration unit is used to disable the subscription module and start the remaining functional modules in the main device.

10. The cluster-mode configuration management system according to claim 8, characterized in that, In the connection establishment module, the relay of the master device establishes connections with the publishing module of the master device and the subscription module of the slave device, respectively.

Images