Node upgrading control method and electronic equipment

Abstract

The invention discloses a node upgrading control method and electronic equipment, and relates to the technical field of computers, and the node upgrading control method comprises the following steps: starting an upgrading process of a cluster system in response to a received upgrading command of a specified object; when the upgrading mode adopted by the cluster system is the first upgrading mode and the next batch of the current batch exists in the at least two batches, responding to completion of node upgrading of the current batch, pausing an upgrading process and starting a timer; under the condition that an upgrading pause instruction of the specified object is received before the timing time of the timer ends, stopping the timer, and waiting for receiving an upgrading continuing command; according to the node upgrading control method and device, under the condition that the first continuous upgrading command of the specified object is received, the upgrading process is recovered, and the next batch of nodes are upgraded, so that the technical problem of insufficient flexibility of a node upgrading control method in the related technology is solved, and the technical effect of improving the flexibility of node upgrading control is achieved.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, and particularly relates to a node upgrade control method and electronic equipment. BACKGROUND

[0002] With the rapid development of information technology, distributed systems, especially cluster computing systems (such as server clusters, storage clusters, database clusters, etc.) play an indispensable role in key fields such as enterprise-level applications, cloud computing, big data processing, etc. In order to guarantee the security, stability and performance optimization of the system, the cluster system needs to be upgraded regularly in terms of software version, patch update or configuration change. In the upgrading process, in order to avoid the entire cluster being unavailable due to large-scale nodes being upgraded at the same time, batch upgrading is usually adopted, and there is a fixed intermediate interval time before upgrading of different batches, which is used for relevant personnel to check the upgrading results of the previous batch or to check the upgrading environment of the next batch.

[0003] However, in the related art, the intermediate interval time is preset and fixed, and lacks flexibility when facing a cluster system with complex upgrading environment. For example, if the upgrading environment of the next batch of nodes is relatively simple, the relevant personnel can complete the check quickly but still need to wait for the same long intermediate interval time, resulting in time waste; or if the upgrading environment of the next batch of nodes is relatively complex, the relevant personnel need to spend a relatively long time for checking but only have the same long intermediate interval time, resulting in insufficient time. As can be seen, the node upgrade control method in the related art has the problem of insufficient flexibility. SUMMARY

[0004] The present application provides a node upgrade control method and electronic equipment to at least solve the problem of insufficient flexibility of the node upgrade control method in the related art.

[0005] The application provides a node upgrade control method, comprising: in response to receiving an upgrade command of a specified object, starting an upgrade process of a cluster system, wherein nodes to be upgraded in the cluster system are divided into at least two batches, and the upgrade process is used to upgrade the nodes to be upgraded in the cluster system according to the batches to which the nodes belong; in the case that an upgrade mode adopted by the cluster system is a first upgrade mode and there is a next batch of the at least two batches in a current batch, in response to the nodes in the current batch being upgraded, suspending the upgrade process and starting a timer, wherein the first upgrade mode is an upgrade mode in which the upgrade time of nodes in different batches is controlled by the timer, and the timing time of the timer is positively correlated with the environment complexity of the nodes in the next batch; in the case that a pause upgrade instruction of the specified object is received before the timing time of the timer ends, stopping the timer and waiting for receiving a continue upgrade command; in the case that a first continue upgrade command of the specified object is received, resuming the upgrade process and upgrading the nodes in the next batch.

[0006] The application further provides a node upgrade control device, comprising: a first starting unit configured to, in response to receiving an upgrade command of a specified object, start an upgrade process of a cluster system, wherein nodes to be upgraded in the cluster system are divided into at least two batches, and the upgrade process is used to upgrade the nodes to be upgraded in the cluster system according to the batches to which the nodes belong; a first execution unit configured to, in the case that an upgrade mode adopted by the cluster system is a first upgrade mode and there is a next batch of the at least two batches in a current batch, in response to the nodes in the current batch being upgraded, suspend the upgrade process and start a timer, wherein the first upgrade mode is an upgrade mode in which the upgrade time of nodes in different batches is controlled by the timer, and the timing time of the timer is positively correlated with the environment complexity of the nodes in the next batch; a second execution unit configured to, in the case that a pause upgrade instruction of the specified object is received before the timing time of the timer ends, stop the timer and wait for receiving a continue upgrade command; and a third execution unit configured to, in the case that a first continue upgrade command of the specified object is received, resume the upgrade process and upgrade the nodes in the next batch.

[0007] The application further provides an electronic device, comprising: a memory configured to store a computer program; and a processor configured to implement the steps of any of the above node upgrade control methods when executing the computer program.

[0008] The application further provides a computer readable storage medium, wherein the computer readable storage medium stores a computer program, and the computer program is executed by a processor to implement the steps of any of the above node upgrade control methods.

[0009] The application further provides a computer program product comprising a computer program which, when executed by a processor, implements the steps of any of the node upgrade control methods described above.

[0010] According to the application, in response to receiving an upgrade command of a specified object, an upgrade process of a cluster system is started, wherein the nodes to be upgraded in the cluster system are divided into at least two batches, and the upgrade process is used to upgrade the nodes to be upgraded in the cluster system according to the batches to which the nodes belong; in the case where the upgrade mode adopted by the cluster system is a first upgrade mode and there is a next batch of the at least two batches, in response to the completion of the node upgrade of the current batch, the upgrade process is suspended, and a timer is started, wherein the first upgrade mode is an upgrade mode in which the upgrade time of the nodes of different batches is controlled by the timer, and the timing time of the timer is positively correlated with the environment complexity of the deployment of the nodes of the next batch; in the case where a pause upgrade instruction of the specified object is received before the timing time of the timer ends, the timer is stopped, and the reception of a continue upgrade command is waited for; in the case where a first continue upgrade command of the specified object is received, the upgrade process is resumed, and the nodes of the next batch are upgraded. Since the timing time of the timer for controlling the upgrade time of the nodes of the next batch in the first upgrade mode is positively correlated with the environment complexity of the deployment of the nodes, the waiting time can be adaptively adjusted for different deployment environments, and the user can also freely control the upgrade start time of the nodes of the next batch through the pause upgrade instruction and the first continue upgrade command, thereby solving the technical problem of insufficient flexibility of the node upgrade control method in the related art, and achieving the technical effect of improving the flexibility of node upgrade control. BRIEF DESCRIPTION OF DRAWINGS

[0011] In order to more clearly illustrate the embodiments of the application, the drawings required to be used in the embodiments will be briefly introduced. Obviously, the drawings in the following description are only some embodiments of the application, and other drawings can be obtained by those skilled in the art without creative labor.

[0012] Figure 1 is a hardware structure block diagram of a node upgrade control method according to an embodiment of the application.

[0013] Figure 2 is a flowchart of an optional node upgrade control method according to an embodiment of the application.

[0014] Figure 3 is a flowchart of the initial setting of an optional node upgrade control method according to an embodiment of the application.

[0015] Figure 4is a flowchart of an upgrade cycle process of an optional node upgrade control method according to an embodiment of the present application.

[0016] Figure 5 is a flowchart of an upgrade check of an optional node upgrade control method according to an embodiment of the present application.

[0017] Figure 6 is a flowchart of an exception handling of an optional node upgrade control method according to an embodiment of the present application.

[0018] Figure 7 is a structural block diagram of an optional node upgrade control apparatus according to an embodiment of the present application. DETAILED DESCRIPTION

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

[0020] It should be noted that, in the description of the present application, the terms “comprise”, “contain” or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device comprising a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or device. The terms “first”, “second” and the like in the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence.

[0021] In order for those skilled in the art to better understand the present application, the present application will be further described in detail below with reference to the drawings and specific embodiments.

[0022] In combination with the specific application environment architecture or specific hardware architecture on which the node upgrade control method is executed, the specific application environment architecture or specific hardware architecture is described here.

[0023] The method embodiments provided in the embodiments of the present application can be executed in a server device or similar computing apparatus. Taking the case of running on a server device, Figure 1 is a hardware structural block diagram of the node upgrade control method of the embodiments of the present application. As Figure 1 shown, the server device can include one or more ( Figure 1The server device shown in FIG. 1 includes only one processor 102 (the processor 102 can include, but is not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA), and a memory 104 for storing data. The server device can further include a transmission device 106 for communication functions, and an input / output device 108. Those skilled in the art can understand that the server device can further include more or less components than those shown in FIG. 1, or have a different configuration from that shown in FIG. 1. Figure 1 The structure shown in FIG. 1 is only schematic, and does not limit the structure of the server device. For example, the server device can further include more or less components than those shown in FIG. 1, or have a different configuration from that shown in FIG. 1. Figure 1 For example, the server device can further include more or less components than those shown in FIG. 1, or have a different configuration from that shown in FIG. 1. Figure 1 For example, the server device can further include more or less components than those shown in FIG. 1, or have a different configuration from that shown in FIG. 1.

[0024] The memory 104 can be used to store computer programs, such as software programs of application software and modules, such as a computer program corresponding to the node upgrade control method in the embodiments of the present application. The processor 102 can execute various functional applications and data processing by running the computer programs stored in the memory 104, i.e., implement the method described above. The memory 104 can include a high-speed random access memory, and can further include a non-volatile memory, such as one or more magnetic storage devices, a flash memory, or other non-volatile solid-state memories. In some examples, the memory 104 can further include a memory remotely arranged with respect to the processor 102, and the remote memory can be connected to the server device through a network. Examples of the network can include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0025] The transmission device 106 is used to receive or send data via a network. Specific examples of the network can include a wireless network provided by a communication service provider of the server device. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, NIC) which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (Radio Frequency, RF) module which is used to communicate with the Internet in a wireless manner.

[0026] Embodiments of the present application provide a node upgrade control method, by setting a first upgrade mode and a second upgrade mode, in the first upgrade mode, after a batch of nodes is upgraded, the upgrade process is automatically paused until a continue-upgrade instruction is received to upgrade the next batch of nodes; in the second upgrade mode, after the timing time of the timer ends, the next batch of nodes is automatically upgraded, the timing time of the timer can be automatically configured based on the upgrade environment complexity of the next batch of nodes, and the upgrade process can be paused in response to the pause-upgrade instruction until a continue-upgrade instruction is received to upgrade the next batch of nodes, the user can freely select the upgrade mode or pause the upgrade at any time according to the actual situation during the upgrade process, and the effect of improving the flexibility of node upgrade control can be achieved.

[0027] In the present embodiment, a node upgrade control method is provided, Figure 2 is a flowchart of the node upgrade control method according to the embodiments of the present application, as Figure 2 shown, the method comprises steps S202, S204, S206 and S208.

[0028] Step S202, in response to receiving an upgrade command of a specified object, starting the upgrade process of the cluster system, wherein the nodes to be upgraded in the cluster system are divided into at least two batches, and the upgrade process is used to upgrade the nodes to be upgraded in the cluster system according to the batch to which they belong;

[0029] Step S204, in the case that the upgrade mode adopted by the cluster system is the first upgrade mode, and there is a next batch of nodes in the at least two batches, in response to the completion of the upgrade of the nodes in the current batch, pausing the upgrade process and starting a timer, wherein the first upgrade mode is an upgrade mode in which the upgrade time of different batches of nodes is controlled by a timer, and the timing time of the timer is positively correlated with the environment complexity of the deployment of the nodes in the next batch;

[0030] Step S206, in the case that a pause-upgrade instruction of a specified object is received before the timing time of the timer ends, stopping the timer and waiting to receive a continue-upgrade command;

[0031] Step S208, in the case that a first continue-upgrade command of a specified object is received, resuming the upgrade process and upgrading the nodes in the next batch.

[0032] The node upgrade control method in the embodiment can be applied to the field of computer technology and applied to the scene of batch upgrading of a cluster system. The cluster system (such as a server cluster, a storage cluster, a database cluster, etc.) is a kind of distributed system, which is a network composed of multiple independent computers or devices. These devices can be connected and work cooperatively through a communication network, and can share computing resources, storage resources, data and files, etc. to achieve common tasks and goals. The distributed system appears as a unified system image to the outside. The cluster system is a special form of the distributed system, mainly used to improve system performance, availability and scalability. The cluster system is usually composed of a group of closely coupled computers, which share the same network and storage resources and appear as a more powerful computer to the outside.

[0033] In order to ensure the security, stability and performance optimization of the system, the cluster system needs to be upgraded regularly, such as software version upgrade, patch update or configuration change. In the upgrading process, in order to avoid the unavailability of the entire cluster due to the simultaneous upgrade of a large number of nodes, a batch upgrade method is usually used, that is, the nodes in the cluster are divided into several batches, each batch contains multiple nodes to be upgraded in the cluster, and the cluster system is upgraded batch by batch.

[0034] In related technologies, in order to improve the intelligent level of cluster system upgrade, the upgrade process is usually automatically controlled by a computer program, and there is a fixed intermediate interval time before the upgrade of different batches, which is used for relevant personnel to check the upgrade results of the previous batch or check the upgrade environment of the next batch. After the end of the intermediate interval time, the upgrade of the next batch of nodes will be automatically started.

[0035] However, the above intermediate interval time in related technologies is preset and fixed, which lacks flexibility when facing a cluster system with complex upgrade environment. Users cannot externally modify or dynamically adjust the length of this interval time according to actual conditions (such as checking complexity, number of hosts, problem solving speed), nor can they manually end or start the waiting timer in advance. For example, if the upgrade environment of the next batch of nodes is relatively simple, the number of hosts is small, the check is simple or the required state can be quickly restored, the relevant personnel can quickly complete the upgrade preparation of the next batch of nodes, but still need to wait for the same long intermediate interval time, which will cause unnecessary time waste and prolong the overall upgrade period. Or the upgrade environment of the next batch of nodes is relatively complex, or the host connection state or volume dependency state does not meet the upgrade requirements during the check, and the relevant personnel need to spend a long time to check or repair the problem, but only the same long intermediate interval time leads to insufficient time, which may eventually cause business interruption due to the failure to complete the problem repair. As can be seen, the node upgrade control method in related technologies has the problem of insufficient flexibility.

[0036] To at least partially solve the above technical problems, in the embodiment, a first upgrade mode is provided in the upgrade process of the cluster system. Different from the fixed intermediate interval time in the related art, a timer is started after the upgrade of a batch of nodes is completed, and the timing time of the timer is positively correlated with the complexity of the environment in which the next batch of nodes is deployed, or the user can stop the timer by a pause upgrade instruction, until the user completes the upgrade preparation of the next batch of nodes and gives a first continue upgrade command to start the upgrade of the next batch of nodes. The cluster system can adaptively adjust the timing time of the timer based on the complexity of the deployment environment, and the user can flexibly control the upgrade timing of the next batch of nodes according to the actual demand, thereby improving the flexibility of node upgrade control.

[0037] In the embodiment, in response to receiving an upgrade command of a specified object, an upgrade process of the cluster system is started, wherein the nodes to be upgraded in the cluster system are divided into at least two batches, and the upgrade process is used to upgrade the nodes to be upgraded in the cluster system according to the batch to which the nodes belong. Optionally, the specified object can be a user, and the upgrade command can be given by the user in real time or automatically triggered at a predetermined time. Before the upgrade command is given, the resources required by the upgrade process of the cluster system have been configured, and the upgrade resources are controlled and scheduled by a state machine to upgrade the cluster system in the upgrade process. Before starting the upgrade process of the cluster system, in order to avoid the entire cluster being unavailable due to the simultaneous upgrade of a large number of nodes, the nodes to be upgraded in the cluster system can be divided into at least two batches. Optionally, the number of batches or the number of nodes in each batch can be specified, and the nodes to be upgraded in the cluster system are automatically divided according to the specified number, or the user divides the nodes to be upgraded in the cluster system according to the demand, or the complexity of the environment in which the nodes in each batch are deployed is specified to ensure that the nodes in each batch have similar environmental complexity. The embodiment does not limit this.

[0038] In the case where the upgrade mode adopted by the cluster system is the first upgrade mode and there is a next batch of nodes in the at least two batches, in response to the completion of the upgrade of the nodes in the current batch, the upgrade process is paused, and a timer is started, wherein the first upgrade mode is an upgrade mode in which the upgrade timing of different batches of nodes is controlled by a timer, and the timing time of the timer is positively correlated with the complexity of the environment in which the next batch of nodes is deployed. Here, there is a next batch of nodes in the at least two batches, that is, the nodes in the current batch are not the last batch of nodes. In the case where there is a next batch of nodes in the at least two batches other than the current batch, the upgrade of all the nodes to be upgraded in the cluster system is completed after the upgrade of the nodes in the current batch is completed, and there is no need to upgrade the next batch of nodes.

[0039] Optionally, the timing time of the timer can be based on a preset initial timing time, and the environment complexity of the next batch of node deployment can be increased or decreased on the preset initial timing time, or a model can be deployed, which can be trained based on the time consumption data of users completing the upgrade preparation of the next batch of nodes in the upgrade record of the historical cluster system, and the model is used to automatically set different timing times for different batches based on the environment complexity or other characteristics, so as to ensure that the timing time conforms to the actual upgrade environment and improve the flexibility of upgrade control.

[0040] Here, the timing time of the timer is positively correlated with the environment complexity of the next batch of node deployment, that is, if the environment complexity of the next batch of node deployment is high, a longer timing time can be configured to give the user sufficient time to check; if the environment complexity of the next batch of node deployment is low, a shorter timing time can be configured to reduce the redundant waiting time after the user completes the check and prevent time waste.

[0041] In the case that the specified object receives the pause upgrade instruction before the timing time of the timer ends, the timer is stopped, and the reception of the continue upgrade command is waited. Before the upgrade of the next batch of nodes is performed, the user may check that there is an unexpected problem to be repaired. In order to avoid the timing time of the timer being insufficient to repair the problem, causing business interruption caused by check delay, in the embodiment, the user can input the pause upgrade command, and the cluster system can stop the timer in response to the pause upgrade command until the user completes the repair of the problem and gives the first continue upgrade command. In the case that the first continue upgrade command of the specified object is received, the upgrade process is resumed, and the next batch of nodes is upgraded.

[0042] It should be noted that the above stopping of the timer means that the timer is not started again before the next batch of nodes is upgraded. Only in the case that the first continue upgrade command is received, the upgrade process is resumed, the next batch of nodes is upgraded, the user has sufficient time to check and repair the problem, and the upgrade is continued after the completion is confirmed. After the upgrade of the next batch of nodes is completed, the timer can be restarted.

[0043] In response to receiving an upgrade command of a specified object, an upgrade process of a cluster system is started according to the embodiments provided in the present application, wherein nodes to be upgraded in the cluster system are divided into at least two batches, and the upgrade process is used to upgrade the nodes to be upgraded in the cluster system according to the batches to which the nodes belong; in the case that an upgrade mode adopted by the cluster system is a first upgrade mode and there is a next batch of the at least two batches, in response to completion of node upgrade of a current batch, the upgrade process is suspended, and a timer is started, wherein the first upgrade mode is an upgrade mode in which upgrade time of nodes of different batches is controlled by the timer, and a timing time of the timer is positively correlated with environment complexity of a node deployment of the next batch; in the case that the second continue upgrade instruction of the specified object is received before the timing time of the timer ends, the timer is stopped, and a continue upgrade command is waited to be received; in the case that a first continue upgrade command of the specified object is received, the upgrade process is resumed, and the nodes of the next batch are upgraded. Since the timing time of the timer for controlling the upgrade time of the nodes of the next batch in the first upgrade mode is positively correlated with the environment complexity of the node deployment, the waiting time can be adaptively adjusted for different deployment environments, and the user can also freely control the upgrade start time of the nodes of the next batch through the pause upgrade instruction and the first continue upgrade command, thereby solving the problem of insufficient flexibility of the node upgrade control method in the related art, and improving the flexibility of the node upgrade control.

[0044] In one example embodiment, after the timer is started, the above method further includes: in the case that a second continue upgrade instruction of the specified object is received before the timing time of the timer ends, stopping the timer and upgrading the nodes of the next batch; in the case that the timing time of the timer ends, upgrading the nodes of the next batch.

[0045] In the present embodiment, similar to the related art, in the case that the timing time of the timer ends, the nodes of the next batch can be automatically upgraded. In addition, in order to avoid redundant waiting time, in the case that the user completes the upgrade preparation of the nodes of the next batch in advance and the timing time of the timer has not ended, the user can give a second continue upgrade instruction to instruct to start the upgrade of the nodes of the next batch in advance, in the case that the second continue upgrade instruction of the specified object is received before the timing time of the timer ends, the timer is stopped, and the nodes of the next batch are upgraded.

[0046] Optionally, before the nodes of the next batch are upgraded, the cluster system can remind the user to check the host connection state and automatically perform some automated basic checks (such as volume dependency checks) to ensure that the upgrade node does not cause user service interruption after being offline.

[0047] Through the embodiment, the next batch of nodes can be upgraded automatically in the case that the timing time of the timer ends, reducing the operation pressure of the user; or the user gives a second continue upgrading instruction to upgrade the next batch of nodes in advance, which can reduce the redundant waiting time and prevent time waste.

[0048] In one example embodiment, before starting the timer, the above method further comprises: detecting the environment complexity of the next batch of nodes, wherein the environment complexity of the next batch of nodes is determined according to the parameter values of a set of configuration parameters corresponding to the next batch of nodes, and the set of configuration parameters includes the number of host connections; and configuring the timing time of the timer according to the environment complexity of the next batch of nodes.

[0049] Similar to the foregoing embodiments, in order to improve the intelligence of the first upgrade mode, the environment complexity of the next batch of nodes can be checked, and the timing time of the timer can be intelligently configured based on the environment complexity, that is, the timing time of the timer is positively correlated with the environment complexity of the next batch of nodes, that is, the environment complexity of the next batch of nodes is higher, and a longer timing time can be configured to give the user sufficient time to check; the environment complexity of the next batch of nodes is lower, and a shorter timing time can be configured to reduce the redundant waiting time after the user checks and prevent time waste.

[0050] In the embodiment, in the case that the currently adopted upgrade mode is the first upgrade mode, before starting the timer, the environment complexity of the next batch of nodes is detected, wherein the environment complexity of the next batch of nodes is determined according to the parameter values of a set of configuration parameters corresponding to the next batch of nodes, and the set of configuration parameters includes the number of host connections. Optionally, the parameter values of the set of configuration parameters can include network bandwidth and delay, storage volume dependency state, application service state, node health state, etc. in addition to the number of host connections.

[0051] After checking the environment complexity of the next batch of nodes, the timing time of the timer can be configured based on the environment complexity of the next batch of nodes, wherein the timing time of the timer is positively correlated with the environment complexity of the next batch of nodes. Optionally, the timing time of the timer configured based on the environment complexity can be configured within a limited maximum and minimum range, for example, the minimum time is not less than five minutes and the maximum time is not more than sixty minutes. In addition, in the case that a pause upgrade command is received under the second upgrade model, it can be considered that the current cluster system has a large problem risk, and the timing time of the timer configured for the next batch of nodes can be correspondingly increased to ensure sufficient time to check and handle the problem.

[0052] By the embodiment, the environment complexity of the next batch of node deployment is checked, and the timing time of the timer is configured based on the environment complexity, so as to solve the problem of fixed timing time of the timer in the prior art, and improve the flexibility and intelligence of the cluster system upgrade control.

[0053] In an example embodiment, the method further comprises: in the case of receiving the state query instruction, responding to the state query instruction, and displaying the current upgrade state information through the display device, wherein the current upgrade state information is used to indicate at least one of the following: the current upgrade progress; the current state, the current state being one of the following: upgrading, waiting, paused, and abnormal termination; the total timing duration of the timer; the remaining timing duration of the timer; and operation suggestions.

[0054] In order for the user to be able to know the upgrade state and progress of the cluster system at any time, the user can obtain the state information through the query instruction. In the case of receiving the state query instruction, the system responds to the state query instruction and displays the current upgrade state information through the display device, wherein the current upgrade state information is used to indicate at least one of the following: the current upgrade progress, the current state, the total timing duration of the timer, the remaining timing duration of the timer, and operation suggestions. It should be noted that the current upgrade state information displayed through the display device can be at least one or more of the above five kinds of information, and in some cases, part of the information will not be indicated, for example, in the first upgrade mode, the timer is not enabled, so the total timing duration of the timer and the remaining timing duration of the timer will not be indicated.

[0055] Correspondingly, the method further comprises: in the case of the current upgrade state information indicating the current upgrade progress, determining the current upgrade progress according to the total number of nodes to be upgraded in the cluster system and the total number of nodes upgraded in the cluster system. The current upgrade progress, i.e., the upgrade progress of the cluster system as a whole, can be determined according to the total number of nodes to be upgraded in the cluster system and the total number of nodes upgraded in the cluster system, for example, the current upgrade progress can indicate the proportion of the total number of nodes upgraded to the total number of nodes to be upgraded. Alternatively, the current upgrade progress can also indicate the total number of batches into which the nodes to be upgraded in the cluster system are divided and the number of batches that have completed the upgrade.

[0056] The current state can indicate the current upgrade state of the cluster system, and the current state is one of the following four states: upgrading, waiting, paused, and abnormal termination, wherein upgrading means that there is a node being upgraded, waiting means waiting for the timing time of the timer to end in the second upgrade mode, paused means that the upgrade process is in a paused state in the first upgrade mode or in the second upgrade mode, and abnormal termination means that the upgrade process is forcibly terminated due to an abnormal condition.

[0057] The total timing duration of the timer and the remaining timing duration of the timer can be indicated in the second upgrade mode, where the total timing duration of the timer is the configured timing duration, and the remaining timing duration of the timer is the configured timing duration minus the timing duration that has been counted down. Optionally, the expected start-upgrade time of the next batch of nodes can also be indicated, which can be obtained by adding the current time to the remaining timing duration of the timer.

[0058] The operation suggestion can be determined based on the current state, and optionally, in the case that the current state is in the waiting state, the operation suggestion can be "wait"; in the case that the current state is paused, the operation suggestion can be "check and continue upgrade after user selection"; in the case that the current state is abnormally terminated, the operation suggestion can indicate the abnormal condition that triggered the abnormal termination, so that the user can quickly locate and handle the abnormality.

[0059] Through this embodiment, by real-time state query, the upgrade state is transparentized, which can provide detailed upgrade state information for the user, reduce troubleshooting cost, facilitate the user to understand the current state at any time, and perform risk assessment and flexible adjustment of the next operation strategy according to the current state, thereby improving the visualization and controllability of the upgrade process.

[0060] In one example embodiment, the above method further includes: in the case that the upgrade mode adopted by the cluster system is the second upgrade mode, and there is a next batch of nodes in the at least two batches, pausing the upgrade process and waiting to receive a continue-upgrade command, where the second upgrade mode is an upgrade mode in which the upgrade timing of nodes of different batches is controlled by the continue-upgrade command; in the case that the second continue-upgrade command is received, resuming the upgrade process and upgrading the nodes of the next batch.

[0061] In order to improve the flexibility of upgrade control, a second upgrade mode is provided in addition to the first upgrade mode, in which the upgrade timing of nodes of different batches can be controlled by the continue-upgrade command.

[0062] The second upgrade mode is different from the intermediate interval method in the related art, in which the upgrade process can be automatically paused after the upgrade of a batch of nodes is completed, until the user completes the upgrade preparation of the next batch of nodes and gives a continue-upgrade command to start upgrading the next batch of nodes. The user can flexibly regulate and control the upgrade timing of the next batch of nodes according to actual needs, thereby improving the flexibility of node upgrade control.

[0063] In a case where the upgrade mode adopted by the cluster system is the second upgrade mode and there is the next batch of nodes in the at least two batches, the upgrade process is paused and waiting for receiving a continue-upgrade command, wherein the second upgrade mode is an upgrade mode in which the upgrade time of the nodes in different batches is controlled by the continue-upgrade command. In the second upgrade mode, the user can freely control the upgrade time of the nodes in each batch, and the user can input the continue-upgrade command after confirming that the nodes in the next batch are ready for upgrade, so as to ensure sufficient time for checking and problem fixing, and avoid time waste due to redundant waiting time. In a case where the user inputs the second continue-upgrade command and the system receives the second continue-upgrade command, the upgrade process can be resumed and the nodes in the next batch of the current batch are upgraded.

[0064] Optionally, there are the first continue-upgrade command and the second continue-upgrade command, and the two continue-upgrade commands can be the same or different. For example, the user can input the same command of “continue-upgrade”, and the system can intelligently parse the command as the first continue-upgrade command or the second continue-upgrade command according to the current state, and perform the corresponding process resuming operation.

[0065] Optionally, the user can switch the upgrade mode of the nodes in the next batch in the upgrade process. In a case where the upgrade mode of the nodes in the next batch is not switched, the nodes in the next batch can follow the current upgrade mode after the upgrade of the nodes in the next batch is completed. For example, in a case where the current upgrade mode is the first upgrade mode, if the user switches the upgrade mode of the nodes in the next batch, the second upgrade mode will be entered after the upgrade of the nodes in the next batch is completed, that is, the upgrade process is paused and waiting for receiving the continue-upgrade command. If the user does not switch the upgrade mode of the nodes in the next batch, the first upgrade mode will be kept after the upgrade of the nodes in the next batch is completed, that is, the timer is started.

[0066] Through the embodiment, by setting the second upgrade mode, the user can select and use a suitable upgrade mode, and the flexibility of node upgrade control is improved.

[0067] In one example embodiment, the method further includes: in a case where the upgrade mode adopted by the cluster system is the first upgrade mode and there is the next batch of nodes in the at least two batches, in response to the upgrade of the nodes in the current batch being completed, detecting the environment complexity of the nodes in the next batch, wherein the environment complexity of the nodes in the next batch is determined according to the parameter values of a group of configuration parameters corresponding to the nodes in the next batch, and the group of configuration parameters includes the number of host connections.

[0068] Here, the way of detecting the environment complexity of the nodes in the next batch is similar to the foregoing embodiments, and will not be described here.

[0069] Correspondingly, in a case where the environment complexity of the next batch of nodes is higher than the specified complexity threshold, the upgrade mode adopted by the cluster system is switched from the first upgrade mode to a second upgrade mode, where the second upgrade mode is an upgrade mode in which the upgrade timing of the nodes of different batches is controlled by the continue upgrade command.

[0070] In a case where the environment complexity of the next batch of nodes is high (higher than the specified complexity threshold), the pre-upgrade detection of the next batch of nodes can take a long time that is difficult to predict, and in order to give the user sufficient time to prepare for the upgrade, the upgrade mode can be switched from the first upgrade mode to the second upgrade mode in a case where the environment complexity of the next batch of nodes is higher than the specified complexity threshold, i.e., the upgrade process is paused before the upgrade of the next batch of nodes until the user is ready and gives a second continue upgrade command to resume the upgrade process and upgrade the next batch of nodes. Here, the specified complexity threshold can be set according to experience, for example, the number of host connections is greater than 100, 120, or other values, which are not limited in this embodiment. Alternatively, the switching to the second upgrade mode here can be temporary switching, i.e., only switching to the second upgrade mode before the upgrade of the next batch of nodes is completed, and switching back to the first upgrade mode automatically before the upgrade of the next batch of nodes of the next batch of nodes (i.e., the next batch of nodes of the next batch of nodes) is completed; or it can also be a retainable switching, i.e., switching to the second upgrade mode before the upgrade of the next batch of nodes is completed, and remaining in the second upgrade mode after the upgrade of the next batch of nodes of the next batch of nodes is completed in a case where the user does not actively switch the upgrade mode, which is not limited in this embodiment.

[0071] Through this embodiment, in a case where the environment complexity of the next batch of nodes is higher than the specified complexity threshold, the second upgrade mode is automatically switched, which can ensure that the user has sufficient time to prepare when facing a complex upgrade environment, and reduces the risk of upgrade failure or business interruption.

[0072] In one example embodiment, the current batch of nodes is not the first batch of nodes of the cluster system; after starting the upgrade process of the cluster system, the above method further comprises: in response to the upgrade of the first batch of nodes being completed, pausing the upgrade process; in a case where a third continue upgrade command is received, resuming the upgrade process to upgrade the second batch of nodes of the cluster system.

[0073] The upgrade of the first batch of nodes of the cluster system is usually prone to problems. In order to have sufficient time to check and handle the problems after the upgrade of the first batch of nodes of the cluster system is completed, the upgrade process can be automatically paused after the upgrade of the first batch of nodes is completed until a third continue-upgrade command is received to resume the upgrade process for the next batch of nodes (the second batch of nodes of the cluster system). It should be noted that the pause of the upgrade process after the upgrade of the first batch of nodes is completed is not by default in the second upgrade mode. The upgrade mode to be used by default can be set before starting the upgrade process of the cluster system. For example, in the case where the upgrade mode to be used by default is the second upgrade mode, the upgrade process can still be paused after the upgrade of the first batch of nodes is completed, and the second batch and subsequent batches of nodes will follow the upgrade mode to be used by default (here, the first upgrade mode) to control the upgrade time of the next batch of nodes by using the timer.

[0074] Through the embodiment, the user is provided with a more intelligent and safe and controllable upgrade method by pausing the upgrade process after the upgrade of the first batch of nodes is completed, and the controllability and intelligence of the upgrade process are improved.

[0075] In an example embodiment, the method further includes: in the case where at least one abnormal scenario in the abnormal scenario set is triggered, stopping the upgrade process and issuing an abnormal prompt information; in the case where a resume-upgrade command is received, resuming the upgrade process in response to the resume-upgrade command; and in the case where a rollback command is received, restoring the nodes of a specified batch corresponding to the rollback command to a state before the upgrade in response to the rollback command.

[0076] In order to limit the damage of the upgrade process to the cluster system in the case of an abnormality, an abnormal scenario set can be preset, and in the case where at least one abnormal scenario in the abnormal scenario set is triggered, the upgrade process is stopped and an abnormal prompt information is issued to prompt the user to handle the abnormality in a timely manner.

[0077] In the embodiment, in the case where at least one abnormal scenario in the abnormal scenario set is triggered, the upgrade process is stopped and an abnormal prompt information is issued. Here, the abnormal scenario set can include common abnormal scenarios, such as node offline, upgrade failure, storage volume abnormality, etc. When any of the scenarios is triggered, the system will immediately terminate the upgrade process and issue an abnormal prompt information through a display device and / or a sound device. Optionally, the specific abnormal scenario triggered and the specific position of the abnormal scenario triggered can be prompted synchronously when the abnormal prompt information is issued. Recommended solutions can be preset for each abnormal scenario, and the recommended solutions can be prompted when the abnormal prompt information is issued, so as to facilitate the user to handle the abnormality.

[0078] After the user completes the processing of the exception, a resume upgrade command can be input, and the system can resume the upgrade process from the aborted upgrade process in response to the resume upgrade command. Alternatively, in the case that the user encounters difficulties in processing the exception, a rollback command can be input, and the system can restore the nodes of the specified batch corresponding to the rollback command to the state before the upgrade in response to the rollback command, so that the user processes the exception from the state before the exception occurs.

[0079] Through this embodiment, by adding the methods of exception checking and aborting, resuming upgrade, and state rollback in the node upgrade process, the safety and controllability in the upgrade process can be enhanced.

[0080] The node upgrade control method in the embodiments of the present application will be explained below in combination with optional examples. Figure 3 is a flowchart of the initial setting of the node upgrade control method in the present optional example, as shown in Figure 3 The flow of the initial setting of the node upgrade control method can include that the user inputs an upgrade command and selects an initial upgrade mode, including a second upgrade mode and a first upgrade mode, in the second upgrade mode, the node of each batch is upgraded and then automatically enters a pause state, in the first upgrade mode, the upgrade of each batch of nodes is controlled by a timer, the default timing duration of the timer is 30 minutes, and the timing duration can be adjusted intelligently according to the environmental complexity in the upgrade process.

[0081] Figure 4 is a flowchart of the upgrade cycle flow of the node upgrade control method in the present optional example, as shown in Figure 4 The upgrade cycle flow of the node upgrade control method can include that whether it is the first batch of nodes is detected, if it is the first batch of nodes, it directly enters the pause state, if it is not the first batch of nodes, whether it is the first upgrade mode is detected, if it is not the first upgrade mode, it also enters the pause state. In the pause state, until a continue upgrade command is received to determine the upgrade of the next batch of nodes.

[0082] If it is the first upgrade mode, the timer is started, at this time the state is waiting, and the remaining time of the timer is displayed on the display device. The user can input pause at any time, if the user does not input pause, after waiting for the timer to expire, it is determined to execute the upgrade of the next batch of nodes; if the user inputs pause, the upgrade process is paused, the timer is canceled, and the pause state is entered, until a continue upgrade command is received to determine the upgrade of the next batch of nodes.

[0083] After it is determined to prepare to execute the upgrade of the next batch of nodes, the upgrade is performed, and after the upgrade is performed, whether there is a remaining batch is detected, if there is no remaining batch, the upgrade is ended, if there is a remaining batch, the initial detection of whether it is the first batch of nodes is returned, and the cycle upgrade is realized.

[0084] Figure 5 is a flowchart of an upgrade check of a node upgrade control method in the present alternative example, as shown in Figure 5 The upgrade check flow of the node upgrade control method can include: after upgrading a batch of nodes, checking whether the upgrade is successful, if not, performing exception handling; if successful, recording the upgrade success, and judging whether the upgrade of the next batch of nodes has started, if not, judging whether the user switches the upgrade mode, if yes, switching the upgrade mode to another upgrade mode, if not, continuing to use the current upgrade mode.

[0085] Figure 6 is a flowchart of exception handling of a node upgrade control method in the present alternative example, as shown in Figure 6 The exception handling flow of the node upgrade control method can include: after an abnormal interruption occurs, the user handles the exception, after the user handles the exception, the user can choose to resume the upgrade or roll back the version, if the user chooses to resume the upgrade, the current upgrade mode is saved and the upgrade is continued, if the user chooses to roll back the version, the batch of nodes that triggered the exception is rolled back to the state before the upgrade.

[0086] Through the present alternative example, two modes of the first upgrade mode and the second upgrade mode are provided, the user can freely select and flexibly switch the upgrade mode, in the upgrade process, the user can pause the upgrade, and start the upgrade of the next batch of nodes in the case of receiving a continue upgrade command, the upgrade time of each batch of nodes can be flexibly controlled, and the flexibility of the cluster system upgrade is provided.

[0087] It should be noted that for each of the above method embodiments, in order to simply describe, they are all expressed as a series of action combinations, but those skilled in the art should know that the present application is not limited by the order of the described actions, because according to the present application, certain steps can be performed in other order or simultaneously. Secondly, those skilled in the art should know that the embodiments described in the specification all belong to preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

[0088] Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be realized by means of software and the necessary general hardware platform, of course, it can also be realized by hardware, but in many cases, the former is a better embodiment.

[0089] The embodiments of the present application also provide a node upgrade control device, Figure 7 is a structural block diagram of a node upgrade control device according to the embodiments of the present application, as shown in Figure 7 The device includes:

[0090] The first starting unit 702 is configured to start an upgrade process of the cluster system in response to receiving an upgrade command of a specified object, wherein the nodes to be upgraded in the cluster system are divided into at least two batches, and the upgrade process is used to upgrade the nodes to be upgraded in the cluster system according to the batches to which the nodes belong.

[0091] The first execution unit 704 is configured to pause the upgrade process and start a timer in response to completion of node upgrade of a current batch, when the upgrade mode adopted by the cluster system is a first upgrade mode and there is a next batch of the at least two batches, wherein the first upgrade mode is an upgrade mode in which the upgrade time of the nodes of different batches is controlled by the timer, and the timing time of the timer is positively correlated with the environment complexity of the nodes of the next batch.

[0092] The second execution unit 706 is configured to stop the timer and wait for receiving a continue upgrade command in response to receiving a pause upgrade instruction of the specified object before the timing time of the timer ends.

[0093] The third execution unit 708 is configured to resume the upgrade process and upgrade the nodes of the next batch in response to receiving a first continue upgrade command of the specified object.

[0094] With the above device, the upgrade process of the cluster system is started in response to receiving an upgrade command of a specified object, wherein the nodes to be upgraded in the cluster system are divided into at least two batches, and the upgrade process is used to upgrade the nodes to be upgraded in the cluster system according to the batches to which the nodes belong; the upgrade process is paused and a timer is started in response to completion of node upgrade of a current batch, when the upgrade mode adopted by the cluster system is a first upgrade mode and there is a next batch of the at least two batches, wherein the first upgrade mode is an upgrade mode in which the upgrade time of the nodes of different batches is controlled by the timer, and the timing time of the timer is positively correlated with the environment complexity of the nodes of the next batch; the timer is stopped and a continue upgrade command is waited for in response to receiving a pause upgrade instruction of the specified object before the timing time of the timer ends; the upgrade process is resumed and the nodes of the next batch are upgraded in response to receiving a first continue upgrade command of the specified object. Since the timing time of the timer for controlling the upgrade time of the nodes of the next batch in the first upgrade mode is positively correlated with the environment complexity of the nodes, the waiting time can be adaptively adjusted for different deployment environments, and the user can also freely control the upgrade start time of the nodes of the next batch through the pause upgrade instruction and the first continue upgrade command, thereby solving the problem of insufficient flexibility of the node upgrade control method in the related art and improving the flexibility of the node upgrade control.

[0095] In an example embodiment, the apparatus further includes a fourth execution unit, configured to, in response to receiving a second continue-upgrading instruction of the specified object before the timing time of the timer ends after starting the timer, stop the timer and upgrade the next batch of nodes; and an upgrading unit, configured to upgrade the next batch of nodes in response to the timing time of the timer ending.

[0096] In an example embodiment, the apparatus further includes a first detection unit, configured to detect an environment complexity of the next batch of nodes before starting the timer, wherein the environment complexity of the next batch of nodes is determined according to parameter values of a set of configuration parameters corresponding to the next batch of nodes, and the set of configuration parameters includes the number of host connections; and a configuration unit, configured to configure the timing time of the timer according to the environment complexity of the next batch of nodes.

[0097] In an example embodiment, the apparatus further includes a display unit, configured to, in response to receiving the state query instruction, display the current upgrading state information on the display apparatus, wherein the current upgrading state information is used to indicate at least one of the following: a current upgrading progress; a current state, the current state being one of the following: upgrading, waiting, paused, and abnormally terminated; a total timing duration of the timer; a remaining timing duration of the timer; and an operation suggestion.

[0098] In an example embodiment, the apparatus further includes a determination unit, configured to, in response to the current upgrading state information indicating the current upgrading progress, determine the current upgrading progress according to a total number of nodes to be upgraded in the cluster system and a total number of nodes that have been upgraded in the cluster system.

[0099] In an example embodiment, the apparatus further includes a second detection unit, configured to, in response to the current batch of nodes being upgraded, detect an environment complexity of a next batch of nodes in the case that the upgrading mode of the cluster system is the first upgrading mode and there is the next batch of nodes after the current batch of nodes among the at least two batches, wherein the environment complexity of the next batch of nodes is determined according to parameter values of a set of configuration parameters corresponding to the next batch of nodes, and the set of configuration parameters includes the number of host connections; and a switching unit, configured to switch the upgrading mode of the cluster system from the first upgrading mode to a second upgrading mode in the case that the environment complexity of the next batch of nodes is higher than a specified complexity threshold, wherein the second upgrading mode is an upgrading mode in which upgrading time points of different batches of nodes are controlled by continue-upgrading commands.

[0100] In an example embodiment, the apparatus further includes a fifth execution unit configured to, in the case that the upgrade mode adopted by the cluster system is a second upgrade mode and there is a next batch of the current batch in the at least two batches, suspend the upgrade process and wait for receiving a continue-upgrade command, wherein the second upgrade mode is an upgrade mode in which the upgrade timing of the nodes of different batches is controlled by the continue-upgrade command; and a sixth execution unit configured to, in the case that the second continue-upgrade command is received, resume the upgrade process and upgrade the nodes of the next batch.

[0101] In an example embodiment, the nodes of the current batch are not the nodes of a first batch of the cluster system; and the apparatus further includes a suspension unit configured to, after starting the upgrade process of the cluster system, in response to the nodes of the first batch being upgraded, suspend the upgrade process; and a first resumption unit configured to, in the case that a third continue-upgrade command is received, resume the upgrade process to upgrade the nodes of a second batch of the cluster system.

[0102] In an example embodiment, the apparatus further includes a seventh execution unit configured to, in the case that at least one of the abnormal scenarios in the abnormal scenario set is triggered, abort the upgrade process and issue an abnormal prompt message; a second resumption unit configured to, in the case that a resume-upgrade command is received, resume the upgrade process in response to the resume-upgrade command; and a third resumption unit configured to, in the case that a rollback command is received, restore the nodes of a specified batch corresponding to the rollback command to a state before the upgrade in response to the rollback command.

[0103] The features of the embodiments of the node upgrade control apparatus can be understood by referring to the related descriptions of the embodiments of the node upgrade control method, which will not be repeated here.

[0104] The embodiments of the present application also provide an electronic device including a memory and a processor, the memory storing a computer program, and the processor being configured to run the computer program to perform the steps in any of the embodiments of the node upgrade control method.

[0105] The embodiments of the present application also provide a computer readable storage medium storing a computer program, wherein the computer program is configured to perform the steps in any of the embodiments of the node upgrade control method when running.

[0106] In an example embodiment, the computer readable storage medium can include, but is not limited to, a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store computer programs.

[0107] Embodiments of this application also provide a computer program product, which includes a computer program that, when executed by a processor, implements the steps in any of the above-described node upgrade control method embodiments.

[0108] Embodiments of this application also provide another computer program product, including a non-volatile computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in any of the above-described node upgrade control method embodiments.

[0109] Those skilled in the art will further recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. To clearly illustrate the interchangeability of hardware and software, the components and steps of the various examples have been generally described in terms of functionality in the foregoing description. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can 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.

[0110] The node upgrade control method and electronic device provided in this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of the embodiments above are only intended to help understand the method and core ideas of this application. It should be noted that those skilled in the art can make several improvements and modifications to this application without departing from the principles of this application, and these improvements and modifications also fall within the protection scope of the claims of this application.

Claims

1. A node upgrade control method, characterized in that, include: In response to receiving an upgrade command for a specified object, an upgrade process for the cluster system is initiated, wherein the nodes to be upgraded in the cluster system are divided into at least two batches, and the upgrade process is used to upgrade the nodes to be upgraded in the cluster system according to their respective batches. When the cluster system adopts the first upgrade mode and there is a next batch of the current batch in the at least two batches, in response to the completion of the upgrade of the nodes in the current batch, the upgrade process is paused and a timer is started. The first upgrade mode is an upgrade mode that controls the upgrade timing of nodes in different batches through the timer. The timing of the timer is positively correlated with the environmental complexity of the deployment of the nodes in the next batch. If a pause upgrade command for the specified object is received before the timer expires, the timer is stopped, and the system waits to receive a continue upgrade command. Upon receiving the first continue upgrade command for the specified object, the upgrade process is resumed, and the next batch of nodes is upgraded.

2. The node upgrade control method according to claim 1, characterized in that, After starting the timer, the method further includes: If a second continue upgrade instruction for the specified object is received before the timer expires, the timer is stopped, and the next batch of nodes is upgraded. When the timer expires, the next batch of nodes is upgraded.

3. The node upgrade control method according to claim 1, characterized in that, Prior to starting the timer, the method further includes: The environmental complexity of the next batch of node deployments is detected, wherein the environmental complexity of the next batch of node deployments is determined based on the parameter values ​​of a set of configuration parameters corresponding to the next batch of nodes, the set of configuration parameters including the number of host connections; Configure the timer's timing period based on the environmental complexity of the next batch of node deployments.

4. The node upgrade control method according to claim 1, characterized in that, The method further includes: Upon receiving a status query command, in response to the status query command, the current upgrade status information is displayed through a display device, wherein the current upgrade status information is used to indicate at least one of the following: current upgrade progress; current status, which is one of the following: upgrading, waiting, paused, abnormally terminated; total timeout duration of the timer; remaining timeout duration of the timer; operation suggestions.

5. The node upgrade control method according to claim 4, characterized in that, The method further includes: When the current upgrade status information is used to indicate the current upgrade progress, the current upgrade progress is determined based on the total number of nodes to be upgraded in the cluster system and the total number of nodes that have been upgraded in the cluster system.

6. The node upgrade control method according to claim 1, characterized in that, The method further includes: When the cluster system adopts the first upgrade mode and there is a next batch of the current batch in the at least two batches, in response to the completion of the upgrade of the nodes in the current batch, the environmental complexity of the deployment of the nodes in the next batch is detected. The environmental complexity of the deployment of the nodes in the next batch is determined according to the parameter values ​​of a set of configuration parameters corresponding to the nodes in the next batch, and the set of configuration parameters includes the number of host connections. If the environmental complexity of the next batch of nodes deployed exceeds a specified complexity threshold, the upgrade mode adopted by the cluster system will be switched from the first upgrade mode to the second upgrade mode. The second upgrade mode is an upgrade mode that controls the upgrade timing of different batches of nodes through a continue upgrade command.

7. The node upgrade control method according to claim 1, characterized in that, The method further includes: If the cluster system is using the second upgrade mode and there is a next batch of the current batch in the at least two batches, the upgrade process is paused and the system waits to receive a continue upgrade command. The second upgrade mode is an upgrade mode that controls the upgrade timing of nodes in different batches through the continue upgrade command. Upon receiving a second continue upgrade command, the upgrade process is resumed, and the next batch of nodes is upgraded.

8. The node upgrade control method according to claim 1, characterized in that, The nodes in the current batch are not the nodes in the first batch of the cluster system; After initiating the upgrade process of the cluster system, the method further includes: In response to the completion of the first batch of node upgrades, the upgrade process is paused; Upon receiving a third continue upgrade command, the upgrade process is resumed to upgrade the second batch of nodes in the cluster system.

9. The node upgrade control method according to any one of claims 1 to 8, characterized in that, The method further includes: If at least one abnormal scenario in the abnormal scenario set is triggered, the upgrade process is terminated and an abnormal prompt message is issued. Upon receiving a restore / upgrade command, the upgrade process is resumed in response to the restore / upgrade command; Upon receiving a rollback command, in response to the rollback command, the nodes in the specified batch corresponding to the rollback command are restored to their state before the upgrade.

10. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor for executing the computer program to implement the steps of the node upgrade control method as described in any one of claims 1 to 9.

Images