Monitoring management service deployment method and device, electronic equipment and readable storage medium

Abstract

The invention discloses a monitoring management service deployment method and device, electronic equipment, a computer readable storage medium and a computer program product, and is applied to a distributed cluster system.The method comprises the steps that any cluster node in the distributed cluster system is selected as a target node, and a main monitoring management service is deployed on the target node; acquiring node information of other cluster nodes except the target node in the distributed cluster system through the main monitoring management service; determining other candidate fault domains except the fault domain where the target node is located in the distributed cluster system, and selecting an optimal node in each candidate fault domain according to the information of each node; and selecting a target optimal node from the optimal nodes according to a preset monitoring management service value, and deploying each slave monitoring management service on each target optimal node according to the master monitoring management service. According to the technical scheme, rapid, efficient, stable and accurate deployment of the cluster monitoring management service can be realized, and stable operation of the distributed cluster system is ensured.

Description

Technical Field

[0001] The present application relates to the technical field of distributed systems, and in particular to a monitoring management service deployment method, and also to a monitoring management service deployment device, an electronic device, and a computer-readable storage medium. Background Art

[0002] In traditional distributed cluster systems, such as distributed storage systems, the deployment and management of cluster monitoring and management services often rely on manual intervention. Before cluster deployment, the number of cluster monitoring and management services to be deployed must be determined, and multiple nodes corresponding to the cluster's fault domains must be selected for deployment. For smaller clusters, administrators can easily select specific nodes for cluster monitoring and management service instances, adjust the number of cluster monitoring and management services based on experience, and proactively scale cluster monitoring and management services up or down as needed.

[0003] However, as clusters grow in size and complexity, this administrator-only maintenance approach becomes increasingly difficult. While some existing approaches attempt to assist with the deployment of cluster monitoring and management services through simple scripts or automated tools, these approaches often lack a comprehensive understanding of the entire cluster environment. This can lead to cluster monitoring and management services being concentrated on nodes with poor overall performance, accelerating their performance degradation and impacting the stability of the entire distributed cluster system. Manual deployment and adjustment of cluster monitoring and management services in large clusters is not only labor-intensive and time-consuming, but also prone to human error, impacting system performance.

[0004] Therefore, how to implement faster, more efficient, stable and accurate deployment of cluster monitoring and management services in a distributed cluster system and ensure the stable operation of the distributed cluster system is an urgent problem to be solved by those skilled in the art. Summary of the Invention

[0005] The purpose of this application is to provide a monitoring and management service deployment method, which can realize faster, more efficient, stable and accurate deployment of cluster monitoring and management services in a distributed cluster system, and ensure the stable operation of the distributed cluster system; another purpose of this application is to provide a monitoring and management service deployment device, electronic device, computer-readable storage medium and computer program product, all of which have the above-mentioned beneficial effects.

[0006] In a first aspect, the present application provides a monitoring management service deployment method applied to a distributed cluster system, comprising:

[0007] Selecting any cluster node in the distributed cluster system as a target node, and deploying a master monitoring management service on the target node;

[0008] Obtaining node information of each of the cluster nodes other than the target node in the distributed cluster system through the main monitoring management service;

[0009] Determine, in the distributed cluster system, each candidate fault domain other than the fault domain where the target node is located, and select an optimal node in each candidate fault domain according to information of each node;

[0010] A target optimal node is selected from each of the optimal nodes according to a preset monitoring management service value, and each slave monitoring management service is deployed on each of the target optimal nodes according to the master monitoring management service.

[0011] Optionally, obtaining node information of each of the cluster nodes other than the target node in the distributed cluster system through the main monitoring management service includes:

[0012] Obtaining, through the main monitoring management service, hard disk life usage information of each cluster node other than the target node in the distributed cluster system as node information of the corresponding cluster node;

[0013] Accordingly, selecting the optimal node in each candidate fault domain according to the node information includes:

[0014] For each candidate fault domain, a cluster node with the longest disk service life is selected as the optimal node in the candidate fault domain according to the hard disk service life usage information of each cluster node in the candidate fault domain.

[0015] Optionally, selecting a target optimal node from the optimal nodes according to a preset monitoring management service value includes:

[0016] When the difference between the preset monitoring management service value and the target number of nodes is lower than the number of the optimal nodes, selecting the optimal nodes corresponding to the number of the difference from among all the optimal nodes according to the hard disk life usage information of each of the optimal nodes as the target optimal nodes;

[0017] When the difference between the preset monitoring management service value and the target number of nodes is equal to the number of the optimal nodes, all the optimal nodes are used as the target optimal nodes;

[0018] When the difference between the preset monitoring management service value and the target node number is higher than the number of the optimal nodes, remove the optimal nodes in each candidate fault domain, and return to the step of selecting the optimal node in each candidate fault domain according to the node information, until the optimal nodes corresponding to the difference are obtained as the target optimal nodes.

[0019] Optionally, an information collection tool is deployed on each cluster node in the distributed cluster system;

[0020] Accordingly, obtaining node information of each of the cluster nodes other than the target node in the distributed cluster system through the main monitoring management service includes:

[0021] issuing a node information acquisition instruction to each of the cluster nodes in the distributed cluster system except the target node through the main monitoring management service, so that each of the cluster nodes uses the information collection tool to collect the node information;

[0022] Receive the node information reported by each cluster node, and store the node information locally.

[0023] Optionally, the monitoring management service deployment method further includes:

[0024] Taking the target node and each of the target optimal nodes as actual deployment nodes, and detecting whether each of the actual deployment nodes is an actual optimal node in a corresponding fault domain at a first time interval;

[0025] If the actual deployment node is not the actual optimal node in the corresponding fault domain, a node replacement operation is performed to migrate the monitoring and management service on the actual deployment node to the actual optimal node.

[0026] Optionally, after performing a node swap operation to migrate the monitoring management service on the actual deployment node to the actual optimal node, the method further includes:

[0027] When the actual deployment node performing the node replacement operation includes the target node, obtaining monitoring management service configuration information on the target node;

[0028] The monitoring management service configuration information is updated to the actual optimal node corresponding to the target node.

[0029] Optionally, the monitoring management service deployment method further includes:

[0030] detecting, at a second time interval, whether the number of actually deployed nodes in the distributed cluster system meets the preset monitoring management service value;

[0031] When the number of the actual deployed nodes does not meet the preset monitoring management service value, a monitoring management service expansion operation or a monitoring management service reduction operation is performed according to the difference between the number of the actual deployed nodes and the preset monitoring management service value.

[0032] In a second aspect, the present application further discloses a monitoring management service deployment device, which is applied to a distributed cluster system, comprising:

[0033] A selection module, configured to select any cluster node in the distributed cluster system as a target node and deploy a main monitoring management service on the target node;

[0034] An acquisition module, configured to acquire node information of each of the cluster nodes other than the target node in the distributed cluster system through the main monitoring management service;

[0035] a determination module, configured to determine, in the distributed cluster system, other candidate fault domains except the fault domain where the target node is located, and select an optimal node from each candidate fault domain based on information about each node;

[0036] The deployment node is used to select a target optimal node from each of the optimal nodes according to a preset monitoring management service value, and deploy each slave monitoring management service on each of the target optimal nodes according to the master monitoring management service.

[0037] In a third aspect, the present application further discloses an electronic device, comprising:

[0038] memory for storing computer programs;

[0039] A processor is configured to implement the steps of any one of the monitoring management service deployment methods described above when executing the computer program.

[0040] In a fourth aspect, the present application further discloses a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of any one of the monitoring management service deployment methods described above are implemented.

[0041] In a fifth aspect, the present invention further discloses a computer program product, comprising a computer program / instruction, which, when executed by a processor, implements the steps of any one of the monitoring management service deployment methods described above.

[0042] The present application provides a monitoring and management service deployment method, which is applied to a distributed cluster system, including: selecting any cluster node as a target node in the distributed cluster system, and deploying a master monitoring and management service on the target node; obtaining node information of each cluster node other than the target node in the distributed cluster system through the master monitoring and management service; determining each candidate fault domain other than the fault domain where the target node is located in the distributed cluster system, and selecting an optimal node in each candidate fault domain based on the information of each node; selecting a target optimal node in each optimal node based on a preset monitoring and management service value, and deploying each slave monitoring and management service on each target optimal node based on the master monitoring and management service.

[0043] By applying the technical solution provided in this application, a cluster node is arbitrarily selected in a distributed cluster system to deploy a master monitoring and management service, and then the master monitoring and management service is used to realize the automatic deployment of other monitoring and management services (i.e., each slave monitoring and management service) in the distributed cluster system. The selection of the target optimal node can be realized by referring to the node information, fault domain division and preset monitoring and management service value of each cluster node in the distributed cluster system, so as to realize the deployment of each slave monitoring and management service at each target optimal node. In other words, by obtaining the information of each cluster node and the fault domain division, an effective perception of the overall environment of the distributed cluster system is realized, which can ensure that each monitoring and management service is deployed on the best cluster node in the distributed cluster system, and the entire implementation process can be realized automatically, getting rid of manual dependence and reducing the risk of human error. At the same time, the automation level of the system is improved, and the operation and maintenance cost of the deployment and management of monitoring and management services in the distributed cluster system is reduced. It can be seen that this technical solution can realize the deployment of cluster monitoring and management services in a faster, more efficient, more stable and more accurate manner in a distributed cluster system, further effectively ensuring the stable operation of the distributed cluster system.

[0044] In one embodiment of the present application, the distributed cluster system can also periodically detect the actual status of each cluster node, that is, regularly perceive changes in its own environment, so as to promptly perform node replacement operations when the system environment changes, thereby allowing the cluster monitoring and management services originally deployed on cluster nodes with poor performance to be replaced on cluster nodes with currently better performance, ensuring that each cluster monitoring and management service can always be deployed on high-quality nodes within the distributed cluster system, further improving the stability of the distributed cluster system.

[0045] The monitoring and management service deployment device, electronic device, computer-readable storage medium and computer program product provided in this application also have the above-mentioned technical effects, and this application will not repeat them here. BRIEF DESCRIPTION OF THE DRAWINGS

[0046] In order to more clearly illustrate the technical solutions in the prior art and the embodiments of the present application, the following is a brief introduction to the drawings required for describing the prior art and the embodiments of the present application. Of course, the drawings described below in connection with the embodiments of the present application are only part of the embodiments of the present application. For those skilled in the art, other drawings can be obtained based on the provided drawings without inventive effort, and the obtained other drawings also fall within the scope of protection of the present application.

[0047] Figure 1 A flowchart of a monitoring management service deployment method provided in this application;

[0048] Figure 2 A flowchart for implementing a node swap operation provided by this application;

[0049] Figure 3 A flowchart for implementing an expansion / contraction operation provided by this application;

[0050] Figure 4 This is a flowchart for implementing another expansion / contraction operation provided by this application;

[0051] Figure 5 A schematic diagram of the structure of a monitoring management service deployment device provided in this application;

[0052] Figure 6 This is a schematic diagram of the structure of an electronic device provided in this application. DETAILED DESCRIPTION

[0053] The core of this application is to provide a monitoring and management service deployment method, which can realize faster, more efficient, stable and accurate deployment of cluster monitoring and management services in a distributed cluster system, ensuring the stable operation of the distributed cluster system; another core of this application is to provide a monitoring and management service deployment device, electronic device, computer-readable storage medium and computer program product, all of which have the above-mentioned beneficial effects.

[0054] In order to describe the technical solutions in the embodiments of the present application more clearly and completely, the technical solutions in the embodiments of the present application will be introduced below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0055] An embodiment of the present application provides a monitoring management service deployment method.

[0056] Please refer to Figure 1 , Figure 1 This is a flow chart of a monitoring management service deployment method provided in this application. The monitoring management service deployment method can be applied to a distributed cluster system, including the following S101 to S104.

[0057] S101: Select any cluster node in the distributed cluster system as a target node, and deploy a main monitoring management service on the target node.

[0058] This step is intended to achieve effective deployment of the main monitoring and management service. It is understandable that in the process of executing the group monitoring and management service deployment operation on the distributed cluster system, the number of monitoring and management services that need to be deployed is generally multiple. However, in the embodiment of the present application, you can first arbitrarily select a cluster node in the distributed cluster system as the target node to deploy a main monitoring and management service. On this basis, you can use the main monitoring and management service to implement the deployment of other monitoring and management services (the slave monitoring and management services described below). In other words, by pre-deploying a main monitoring and management service, you can actively realize the automated deployment of all other monitoring and management services. Among them, the method of selecting the target node is not unique. It can be arbitrarily selected or selected with reference to preset conditions. This application does not limit this.

[0059] S102: Obtain node information of all cluster nodes except the target node in the distributed cluster system through the main monitoring management service.

[0060] This step aims to collect node information of each cluster node in the distributed cluster system, that is, the main monitoring and management service obtains the node information of each cluster node in the distributed cluster system except the target node, so as to effectively select cluster nodes that can be deployed from the monitoring and management service by referring to each node information. Among them, the node information is used to characterize the actual performance of the corresponding cluster node, so that high-quality nodes in the distributed cluster system can be screened to realize the deployment of the monitoring and management service. However, the data type of the node information is not unique. For example, it can be disk service life information, load capacity information, storage capacity information, etc. This application does not limit this.

[0061] In one embodiment of the present application, an information collection tool is deployed on each cluster node in the distributed cluster system. Accordingly, obtaining node information of each cluster node in the distributed cluster system other than the target node through the main monitoring management service may include:

[0062] Send node information acquisition instructions to other cluster nodes in the distributed cluster system except the target node through the main monitoring management service, so that other cluster nodes can use information collection tools to collect node information;

[0063] Receive node information reported by each cluster node and save the node information locally.

[0064] An embodiment of the present application provides a method for obtaining node information. Specifically, an information collection tool can be deployed on each cluster node in a distributed cluster system, and the target node deployed with the main monitoring and management service sends node information acquisition instructions to other cluster nodes in the distributed cluster system, so that each other cluster node can use the information collection tool deployed by itself to collect its own node information and actively upload it to the target node. Furthermore, the target node can also use local storage to actively save the information of each node, so that it can refer to this information later to achieve effective selection of cluster nodes that can be deployed from the monitoring and management service. Of course, the information of each node stored in the local storage of the target node can also be updated regularly according to actual conditions.

[0065] S103: Determine other candidate fault domains except the fault domain where the target node is located in the distributed cluster system, and select the best node in each candidate fault domain according to information of each node.

[0066] This step aims to achieve effective selection of the optimal node in each fault domain in the distributed cluster system. First, the main monitoring management service can pre-acquire the fault domain information of each cluster node in the distributed cluster system. This information is basic information in the distributed cluster system and can be directly obtained. Furthermore, in addition to the fault domain where the target node is located, for each other fault domain in the distributed cluster system (i.e., the candidate fault domain mentioned above), the optimal node selection can be achieved directly based on the node information of each cluster node in the corresponding fault domain. As mentioned above, the node information is used to characterize the actual performance of the corresponding cluster node. Correspondingly, the optimal node is the cluster node with the best actual performance in the corresponding candidate fault domain. The selection of the optimal node can be achieved based on the node information.

[0067] In one embodiment of the present application, obtaining, through the main monitoring management service, node information of each cluster node other than the target node in the distributed cluster system includes: obtaining, through the main monitoring management service, hard disk life usage information of each cluster node other than the target node in the distributed cluster system as the node information of the corresponding cluster node;

[0068] Accordingly, the optimal node is selected in each candidate fault domain according to the information of each node, including: for each candidate fault domain, the cluster node with the longest disk service life is selected as the optimal node in the candidate fault domain according to the hard disk life usage information of each cluster node in the candidate fault domain.

[0069] This embodiment of the present application provides a specific type of node information, namely, disk lifespan information. As can be appreciated, disk wear and tear is a major factor affecting the performance of distributed cluster systems. Therefore, disk lifespan information can be selected as node information to effectively select the optimal node within each candidate fault domain. In other words, within each candidate fault domain, the cluster node with the longest disk lifespan can be selected as the optimal node within that candidate fault domain.

[0070] S104: Select a target optimal node from each optimal node according to a preset monitoring management service value, and deploy each slave monitoring management service on each target optimal node according to the master monitoring management service.

[0071] This step is intended to achieve the selection of the target optimal node, and then achieve the effective deployment of each slave monitoring and management service on each target optimal node. As mentioned above, in the process of executing the group monitoring and management service deployment operation on the distributed cluster system, the number of monitoring and management services that need to be deployed is generally multiple, but the specific deployment number can be set in advance according to the actual situation of the distributed cluster system. Therefore, the target optimal node can be selected in each optimal node with reference to the preset monitoring and management service value, so as to deploy each slave monitoring and management service on each target optimal node. Among them, the preset monitoring and management service value is the total number of monitoring and management services that need to be deployed in the distributed cluster system.

[0072] In one embodiment of the present application, selecting a target optimal node from among the optimal nodes according to a preset monitoring management service value includes:

[0073] When the difference between the preset monitoring management service value and the target node number is lower than the number of optimal nodes, the optimal nodes corresponding to the difference are selected from all the optimal nodes according to the hard disk life usage information of each optimal node as the target optimal nodes;

[0074] When the difference between the preset monitoring management service value and the target node number is equal to the number of optimal nodes, all optimal nodes are used as target optimal nodes;

[0075] When the difference between the preset monitoring management service value and the target node number is higher than the number of optimal nodes, the optimal nodes in each candidate fault domain are removed, and the step of selecting the optimal node in each candidate fault domain according to the information of each node is returned until the optimal nodes corresponding to the difference are obtained as the target optimal nodes.

[0076] As described above, disk life usage information can be selected as node information to achieve effective selection of the optimal node within each candidate fault domain. On this basis, if the first round of optimal node selection can obtain the optimal nodes that meet the number of preset monitoring and management service values, then multiple optimal nodes with high disk lifespan rankings can be directly selected from these optimal nodes as target optimal nodes; if the first round of optimal node selection cannot obtain the optimal nodes that meet the number of preset monitoring and management service values, then the second round or even more rounds of optimal node selection can be continued with reference to the hard disk life usage information, until the optimal nodes that meet the number of preset monitoring and management service values ​​can be finally obtained as target optimal nodes.

[0077] It can be seen that the monitoring and management service deployment method provided in the embodiment of the present application selects any cluster node in the distributed cluster system to deploy the main monitoring and management service, and then uses the main monitoring and management service to realize the automatic deployment of other monitoring and management services (i.e., each slave monitoring and management service) in the distributed cluster system, wherein the target optimal node can be selected with reference to the node information, fault domain division and preset monitoring and management service value of each cluster node in the distributed cluster system, so as to realize the deployment of each slave monitoring and management service at each target optimal node. In other words, by obtaining the information of each cluster node and the fault domain division, an effective perception of the overall environment of the distributed cluster system is achieved, which can ensure that each monitoring and management service is deployed on the best cluster node in the distributed cluster system, and the entire implementation process can be realized automatically, getting rid of manual dependence, reducing the risk of human error, and at the same time improving the automation level of the system and reducing the operation and maintenance cost of monitoring and management service deployment and management in the distributed cluster system. It can be seen that the present technical solution can realize the deployment of cluster monitoring and management services in a faster, more efficient, more stable and more accurate manner in the distributed cluster system, further effectively ensuring the stable operation of the distributed cluster system.

[0078] Based on the above embodiments:

[0079] In one embodiment of the present application, the monitoring management service deployment method may further include:

[0080] Taking the target node and each target optimal node as the actual deployment node, and detecting whether each actual deployment node is the actual optimal node in the corresponding fault domain at a first time interval;

[0081] If the actual deployment node is not the actual optimal node in the corresponding fault domain, a node swap operation is performed to migrate the monitoring and management service on the actual deployment node to the actual optimal node.

[0082] It is understandable that as the distributed cluster system continues to run, the performance of each cluster node within it is also constantly changing. Cluster nodes that originally had better performance may experience performance degradation, and cluster nodes that originally had poorer performance may also experience performance improvement. Therefore, the distributed cluster system can regularly detect the actual conditions of each cluster node within it, that is, regularly and repeatedly obtain the node information of each cluster node to determine whether the cluster node currently deployed with the monitoring and management service is the best node in the corresponding fault domain. If it is the best node, no processing is required and the system continues to wait for the next detection cycle to arrive. If it is not the best node, the best node in the corresponding fault domain can be reselected to perform the node replacement operation, so that the monitoring and management service can be migrated to the best node. It should be noted that the specific value of the above-mentioned first time interval does not affect the implementation of this technical solution. It can be set according to actual needs, and this application does not limit this.

[0083] It can be seen that in the embodiment of the present application, the distributed cluster system can also regularly detect the actual situation of each cluster node, that is, regularly perceive changes in its own environment, so as to perform node replacement operations in a timely manner when the system environment changes, thereby being able to replace the cluster monitoring and management services originally deployed on the cluster nodes with poor performance to the cluster nodes with better performance, ensuring that each cluster monitoring and management service can always be deployed on high-quality nodes within the distributed cluster system, further improving the stability of the distributed cluster system.

[0084] Furthermore, after the above-mentioned node replacement operation is performed to migrate the monitoring and management service on the actual deployment node to the actual optimal node, it can also include: when the actual deployment node on which the node replacement operation is performed includes the target node, obtaining the monitoring and management service configuration information on the target node; and updating the monitoring and management service configuration information to the actual optimal node corresponding to the target node.

[0085] It is understandable that the cluster node where the node performance change occurs may also be the target node where the main monitoring and management service is deployed. Since the main monitoring and management service in the target node is the first monitoring and management service deployed in the distributed cluster system, and the selection of the target optimal node and the automatic deployment of each slave monitoring and management service are realized based on the main monitoring and management service, the full amount of basic configuration information of the distributed cluster system should be saved, that is, the above-mentioned monitoring and management service configuration information. However, since the main monitoring and management service has replaced the new cluster node, the monitoring and management service configuration information can be further updated from the original target node to the new cluster node where the main monitoring and management service is deployed, that is, the synchronous migration of the monitoring and management service configuration information and the main monitoring and management service is realized.

[0086] In one embodiment of the present application, the monitoring management service deployment method may further include:

[0087] detecting, at a second time interval, whether the number of actually deployed nodes in the distributed cluster system meets a preset monitoring management service value;

[0088] When the number of actually deployed nodes does not meet the preset monitoring management service value, a monitoring management service expansion operation or a monitoring management service reduction operation is performed according to the difference between the number of actually deployed nodes and the preset monitoring management service value.

[0089] In order to effectively ensure the normal operation of each monitoring and management service in the distributed cluster system, the number of monitoring and management services actually deployed in the distributed cluster system can be regularly detected, so that when the actual number of deployed monitoring and management services does not meet the preset monitoring and management service value, the monitoring and management service expansion operation is performed, and when the actual number of deployed monitoring and management services exceeds the preset monitoring and management service value, the monitoring and management service reduction operation is performed. Among them, the expansion operation refers to continuing to select new best-quality nodes for the deployment of monitoring and management services in the distributed cluster system until the actual number of deployed monitoring and management services is equal to the preset monitoring and management service value; the reduction operation refers to selecting the worst-quality nodes in the cluster nodes where monitoring and management services are deployed and deleting the monitoring and management services deployed thereon until the actual number of deployed monitoring and management services is equal to the preset monitoring and management service value. Similarly, the specific value of the second time interval mentioned above does not affect the implementation of this technical solution, and can be set according to actual needs. This application does not limit this.

[0090] Furthermore, before performing the monitoring management service expansion operation or the monitoring management service reduction operation according to the difference between the number of actually deployed nodes and the preset monitoring management service value, the following may also be included:

[0091] Determine whether the number of detections on the actual deployed nodes reaches a preset threshold;

[0092] When the number of detections does not reach the preset threshold, returning to the step of detecting whether the number of actually deployed nodes in the distributed cluster system meets the preset monitoring management service value according to the second time interval;

[0093] When the number of detections reaches a preset threshold, the step of performing a monitoring management service expansion operation or a monitoring management service reduction operation is executed according to the difference between the number of actual deployed nodes and the preset monitoring management service value.

[0094] In an embodiment of the present application, in order to effectively ensure the accuracy of expansion and reduction operations, that is, to ensure that the actual number of deployed monitoring and management services is equal to the preset monitoring and management service value, a multi-round detection mechanism can be set to avoid the problem of inaccurate expansion or reduction operations caused by inaccurate detection results in one round, thereby further ensuring the stability of the distributed cluster system.

[0095] Based on the above embodiments, the present invention provides another monitoring management service deployment method. The implementation process of the monitoring management service deployment method provided in the present invention may include the following steps.

[0096] 1. Cluster node information collection.

[0097] 1. Implement an information collection tool that can obtain the hard disk life information of the corresponding cluster node according to instructions;

[0098] 2. The information collection tool is deployed on each cluster node in the distributed cluster system;

[0099] 3. The main monitoring management service completes a round of information collection for all nodes every day. The collection task can be spread over the day according to the number of cluster nodes.

[0100] 4. The main monitoring management service calls the information collection tool on each cluster node through remote calls to obtain the reported information;

[0101] 5. The main monitoring management service will persist the collected node information and keep a copy in memory for subsequent policy use.

[0102] 2. The monitoring and management service independently selects new nodes for deploying the monitoring and management service.

[0103] 1. The monitoring management service itself has saved the information about the fault domain to which each cluster node belongs. This information is the basic information of the distributed cluster system.

[0104] 2. All fault domains are selected as candidate fault domains;

[0105] 3. Remove the fault domain where the primary monitoring management service has been deployed from the candidate fault domains;

[0106] 4. Select the optimal node within each fault domain from the candidate fault domains. Currently, the cluster node with the longest hard drive life within the fault domain is the optimal node.

[0107] 5. Select the best node (target best node) from the best nodes in each candidate fault domain. The selection method is the same as the selection method for the best node in the fault domain.

[0108] 6. The optimal node finally obtained is the newly added node.

[0109] 3. The monitoring and management service independently chooses to reduce nodes.

[0110] 1. Each cluster node where monitoring and management services have been deployed is considered as a node to be reduced;

[0111] 2. Select the worst node from the nodes to be reduced. Currently, the cluster node with the shortest hard drive life is selected as the worst node.

[0112] 3. Use the worst node as the reduction node.

[0113] 4. The monitoring and management service autonomously triggers the node replacement operation.

[0114] Please refer to Figure 2 , Figure 2 This is a flowchart for implementing a node swap operation provided in this application, and its implementation process may include:

[0115] 1. The monitoring management service periodically performs node replacement operations;

[0116] 2. Determine whether the cluster node where the monitoring and management service is deployed is the optimal node in this fault domain;

[0117] 3. If there is a cluster node with monitoring and management services deployed that is not the optimal node in this fault domain, this cluster node will be used as the node to be scaled down.

[0118] 4. If all nodes are optimal, the worst node is selected according to the monitoring and management service's autonomous selection of node reduction strategy (step 3), and the optimal node is selected according to the monitoring and management service's autonomous selection of new nodes for deploying the monitoring and management service (step 2).

[0119] 5. If the worst node is still the best node after comparing it to the best node, the process ends and no node swap is triggered. If not, the worst node becomes the node to be scaled down.

[0120] 6. Initiate scaling down for the selected nodes to be scaled down;

[0121] 7. After the reduction is completed, the monitoring management service will detect that the number of surviving monitoring management services is inconsistent with the preset value (preset monitoring management service value), and will automatically initiate the monitoring management service expansion process.

[0122] 5. The monitoring management service automatically triggers expansion / reduction operations.

[0123] Please refer to Figure 3 , Figure 3 This is a flowchart for implementing an expansion / contraction operation provided in this application. The implementation process may include:

[0124] 1. The monitoring management service periodically checks whether the number of currently surviving monitoring management services is consistent with the preset value;

[0125] 2. When the actual quantity is consistent with the preset value, the number of inconsistency checks is reset and the next round of checks is awaited;

[0126] 3. When the actual number is inconsistent with the preset value, the number of inconsistent checks will be counted. If the threshold is not met, the next round of checks will be waited for;

[0127] 4. When the number of inconsistency checks reaches the threshold, the node scaling action is triggered;

[0128] 5. When the actual number is greater than the preset value, the node to be reduced is selected according to the monitoring management service's autonomous node reduction strategy (step 3), and then the reduction action is initiated for the node to be reduced;

[0129] 6. When the actual number is less than the preset value, the node to be expanded is selected according to the strategy of the monitoring management service for autonomously selecting new nodes for deploying the monitoring management service (step 2), and then the expansion action is initiated for the node to be expanded.

[0130] 6. The monitoring and management service autonomously triggers expansion / contraction operations on the master node (the cluster node where the master monitoring and management service is located).

[0131] Please refer to Figure 4 , Figure 4 This is another implementation flow chart of the expansion / contraction operation provided in this application, and its implementation process may include:

[0132] 1. Implement single-point expansion and contraction processing tools for monitoring and management services;

[0133] 2. Capacity expansion and contraction processing tools are deployed on each cluster node;

[0134] 3. When initiating a capacity expansion action, the monitoring management service calls the capacity expansion tool on the node to be expanded through remote calling to complete the capacity expansion on the cluster node;

[0135] 4. When initiating a scaling-down action, if the node to be scaled down is a master node with a master monitoring management service deployed, directly call the local scaling-down tool;

[0136] 5. When initiating a scaling-down action, if the node to be scaled down is not the master node where the master monitoring management service is deployed, the scaling-down tool is called on the node to be scaled down through remote calling to complete the scaling-down on the node;

[0137] 6. After completing the scaling-in / scaling action, the newly selected master monitoring management service will update the current management monitoring service configuration information to the cluster configuration files of all cluster nodes in the cluster.

[0138] Combining steps 1 to 6 above, the deployment process of the monitoring management service is as follows:

[0139] 1. Randomly select a cluster node from all cluster nodes of the distributed cluster system to be deployed as the cluster node where the main monitoring management service is located, that is, the master node, and complete the deployment of a main monitoring management service on the master node;

[0140] 2. After cluster deployment is complete, perform fault domain division. After fault domain division is completed, bind the monitoring and management service to the fault domain;

[0141] 3. Adjust the preset values ​​of the monitoring and management service according to the deployment requirements, or you can set the preset values ​​of the monitoring and management service independently;

[0142] 4. The monitoring and management service completes the automated deployment of other monitoring and management services through the process of autonomous expansion / contraction.

[0143] It can be seen that the monitoring and management service deployment method provided in the embodiment of the present application selects any cluster node in the distributed cluster system to deploy the main monitoring and management service, and then uses the main monitoring and management service to realize the automatic deployment of other monitoring and management services (i.e., each slave monitoring and management service) in the distributed cluster system, wherein the target optimal node can be selected with reference to the node information, fault domain division and preset monitoring and management service value of each cluster node in the distributed cluster system, so as to realize the deployment of each slave monitoring and management service at each target optimal node. In other words, by obtaining the information of each cluster node and the fault domain division, an effective perception of the overall environment of the distributed cluster system is achieved, which can ensure that each monitoring and management service is deployed on the best cluster node in the distributed cluster system, and the entire implementation process can be realized automatically, getting rid of manual dependence, reducing the risk of human error, and at the same time improving the automation level of the system and reducing the operation and maintenance cost of monitoring and management service deployment and management in the distributed cluster system. It can be seen that the present technical solution can realize the deployment of cluster monitoring and management services in a faster, more efficient, more stable and more accurate manner in the distributed cluster system, further effectively ensuring the stable operation of the distributed cluster system.

[0144] An embodiment of the present application provides a monitoring management service deployment device.

[0145] Please refer to Figure 5 , Figure 5This is a schematic diagram of the structure of a monitoring management service deployment device provided by this application. The monitoring management service deployment device can be applied to a distributed cluster system, including:

[0146] Selection module 1 is used to select any cluster node as a target node in the distributed cluster system and deploy the main monitoring management service on the target node;

[0147] Acquisition module 2, used to obtain node information of each cluster node other than the target node in the distributed cluster system through the main monitoring management service;

[0148] Determination module 3, used to determine other candidate fault domains except the fault domain where the target node is located in the distributed cluster system, and select the best node in each candidate fault domain based on the information of each node;

[0149] The deployment node 4 is used to select a target optimal node from each optimal node according to a preset monitoring management service value, and deploy each slave monitoring management service on each target optimal node according to the master monitoring management service.

[0150] It can be seen that the monitoring and management service deployment device provided in the embodiment of the present application selects any cluster node in the distributed cluster system to deploy the main monitoring and management service, and then uses the main monitoring and management service to realize the automatic deployment of other monitoring and management services (i.e., each slave monitoring and management service) in the distributed cluster system, wherein the node information, fault domain division and preset monitoring and management service value of each cluster node in the distributed cluster system can be referred to to realize the selection of the target optimal node, so as to realize the deployment of each slave monitoring and management service at each target optimal node. In other words, by obtaining the information of each cluster node and the fault domain division, an effective perception of the overall environment of the distributed cluster system is realized, which can ensure that each monitoring and management service is deployed on the best cluster node in the distributed cluster system, and the entire implementation process can be realized automatically, getting rid of manual dependence, reducing the risk brought by human error, and at the same time improving the automation level of the system and reducing the operation and maintenance cost of the deployment and management of monitoring and management services in the distributed cluster system. It can be seen that the present technical solution can realize the deployment of cluster monitoring and management services in a faster, more efficient, more stable and more accurate manner in the distributed cluster system, further effectively ensuring the stable operation of the distributed cluster system.

[0151] In one embodiment of the present application, the acquisition module 2 may be specifically configured to acquire, through the main monitoring management service, hard disk life usage information of each cluster node other than the target node in the distributed cluster system as node information of the corresponding cluster node;

[0152] Accordingly, the determination module 3 may be specifically configured to select, for each candidate fault domain, a cluster node with the longest disk lifespan as the optimal node in the candidate fault domain according to the disk lifespan usage information of each cluster node in the candidate fault domain.

[0153] In one embodiment of the present application, the above-mentioned deployment node 4 can specifically select the optimal nodes corresponding to the difference from all the optimal nodes as the target optimal nodes according to the hard disk life usage information of each optimal node when the difference between the preset monitoring management service value and the target number of nodes is lower than the number of nodes of the optimal node; when the difference between the preset monitoring management service value and the target number of nodes is equal to the number of nodes of the optimal node, all the optimal nodes are used as the target optimal nodes; when the difference between the preset monitoring management service value and the target number of nodes is higher than the number of nodes of the optimal node, the optimal nodes in each candidate fault domain are removed, and the step of selecting the optimal node in each candidate fault domain according to the information of each node is returned until the optimal nodes corresponding to the difference are obtained as the target optimal nodes.

[0154] In one embodiment of the present application, an information collection tool is deployed on each cluster node in the distributed cluster system; accordingly, the above-mentioned acquisition module 2 can be specifically used to issue node information acquisition instructions to other cluster nodes in the distributed cluster system except the target node through the main monitoring management service, so that other cluster nodes can use the information collection tool to collect node information; receive each node information reported by each cluster node, and locally save each node information.

[0155] In one embodiment of the present application, the monitoring and management service deployment device may also include a first detection module, which is used to take the target node and each target optimal node as the actual deployment node, and detect whether each actual deployment node is the actual optimal node in the corresponding fault domain according to a first time interval; if the actual deployment node is not the actual optimal node in the corresponding fault domain, a node replacement operation is performed to migrate the monitoring and management service on the actual deployment node to the actual optimal node.

[0156] In one embodiment of the present application, the monitoring and management service deployment device may also include an update module, which is used to obtain the monitoring and management service configuration information on the target node after the above-mentioned node replacement operation is performed to migrate the monitoring and management service on the actual deployment node to the actual optimal node, when the actual deployment node performing the node replacement operation includes the target node; and update the monitoring and management service configuration information to the actual optimal node corresponding to the target node.

[0157] In one embodiment of the present application, the monitoring management service deployment device may also include a second detection module for detecting whether the number of actual deployed nodes in the distributed cluster system meets the preset monitoring management service value according to a second time interval; when the number of actual deployed nodes does not meet the preset monitoring management service value, a monitoring management service expansion operation or a monitoring management service reduction operation is performed based on the difference between the number of actual deployed nodes and the preset monitoring management service value.

[0158] For an introduction to the apparatus provided in the embodiments of this application, please refer to the above method embodiments, which will not be elaborated in this application.

[0159] An embodiment of the present application provides an electronic device.

[0160] Please refer to Figure 6 , Figure 6 This is a schematic diagram of the structure of an electronic device provided in this application, which may include:

[0161] Memory 11, for storing computer programs;

[0162] The processor 10 can implement the steps of any of the above-mentioned monitoring management service deployment methods when executing a computer program.

[0163] like Figure 6 FIG2 is a schematic diagram of the structure of an electronic device, which may include a processor 10, a memory 11, a communication interface 12, and a communication bus 13. The processor 10, the memory 11, and the communication interface 12 communicate with each other via the communication bus 13.

[0164] In the embodiment of the present application, the processor 10 may be a central processing unit (CPU), an application-specific integrated circuit, a digital signal processor, a field programmable gate array, or other programmable logic device. The processor 10 may call a program stored in the memory 11. Specifically, the processor 10 may perform the operations in the embodiment of the monitoring management service deployment method.

[0165] The memory 11 is used to store one or more programs. The program may include program code, and the program code includes computer operating instructions. In the embodiment of the present application, the memory 11 stores at least a program for implementing the following functions:

[0166] Select any cluster node in the distributed cluster system as the target node and deploy the main monitoring management service on the target node;

[0167] Obtain node information of all cluster nodes except the target node in the distributed cluster system through the main monitoring management service;

[0168] Determine other candidate fault domains in the distributed cluster system except the fault domain where the target node is located, and select the best node in each candidate fault domain based on the information of each node;

[0169] The target optimal node is selected from each optimal node according to the preset monitoring management service value, and each slave monitoring management service is deployed on each target optimal node according to the master monitoring management service.

[0170] In one possible implementation, the memory 11 may include a program storage area and a data storage area. The program storage area may store an operating system and at least one application required for a function, and the data storage area may store data created during use. Furthermore, the memory 11 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device or other volatile solid-state storage device.

[0171] The communication interface 12 may be an interface of a communication module, and is used to connect to other devices or systems.

[0172] Of course, it needs to be explained that Figure 6 The structure shown does not constitute a limitation on the electronic device in the embodiment of the present application. In actual applications, the electronic device may include Figure 6 More or fewer components than shown, or combinations of certain components.

[0173] An embodiment of the present application provides a computer-readable storage medium.

[0174] The computer-readable storage medium provided in the embodiment of the present application stores a computer program, and when the computer program is executed by a processor, the steps of any of the above-mentioned monitoring management service deployment methods can be implemented.

[0175] Among them, computer-readable storage media can be any available medium that can be stored by a computer or a data storage device such as a server or data center that integrates one or more available media. For example, it can be magnetic media (such as floppy disks, hard disks, tapes, etc.), optical media (such as DVDs) or semiconductor media (such as solid-state drives) and other media that can store computer program codes.

[0176] For an introduction to the computer-readable storage medium provided in the embodiments of the present application, please refer to the above method embodiments, and this application will not elaborate on them here.

[0177] An embodiment of the present application provides a computer program product.

[0178] The computer program product provided in the embodiments of the present application includes a computer program / instruction, which, when executed by a processor, can implement the steps of any of the above-mentioned monitoring management service deployment methods.

[0179] Specifically, in each of the above embodiments, all or part of the embodiments may be implemented through software, hardware, firmware, or any combination thereof. When implemented through software, all or part of the embodiments may be implemented in the form of a computer program product.

[0180] Among them, the computer program product may include one or more computer programs / instructions, which, when loaded and executed on a computer, may generate, in whole or in part, the processes or functions described in the embodiments of the present application. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. Computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line, etc.) or wireless (e.g., infrared, wireless, microwave, etc.) method.

[0181] For an introduction to the computer program product provided in the embodiments of the present application, please refer to the above method embodiments, which will not be elaborated in this application.

[0182] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. Reference can be made to the common and similar parts between the various embodiments. For the devices disclosed in the embodiments, since they correspond to the methods disclosed in the embodiments, the description is relatively simple, and the relevant parts can be referred to the method description.

[0183] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0184] The steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be implemented directly using hardware, a software module executed by a processor, or a combination of the two. The software module may be placed in random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.

[0185] The technical solution provided by the present application is described in detail above. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only intended to help understand the method and core ideas of the present application. It should be noted that, for those skilled in the art, without departing from the principles of the present application, several improvements and modifications may be made to the present application, and these improvements and modifications also fall within the scope of protection of the present application.

Claims

1. A monitoring management service deployment method, characterized in that: Applied to distributed cluster systems, including: Selecting any cluster node in the distributed cluster system as a target node, and deploying a master monitoring management service on the target node; Obtaining node information of each of the cluster nodes other than the target node in the distributed cluster system through the main monitoring management service; Determine, in the distributed cluster system, each candidate fault domain other than the fault domain where the target node is located, and select an optimal node in each candidate fault domain according to information of each node; A target optimal node is selected from each of the optimal nodes according to a preset monitoring management service value, and each slave monitoring management service is deployed on each of the target optimal nodes according to the master monitoring management service.

2. The monitoring management service deployment method according to claim 1, characterized in that: Obtaining node information of each of the cluster nodes other than the target node in the distributed cluster system through the main monitoring management service includes: Obtaining, through the main monitoring management service, hard disk life usage information of each cluster node other than the target node in the distributed cluster system as node information of the corresponding cluster node; Accordingly, selecting the optimal node in each candidate fault domain according to the node information includes: For each candidate fault domain, a cluster node with the longest disk service life is selected as the optimal node in the candidate fault domain according to the hard disk service life usage information of each cluster node in the candidate fault domain.

3. The monitoring management service deployment method according to claim 2, characterized in that: Selecting a target optimal node from the optimal nodes according to a preset monitoring management service value includes: When the difference between the preset monitoring management service value and the target number of nodes is lower than the number of the optimal nodes, selecting the optimal nodes corresponding to the number of the difference from among all the optimal nodes according to the hard disk life usage information of each of the optimal nodes as the target optimal nodes; When the difference between the preset monitoring management service value and the target number of nodes is equal to the number of the optimal nodes, all the optimal nodes are used as the target optimal nodes; When the difference between the preset monitoring management service value and the target node number is higher than the number of the optimal nodes, remove the optimal nodes in each candidate fault domain, and return to the step of selecting the optimal node in each candidate fault domain according to the node information, until the optimal nodes corresponding to the difference are obtained as the target optimal nodes.

4. The monitoring management service deployment method according to claim 1, characterized in that: An information collection tool is deployed on each cluster node in the distributed cluster system; Accordingly, obtaining node information of each of the cluster nodes other than the target node in the distributed cluster system through the main monitoring management service includes: issuing a node information acquisition instruction to each of the cluster nodes in the distributed cluster system except the target node through the main monitoring management service, so that each of the cluster nodes uses the information collection tool to collect the node information; Receive the node information reported by each cluster node, and store the node information locally.

5. The monitoring management service deployment method according to any one of claims 1 to 4, characterized in that: Also includes: Taking the target node and each of the target optimal nodes as actual deployment nodes, and detecting whether each of the actual deployment nodes is an actual optimal node in a corresponding fault domain at a first time interval; If the actual deployment node is not the actual optimal node in the corresponding fault domain, a node replacement operation is performed to migrate the monitoring and management service on the actual deployment node to the actual optimal node.

6. The monitoring management service deployment method according to claim 5, characterized in that: After performing a node swap operation to migrate the monitoring management service on the actual deployment node to the actual optimal node, the method further includes: When the actual deployment node performing the node replacement operation includes the target node, obtaining monitoring management service configuration information on the target node; The monitoring management service configuration information is updated to the actual optimal node corresponding to the target node.

7. The monitoring management service deployment method according to claim 5, characterized in that: Also includes: detecting, at a second time interval, whether the number of actually deployed nodes in the distributed cluster system meets the preset monitoring management service value; When the number of the actual deployed nodes does not meet the preset monitoring management service value, a monitoring management service expansion operation or a monitoring management service reduction operation is performed according to the difference between the number of the actual deployed nodes and the preset monitoring management service value.

8. A monitoring management service deployment device, characterized in that: Applied to distributed cluster systems, including: A selection module, configured to select any cluster node in the distributed cluster system as a target node and deploy a main monitoring management service on the target node; An acquisition module, configured to acquire node information of each of the cluster nodes other than the target node in the distributed cluster system through the main monitoring management service; a determination module, configured to determine, in the distributed cluster system, other candidate fault domains except the fault domain where the target node is located, and select an optimal node from each candidate fault domain based on information about each node; The deployment node is used to select a target optimal node from each of the optimal nodes according to a preset monitoring management service value, and deploy each slave monitoring management service on each of the target optimal nodes according to the master monitoring management service.

9. An electronic device, characterized in that: include: memory for storing computer programs; A processor is configured to implement the steps of the monitoring management service deployment method according to any one of claims 1 to 7 when executing the computer program.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the monitoring management service deployment method according to any one of claims 1 to 7 are implemented.

Images