Node upgrade control method and electronic device

Abstract

The application discloses a node upgrade control method and electronic equipment, and relates to the technical field of computers, and comprises the following steps: in response to receiving an upgrade command of a specified object, starting an upgrade process of a cluster system; in the case that an upgrade mode adopted by the cluster system is a first upgrade mode, and there is a next batch in at least two batches, in response to completion of node upgrade of a current batch, suspending the upgrade process and starting a timer; in the case that a suspension 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 nodes of the next batch, so that the technical problem of insufficient flexibility of a node upgrade control method in the prior art is solved, and the technical effect of improving the flexibility of node upgrade control is achieved.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to a node upgrade control method and electronic device. Background Technology

[0002] With the rapid development of information technology, distributed systems, especially cluster computing systems (such as server clusters, storage clusters, and database clusters), play an indispensable role in key areas such as enterprise applications, cloud computing, and big data processing. To ensure system security, stability, and performance optimization, cluster systems require regular software version upgrades, patch updates, or configuration changes. During the upgrade process, to avoid the entire cluster becoming unavailable due to simultaneous upgrades of a large number of nodes, batch upgrades are typically used. A fixed interval is maintained between different batches to allow relevant personnel to check the results of the previous batch or inspect the environment for the next batch.

[0003] However, in related technologies, the intermediate interval time is preset and fixed, lacking flexibility when facing complex cluster systems undergoing upgrades. For example, if the upgrade environment of the next batch of nodes is relatively simple, relevant personnel can quickly complete the check but still need to wait for the same long intermediate interval, resulting in wasted time; or if the upgrade environment of the next batch of nodes is more complex, relevant personnel need to spend a longer time checking, but only have the same long intermediate interval, resulting in insufficient time. Therefore, it is evident that the node upgrade control methods in related technologies suffer from a lack of flexibility. Summary of the Invention

[0004] This application provides a node upgrade control method and an electronic device to at least solve the problem of insufficient flexibility in node upgrade control methods in related technologies.

[0005] This application provides a node upgrade control method, comprising: in response to receiving an upgrade command from a specified object, initiating an upgrade process of a 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 their respective batches; when the upgrade mode adopted by the cluster system is a first upgrade mode, and there is a next batch of the current batch among 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 that controls the upgrade timing of different batches of nodes through the timer, and the timing period of the timer is positively correlated with the environmental complexity of the deployment of the next batch of nodes; if a pause upgrade command is received from the specified object before the timing period of the timer expires, stopping the timer and waiting to receive a continue upgrade command; if a first continue upgrade command is received from the specified object, resuming the upgrade process and upgrading the nodes in the next batch.

[0006] This application also provides a node upgrade control device, comprising: a first initiation unit, configured to initiate an upgrade process of a cluster system in response to receiving an upgrade command from 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 their respective batches; a first execution unit, configured to, when the cluster system adopts a first upgrade mode and there is a next batch of the current batch among the at least two batches, suspend the upgrade process and start a timer in response to the completion of the upgrade of the nodes in the current batch, wherein the first upgrade mode is an upgrade mode that controls the upgrade timing of nodes in different batches through the timer, and the timing period of the timer is positively correlated with the environmental complexity of the deployment of the nodes in the next batch; a second execution unit, configured to, upon receiving a pause upgrade command from the specified object before the timing period of the timer expires, stop the timer and wait to receive a continue upgrade command; and a third execution unit, configured to, upon receiving a first continue upgrade command from the specified object, resume the upgrade process and upgrade the nodes in the next batch.

[0007] This application also provides an electronic device, including: a memory for storing a computer program; and a processor for executing the computer program to implement the steps of any of the above-described node upgrade control methods.

[0008] This application also provides a computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of any of the above-described node upgrade control methods.

[0009] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of any of the above-described node upgrade control methods.

[0010] According to this application, in response to receiving an upgrade command from a specified object, an upgrade process for the cluster system is initiated. 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 according to their respective batches. If the cluster system adopts the first upgrade mode, and there is a next batch within the current batch among 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 a timer, and the timer's duration is positively correlated with the environmental complexity of the next batch of nodes. If a pause upgrade command is received from a specified object before the timer's duration expires, the timer is stopped, and the system waits to receive a continue upgrade command. If a first continue upgrade command is received from a specified object, the upgrade process is resumed, and the next batch of nodes is upgraded. Since the timing of the timer controlling the timing of the next batch of node upgrades in the first upgrade mode is positively correlated with the complexity of the node deployment environment, the waiting time can be adaptively adjusted for different deployment environments. Furthermore, users can freely control the start time of the next batch of node upgrades through pause upgrade commands and first continue upgrade commands. This solves the technical problem of insufficient flexibility in node upgrade control methods in related technologies, and achieves the technical effect of improving the flexibility of node upgrade control. Attached Figure Description

[0011] To more clearly illustrate the embodiments of this application, the accompanying drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

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

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

[0014] Figure 3 This is a schematic flowchart illustrating the initial setup of an optional node upgrade control method according to an embodiment of this application.

[0015] Figure 4This is a schematic flowchart of an optional node upgrade control method according to an embodiment of this application, illustrating the upgrade cycle process.

[0016] Figure 5 This is a schematic flowchart of an optional node upgrade control method according to an embodiment of this application, illustrating the upgrade check process.

[0017] Figure 6 This is a schematic flowchart of an exception handling method for an optional node upgrade control method according to an embodiment of this application.

[0018] Figure 7 This is a structural block diagram of an optional node upgrade control device according to an embodiment of this application. Detailed Implementation

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

[0020] It should be noted that, in the description of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. The terms "first," "second," etc., in this application are used to distinguish similar objects and are not used to describe a specific order or sequence.

[0021] To enable 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 accompanying drawings and specific embodiments.

[0022] The specific application environment architecture or specific hardware architecture on which the execution of the node upgrade control method depends is described here.

[0023] The methods and embodiments provided in this application can be executed on a server device or a similar computing device. Taking running on a server device as an example, Figure 1 This is a hardware structure block diagram of the node upgrade control method according to an embodiment of this application. Figure 1 As shown, the server device may include one or more ( Figure 1Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The server device may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the server equipment described above. For example, the server equipment may also include components that are more... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0024] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the node upgrade control method in this embodiment. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thus implementing the aforementioned method. The memory 104 may include high-speed random access memory and non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to server devices via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0025] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by a communication provider for the server device. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module used for wireless communication with the Internet.

[0026] The embodiments of this application provide a node upgrade control method. By setting a first upgrade mode and a second upgrade mode, in the first upgrade mode, the upgrade process is automatically paused after a batch of nodes is upgraded, until a command to continue upgrading is received before upgrading the next batch of nodes. In the second upgrade mode, the next batch of nodes is automatically upgraded after the timer expires. The timer can be automatically configured based on the upgrade environment complexity of the next batch of nodes, and can pause the upgrade process in response to a pause upgrade command, until a command to continue upgrading is received before upgrading the next batch of nodes. Users can freely choose the upgrade mode or pause the upgrade at any time according to the actual situation during the upgrade process, which can improve the flexibility of node upgrade control.

[0027] This embodiment provides a node upgrade control method. Figure 2 This is a flowchart of a node upgrade control method according to an embodiment of this application, such as... Figure 2 As shown, the method includes steps S202, S204, S206 and S208.

[0028] Step S202: In response to receiving an upgrade command for a specified object, the upgrade process of the cluster system is started. The nodes to be upgraded in the cluster system are divided into at least two batches. The upgrade process is used to upgrade the nodes to be upgraded in the cluster system according to their respective batches.

[0029] Step S204: When the cluster system adopts the first upgrade mode and there is a next batch of the current batch in 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 a timer. The timing of the timer is positively correlated with the environmental complexity of the deployment of the nodes in the next batch.

[0030] Step S206: If a pause upgrade command for a specified object is received before the timer expires, stop the timer and wait to receive a continue upgrade command.

[0031] Step S208: Upon receiving the first continue upgrade command for the specified object, resume the upgrade process and upgrade the next batch of nodes.

[0032] The node upgrade control method in this embodiment can be applied to the field of computer technology, specifically to scenarios involving the phased upgrade of cluster systems. A cluster system (such as a server cluster, storage cluster, or database cluster) is a distributed system. A distributed system is a network composed of multiple independent computers or devices that can connect to each other and work collaboratively through a communication network. They can share computing resources, storage resources, data, and files to achieve common tasks and goals. Externally, a distributed system presents itself as a unified system. A cluster system is a special form of distributed system, primarily used to improve system performance, availability, and scalability. A cluster system typically consists of a group of tightly coupled computers that share the same network and storage resources, appearing externally as a single, more powerful computer.

[0033] To ensure system security, stability, and performance optimization, cluster systems require regular software version upgrades, patch updates, or configuration changes. During the upgrade process, to avoid the entire cluster becoming unavailable due to simultaneous upgrades of a large number of nodes, a batch upgrade approach is typically used. This involves dividing the nodes within the cluster into several batches, with each batch containing multiple nodes to be upgraded, and performing the upgrade operation on the cluster system batch by batch.

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

[0035] However, the aforementioned intermediate intervals in related technologies are preset and fixed, lacking flexibility when facing complex cluster systems undergoing upgrades. Users cannot externally modify or dynamically adjust the length of this interval based on actual conditions (such as inspection complexity, number of hosts, and problem-solving speed), nor can they manually end or start the waiting timer in advance. For example, if the upgrade environment for the next batch of nodes is relatively simple, with fewer hosts, simpler inspections, or the ability to quickly restore the required state, relevant personnel can quickly complete the upgrade preparation for the next batch of nodes, but still need to wait for the same long intermediate interval, resulting in unnecessary time waste and extending the overall upgrade cycle. Alternatively, if the upgrade environment for the next batch of nodes is more complex, or if the inspection reveals that the host connection status or volume dependency status does not meet the upgrade requirements, relevant personnel need to spend a longer time inspecting or fixing the problem. However, the same long intermediate interval leads to insufficient time, potentially resulting in business interruption due to the inability to complete the problem fix. Therefore, it is evident that the node upgrade control methods in related technologies suffer from insufficient flexibility.

[0036] To at least partially solve the aforementioned technical problems, this embodiment includes a first upgrade mode in the cluster system upgrade process. Unlike the fixed intermediate interval in related technologies, a timer is started after the upgrade of a batch of nodes is completed. The timing of this timer is positively correlated with the environmental complexity of the next batch of nodes. Alternatively, the user can stop the timer by pausing the upgrade command until the user completes the upgrade preparation for the next batch of nodes and issues the first command to continue the upgrade before starting the upgrade of the next batch of nodes. The cluster system can adaptively adjust the timing of the timer based on the complexity of the deployment environment. The user can also flexibly adjust the upgrade timing of the next batch of nodes according to actual needs, thereby improving the flexibility of node upgrade control.

[0037] In this embodiment, in response to receiving an upgrade command from a specified object, the upgrade process of the cluster system is initiated. 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 according to their respective batches. Optionally, the specified object can be a user, and the upgrade command can be given by the user immediately or automatically triggered at a predetermined time. Before giving the upgrade command, the resources required for the cluster system upgrade process have been configured. During the upgrade process, the upgrade resources can be controlled and scheduled through a state machine to upgrade the cluster system. Before initiating the cluster system upgrade process, to avoid the entire cluster becoming unavailable due to simultaneous upgrades 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 can be automatically divided according to the specified number. Alternatively, the user can divide the nodes to be upgraded in the cluster system according to their needs. Alternatively, the environmental complexity of the nodes deployed in each batch can be specified to ensure that the nodes in each batch have similar environmental complexity. This embodiment does not impose any limitations on this.

[0038] When the cluster system adopts the first upgrade mode, and at least two batches contain a next batch following the current batch, the upgrade process is paused upon completion of the upgrade of the nodes in the current batch, and a timer is started. The first upgrade mode controls the upgrade timing of different batches of nodes through a timer, and the timer's duration is positively correlated with the environmental complexity of the next batch of nodes. Here, "at least two batches contain a next batch following the current batch" means that the nodes in the current batch are not in the last batch. In this case, the upgrade of all nodes in the cluster system is completed upon completion of the upgrade of the nodes in the current batch, and there is no need to upgrade the next batch of nodes.

[0039] Optionally, the timer's timing period can be based on a preset initial timing period, and adjusted by increasing or decreasing the preset initial timing period based on the environmental complexity of the next batch of node deployments. Alternatively, a model can be deployed, which can be trained based on the time taken by users to complete the upgrade preparation for the next batch of nodes in the historical cluster system upgrade records. This model is used to automatically set different timing periods for different batches based on environmental complexity or other characteristics, so as to ensure that the timing period conforms to the actual upgrade environment and improves the flexibility of upgrade control.

[0040] Here, the timing period of the timer is positively correlated with the environmental complexity of the next batch of nodes deployed. That is, if the environmental complexity of the next batch of nodes is high, a longer timing period can be configured so that users have enough time to perform the checks; if the environmental complexity of the next batch of nodes is low, a shorter timing period can be configured to reduce the redundant waiting time after the user completes the checks and prevent time waste.

[0041] If a pause upgrade command is received for a specified object before the timer expires, the timer is stopped, and the system waits for a resume upgrade command. Before upgrading the next batch of nodes, the user may discover unexpected problems that need to be fixed. To avoid service interruptions caused by inspection delays due to insufficient timer duration, in this embodiment, the user can input a pause upgrade command. The cluster system can respond to the pause upgrade command by stopping the timer until the user has fixed the problem and issued a first resume upgrade command. Upon receiving the first resume upgrade command for the specified object, the upgrade process resumes, and the next batch of nodes is upgraded.

[0042] It should be noted that the above-mentioned stop timer means that the timer will not be activated until the next batch of nodes is upgraded. The upgrade process will only resume upon receiving the first continue upgrade command, and the next batch of nodes will be upgraded. Users have sufficient time to check and fix problems, and the upgrade will continue after confirmation. The timer can be restarted after the next batch of nodes has been upgraded.

[0043] According to the embodiments provided in this application, in response to receiving an upgrade command from a specified object, an upgrade process of the cluster system is initiated. 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 according to their respective batches. If the cluster system adopts a first upgrade mode, and there is a next batch within the current batch among 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 a timer, and the timer's duration is positively correlated with the environmental complexity of the next batch of nodes. If a pause upgrade command from a specified object is received before the timer's duration expires, the timer is stopped, and the system waits to receive a continue upgrade command. If a first continue upgrade command from a specified object is received, the upgrade process is resumed, and the next batch of nodes is upgraded. Since the timing of the timer controlling the timing of the next batch of node upgrades in the first upgrade mode is positively correlated with the complexity of the node deployment environment, the waiting time can be adaptively adjusted for different deployment environments. Furthermore, users can freely control the start time of the next batch of node upgrades through pause upgrade commands and first continue upgrade commands, which solves the problem of insufficient flexibility in node upgrade control methods in related technologies and improves the flexibility of node upgrade control.

[0044] In one exemplary embodiment, after starting the timer, the method further includes: if a second continue upgrade instruction for a specified object is received before the timer expires, stopping the timer and upgrading the next batch of nodes; and upgrading the next batch of nodes when the timer expires.

[0045] In this embodiment, similar to related technologies, the next batch of nodes can be automatically upgraded when the timer expires. Furthermore, to avoid unnecessary waiting time, if the user completes preparations for upgrading the next batch of nodes ahead of schedule before the timer expires, the user can issue a second continue-upgrade command to instruct the next batch of nodes to start upgrading earlier. If the second continue-upgrade command is received from the specified object before the timer expires, the timer is stopped, and the next batch of nodes is upgraded.

[0046] Optionally, after the timer expires or a second upgrade instruction is received, before upgrading the next batch of nodes, the cluster system can remind users to check the host connection status and automatically perform some automated basic checks (such as volume dependency checks) to ensure that user services are not interrupted after the upgraded node goes offline.

[0047] This embodiment allows for automatic upgrades of the next batch of nodes when the timer expires, reducing the user's operational burden; alternatively, the user can issue a second command to continue upgrading, thus accelerating the upgrade of the next batch of nodes and reducing unnecessary waiting time, preventing wasted time.

[0048] In one exemplary embodiment, before starting the timer, the method further includes: detecting the environmental complexity of the next batch of node deployments, 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; and configuring the timer duration based on the environmental complexity of the next batch of node deployments.

[0049] Similar to the aforementioned embodiments, in order to improve the intelligence of the first upgrade mode, the environmental complexity of the next batch of node deployments can be checked, and the timer's timing period can be intelligently configured based on the environmental complexity. The timer's timing period is positively correlated with the environmental complexity of the next batch of node deployments. That is, if the environmental complexity of the next batch of node deployments is high, a longer timing period can be configured so that the user has enough time to check; if the environmental complexity of the next batch of node deployments is low, a shorter timing period can be configured to reduce the redundant waiting time after the user completes the check and prevent time waste.

[0050] In this embodiment, when the current upgrade mode is the first upgrade mode, the environmental complexity of the next batch of node deployments is detected before the timer is started. 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 nodes in the next batch. This set of configuration parameters includes the number of host connections. Optionally, in addition to the number of host connections, the parameter values ​​of this set of configuration parameters may also include network bandwidth and latency, storage volume dependency status, application service status, node health status, etc.

[0051] After checking the environmental complexity of the next batch of node deployments, the timer's duration can be configured based on this complexity, where the timer's duration is positively correlated with the environmental complexity. Optionally, the timer's duration configured based on environmental complexity can be set within a limited minimum and maximum range; for example, the minimum duration should not be less than five minutes and the maximum duration should not exceed sixty minutes. Furthermore, if a pause upgrade command is received under the second upgrade model, the current cluster system can be considered to have a significant risk of problems, and the timer's duration configured for the next batch of nodes can be increased accordingly to ensure sufficient time for problem checking and handling.

[0052] This embodiment checks the environmental complexity of the next batch of node deployments and configures the timer's timing based on the environmental complexity, which can solve the problem of fixed timer timing in related technologies and improve the flexibility and intelligence of cluster system upgrade control.

[0053] In one exemplary embodiment, the method further includes: upon receiving a status query instruction, responding to the status query instruction by displaying current upgrade status information 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 timer duration; remaining timer duration; operation suggestions.

[0054] To allow users to stay informed about the upgrade status and progress of the cluster system, users can retrieve status information via query commands. Upon receiving a status query command, the system responds by displaying the current upgrade status information on a display device. This information indicates at least one of the following: current upgrade progress, current status, total timer duration, remaining timer duration, and operational suggestions. It should be noted that the current upgrade status information displayed may include at least one or more of these five pieces of information. In some cases, only some of this information may be displayed. For example, in the first upgrade mode, if timers are not enabled, the total timer duration and remaining timer duration will not be displayed.

[0055] Correspondingly, the above method further includes: when the current upgrade status information is used to indicate the current upgrade progress, determining the current upgrade progress based on the total number of nodes to be upgraded and the total number of nodes already upgraded in the cluster system. The current upgrade progress is the overall upgrade progress of the cluster system, which can be determined based on the total number of nodes to be upgraded and the total number of nodes already upgraded in the cluster system. For example, the current upgrade progress can indicate the proportion of the total number of upgraded nodes to the total number of nodes to be upgraded. Optionally, 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 been upgraded.

[0056] The current status indicates the current upgrade status of the cluster system. The current status is one of the following four states: Upgrading, Waiting, Paused, and Abnormal Termination. Upgrading means that there are currently nodes upgrading. Waiting means that the upgrade is waiting for the timer to expire in the second upgrade mode. Paused means that the upgrade process is paused in the first upgrade mode or in the second upgrade mode after receiving a pause upgrade command. Abnormal Termination means that the upgrade process has encountered an abnormal situation and has been forced to stop the upgrade.

[0057] In the second upgrade mode, both the total timer duration and the remaining timer duration can be indicated. The total timer duration is the configured timer duration, and the remaining timer duration is the configured timer duration minus the countdown time. Optionally, the estimated start time for the next batch of nodes can also be indicated. This is achieved by adding the remaining timer duration to the current time.

[0058] Operation suggestions can be determined based on the current status. Optionally, if the current status is "waiting", the operation suggestion can be "wait"; if the current status is "paused", the operation suggestion can be "after checking, the user can choose to continue the upgrade"; if the current status is "abnormal termination", the operation suggestion can indicate the abnormal situation that triggered the abnormal termination, so that the user can quickly locate and handle the abnormality.

[0059] This embodiment makes the upgrade status transparent through real-time status queries, providing users with detailed upgrade status information, reducing troubleshooting costs, and allowing users to understand the current status at any time. Based on the current status, users can conduct risk assessments and flexibly adjust their next operational strategies, thus improving the visualization and controllability of the upgrade process.

[0060] In an exemplary embodiment, the method further includes: pausing the upgrade process and waiting to receive a continue upgrade command when the cluster system adopts a second upgrade mode and there is a next batch of the current batch in at least two batches, wherein the second upgrade mode is an upgrade mode that controls the upgrade timing of nodes in different batches through the continue upgrade command; and resuming the upgrade process and upgrading the nodes in the next batch when the second continue upgrade command is received.

[0061] To improve the flexibility of upgrade control, a second upgrade mode is set up in addition to the first upgrade mode. In the second upgrade mode, the timing of upgrades for different batches of nodes can be controlled by continuing the upgrade command.

[0062] The second upgrade mode differs from the intermediate interval method in related technologies. After completing the upgrade of a batch of nodes, the upgrade process can be automatically paused until the user completes the upgrade preparation for the next batch of nodes and gives the command to continue the upgrade before the upgrade of the next batch of nodes can begin. Users can flexibly adjust the upgrade timing of the next batch of nodes according to actual needs, thereby improving the flexibility of node upgrade control.

[0063] If the cluster system is using the second upgrade mode, and at least two batches contain a next batch following the current batch, the upgrade process is paused, awaiting a continuation upgrade command. The second upgrade mode controls the upgrade timing of nodes in different batches via the continuation upgrade command. In this mode, users can freely control the upgrade time for each batch of nodes. Users can enter the continuation upgrade command after confirming the next batch is ready for upgrade, ensuring sufficient time for checking and troubleshooting without wasting time due to redundant waiting. Upon receiving the second continuation upgrade command from the user, the system can resume the upgrade process and upgrade the next batch of nodes from the current batch.

[0064] Optionally, there is a first continue upgrade command and a second continue upgrade command. The two continue upgrade commands can be the same or different. For example, the user can enter the command "continue upgrade" in the same way. The system can intelligently parse the command as the first continue upgrade command or the second continue upgrade command according to the current status, and execute the corresponding process recovery operation.

[0065] Optionally, users can switch the upgrade mode for the next batch of nodes during the upgrade process. If the upgrade mode for the next batch of nodes is not switched, the current upgrade mode can be used after the next batch of nodes is upgraded. For example, if the current upgrade mode is the first upgrade mode, and the user switches the upgrade mode for the next batch of nodes, the second upgrade mode will be entered after the next batch of nodes is upgraded, that is, the upgrade process will be paused and wait to receive the command to continue upgrading. If the user does not switch the upgrade mode for the next batch of nodes, the first upgrade mode will be retained after the next batch of nodes is upgraded, that is, a timer will be started.

[0066] Through this embodiment, by setting a second upgrade mode, users can select and use an appropriate upgrade mode, thereby improving the flexibility of node upgrade control.

[0067] In an exemplary embodiment, the method further includes: when the cluster system adopts a first upgrade mode and there is a next batch of the current batch in at least two batches, in response to the completion of the upgrade of the nodes in the current batch, detecting the environmental complexity of the deployment of the nodes in the next batch, wherein 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, the set of configuration parameters including the number of host connections.

[0068] Here, the method for detecting the environmental complexity of the next batch of node deployments is similar to that in the aforementioned embodiments, and will not be repeated here.

[0069] Correspondingly, if the environmental complexity of the next batch of node deployments exceeds the specified complexity threshold, the cluster system will switch 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 the continue upgrade command.

[0070] If the environment complexity of the next batch of nodes is high (exceeding a specified complexity threshold), the pre-upgrade testing of the next batch of nodes may take an unpredictable and lengthy time. To allow users sufficient time to prepare for the upgrade, the upgrade mode can be switched from the first upgrade mode to the second upgrade mode if the environment complexity of the next batch of nodes exceeds the specified complexity threshold. That is, the upgrade process is paused before the upgrade of the next batch of nodes, and resumed only after the user is ready and submits a second command to continue the upgrade. Here, the specified complexity threshold can be set based on experience, for example, the number of host connections is greater than 100, 120, or other values. This embodiment does not limit this. Optionally, the switch to the second upgrade mode can be a temporary switch, that is, the switch to the second upgrade mode is only made before the upgrade of the next batch of nodes is completed, and the switch can be automatically made back to the first upgrade mode before the upgrade of the next batch of nodes (i.e., the next batch of nodes after the next batch of nodes) is completed; or it can be a retainable switch, that is, the switch to the second upgrade mode is made before the upgrade of the next batch of nodes is completed, and the second upgrade mode is maintained after the upgrade of the next batch of nodes is completed if the user does not actively switch the upgrade mode. This embodiment does not limit this.

[0071] This embodiment automatically switches to the second upgrade mode when the environment complexity of the next batch of node deployments exceeds a specified complexity threshold. This ensures that users have sufficient time to prepare when facing complex upgrade environments, reducing the risk of upgrade failure or business interruption.

[0072] In an exemplary embodiment, the nodes in the current batch are not the nodes in the first batch of the cluster system; after the upgrade process of the cluster system is started, the method further includes: pausing the upgrade process in response to the completion of the upgrade of the first batch of nodes; and resuming the upgrade process to upgrade the nodes in the second batch of the cluster system upon receiving a third continue upgrade command.

[0073] Upgrading the first batch of nodes in a cluster system is often prone to problems. To allow sufficient time for checking and resolving issues after the first batch of nodes is upgraded, the upgrade process can be automatically paused after the upgrade is completed, and resumed only upon receiving a third "continue upgrade" command to upgrade the next batch of nodes (the second batch of nodes in the cluster system). It's important to note that pausing the upgrade process after the first batch of nodes is upgraded does not default to the second upgrade mode. The default upgrade mode can be set before starting the cluster system's upgrade process. For example, even with the second upgrade mode as the default, the upgrade process can still be paused after the first batch of nodes is upgraded, and the second and subsequent batches of nodes will use the default upgrade mode (here, the first upgrade mode) and a timer to control the upgrade time of the next batch of nodes.

[0074] This embodiment provides users with a more intelligent and secure upgrade method by pausing the upgrade process after the first batch of nodes has been upgraded, thereby improving the controllability and intelligence of the upgrade process.

[0075] In one exemplary embodiment, the method further includes: suspending the upgrade process and issuing an exception message when at least one abnormal scenario in the abnormal scenario set is triggered; resuming the upgrade process in response to receiving a resume upgrade command; and restoring the specified batch of nodes corresponding to the rollback command to their state before the upgrade in response to receiving a rollback command.

[0076] To limit the damage to the cluster system caused by abnormalities in the upgrade process, a set of abnormal scenarios can be preset. If at least one of the abnormal scenarios in the set is triggered, the upgrade process will be stopped and an abnormality prompt message will be issued to remind the user to handle the abnormality in a timely manner.

[0077] In this embodiment, if at least one of the abnormal scenarios in the abnormal scenario set is triggered, the upgrade process is aborted and an abnormal prompt message is issued. Here, the abnormal scenario set may include common abnormal scenarios, such as node offline, upgrade failure, storage volume abnormality, etc. When any of these scenarios is triggered, the system will immediately terminate the upgrade process and issue an abnormal prompt message via a display device and / or an audio device. Optionally, when issuing the abnormal prompt message, the specific abnormal scenario that was triggered and its location can be simultaneously indicated. Recommended solutions can be preset for each abnormal scenario, and these solutions can be displayed simultaneously with the abnormal prompt message to facilitate user reference in handling the abnormality.

[0078] After handling the exception, the user can enter a "Restore Upgrade" command. The system can respond to this command and resume the upgrade process from where it was aborted. Alternatively, if the user encounters difficulties handling the exception, they can enter a "Rollback" command. The system can respond to this command and restore the specified batch of nodes corresponding to the rollback command to their state before the upgrade, allowing the user to begin handling the exception from the state before it occurred.

[0079] This embodiment enhances the security and controllability of the upgrade process by adding methods for anomaly checks, suspension, resumption of upgrades, and state rollback in the node upgrade process.

[0080] The node upgrade control method in the embodiments of this application will be explained below with reference to optional examples. Figure 3 This is a flowchart illustrating the initial setup of the node upgrade control method in this optional example, as follows: Figure 3 As shown, the initial setup process of this node upgrade control method may include: 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, each batch of nodes automatically enters a pause state after the upgrade is completed. In the first upgrade mode, the upgrade of each batch of nodes is controlled by a timer. The default timer duration is 30 minutes, and the timer duration can be adjusted by intelligently analyzing the environmental complexity during the upgrade process.

[0081] Figure 4 This is a flowchart illustrating the upgrade loop of the node upgrade control method in this optional example, as shown below. Figure 4 As shown, the upgrade cycle of this node upgrade control method may include: checking whether it is a first batch of nodes; if it is, it directly enters a pause state; if not, it checks whether it is in the first upgrade mode; if not, it also enters a pause state. In the pause state, it continues until a continue upgrade command is received to determine the next batch of nodes to be upgraded.

[0082] If it is the first upgrade mode, a timer is started, and the status is in a waiting state, with the remaining timer time displayed on the display device. The user can pause at any time. If the user does not pause, the upgrade process will proceed until the timer expires, and the next batch of nodes will be upgraded. If the user pauses, the upgrade process is paused, the timer is canceled, and the system enters a paused state until a command to continue the upgrade process is received to proceed with the upgrade of the next batch of nodes.

[0083] After determining that the next batch of nodes is ready to be upgraded, the upgrade is performed. After the upgrade is performed, it is checked whether there are any remaining batches. If there are no remaining batches, the upgrade ends. If there are remaining batches, the process returns to the initial check to see if it is the first batch of nodes, thus realizing a cyclical upgrade.

[0084] Figure 5 This is a flowchart illustrating the upgrade check process of the node upgrade control method in this optional example, as follows: Figure 5 As shown, the upgrade check process of this node upgrade control method may include: after upgrading a batch of nodes, checking whether the upgrade is successful; if unsuccessful, performing exception handling; if successful, recording the upgrade as successful, and determining whether the upgrade of the next batch of nodes has started; if not yet started, determining whether the user has switched upgrade modes; if switched, switching the upgrade mode to another upgrade mode; if not switched, continuing to use the current upgrade mode.

[0085] Figure 6 This is a flowchart illustrating the exception handling process of the node upgrade control method in this optional example, as follows: Figure 6 As shown, the exception handling process of this node upgrade control method may include: after an abnormal interruption occurs, the user handles the exception, and after the user handles the exception, they can choose to resume the upgrade or roll back the version. If the upgrade is resumed, the current upgrade mode is saved and the upgrade continues. If the version is rolled back, the nodes in the batch that triggered the exception are rolled back to their state before the upgrade.

[0086] This optional example provides two upgrade modes: a first upgrade mode and a second upgrade mode. Users can freely choose and flexibly switch between upgrade modes. During the upgrade process, users can pause the upgrade and start the upgrade of the next batch of nodes upon receiving a command to continue the upgrade. This allows for flexible control over the upgrade time of each batch of nodes, providing flexibility for cluster system upgrades.

[0087] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0088] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method.

[0089] Embodiments of this application also provide a node upgrade control device. Figure 7 This is a structural block diagram of a node upgrade control device according to an embodiment of this application, such as... Figure 7 As shown, the device includes:

[0090] The first startup unit 702 is used to start the upgrade process of the cluster system in response to receiving an upgrade command for a specified object. 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.

[0091] The first execution unit 704 is used to pause the upgrade process and start a timer in response to the completion of the upgrade of the nodes in the current batch when the cluster system adopts the first upgrade mode and there is a next batch of the current batch in at least two batches. The first upgrade mode is an upgrade mode that controls the upgrade timing of nodes in different batches through a timer. The timing of the timer is positively correlated with the environmental complexity of the deployment of the nodes in the next batch.

[0092] The second execution unit 706 is used to stop the timer and wait to receive a continue upgrade command if a pause upgrade command for a specified object is received before the timer expires.

[0093] The third execution unit 708 is used to resume the upgrade process and upgrade the next batch of nodes upon receiving the first continue upgrade command for the specified object.

[0094] Using the above device, in response to receiving an upgrade command from a specified object, the upgrade process of the cluster system is initiated. 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 according to their respective batches. If the cluster system is using the first upgrade mode, and there is a next batch within the current batch among 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 a timer, and the timer's duration is positively correlated with the environmental complexity of the next batch of nodes. If a pause upgrade command is received from a specified object before the timer's duration expires, the timer is stopped, and the system waits to receive a continue upgrade command. If a first continue upgrade command is received from a specified object, the upgrade process is resumed, and the next batch of nodes is upgraded. Since the timing of the timer controlling the timing of the next batch of node upgrades in the first upgrade mode is positively correlated with the complexity of the node deployment environment, the waiting time can be adaptively adjusted for different deployment environments. Furthermore, users can freely control the start time of the next batch of node upgrades through pause upgrade commands and first continue upgrade commands, which solves the problem of insufficient flexibility in node upgrade control methods in related technologies and improves the flexibility of node upgrade control.

[0095] In an exemplary embodiment, the apparatus further includes: a fourth execution unit, configured to stop the timer and upgrade the next batch of nodes if a second continue upgrade instruction for a specified object is received after the timer is started but before the timer expires; and an upgrade unit, configured to upgrade the next batch of nodes when the timer expires.

[0096] In an exemplary embodiment, the apparatus further includes: a first detection unit, configured to detect the environmental complexity of the next batch of node deployments before starting the timer, 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; and a configuration unit, configured to configure the timing period of the timer based on the environmental complexity of the next batch of node deployments.

[0097] In one exemplary embodiment, the above apparatus further includes: a display unit, configured to, upon receiving a status query instruction, display current upgrade status information via a display device in response to the status query instruction, wherein the current upgrade status information indicates 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; and operation suggestions.

[0098] In one exemplary embodiment, the apparatus further includes a determining unit, configured to determine the current upgrade progress based on the total number of nodes to be upgraded in the cluster system and the total number of nodes already upgraded in the cluster system, when the current upgrade status information is used to indicate the current upgrade progress.

[0099] In an exemplary embodiment, the apparatus further includes: a second detection unit, configured to, when the cluster system adopts a first upgrade mode and there is a next batch of the current batch in at least two batches, detect the environmental complexity of the next batch of node deployment in response to the completion of the node upgrade in the current batch, wherein the environmental complexity of the next batch of node deployment is determined based on the parameter values ​​of a set of configuration parameters corresponding to the nodes in the next batch, the set of configuration parameters including the number of host connections; and a switching unit, configured to, when the environmental complexity of the next batch of node deployment is higher than a specified complexity threshold, switch the upgrade mode adopted by the cluster system from the first upgrade mode to a second upgrade mode, wherein the second upgrade mode is an upgrade mode that controls the upgrade timing of different batches of nodes through a continue upgrade command.

[0100] In an exemplary embodiment, the apparatus further includes: a fifth execution unit, configured to pause the upgrade process and wait to receive a continue upgrade command when the cluster system adopts a second upgrade mode and there is a next batch of the current batch in at least two batches, wherein the second upgrade mode is an upgrade mode that controls the upgrade timing of nodes in different batches through the continue upgrade command; and a sixth execution unit, configured to resume the upgrade process and upgrade the nodes in the next batch upon receiving the second continue upgrade command.

[0101] In an exemplary embodiment, the nodes in the current batch are not the nodes in the first batch of the cluster system; the apparatus further includes: a pause unit after starting the upgrade process of the cluster system, configured to pause the upgrade process in response to the completion of the upgrade of the first batch of nodes; and a first recovery unit, configured to resume the upgrade process upon receiving a third continue upgrade command, so as to upgrade the nodes in the second batch of the cluster system.

[0102] In one exemplary embodiment, the above apparatus further includes: a seventh execution unit, configured to terminate the upgrade process and issue an exception prompt message when at least one of the exception scenarios in the exception scenario set is triggered; a second recovery unit, configured to resume the upgrade process in response to a recovery upgrade command received; and a third recovery unit, configured to restore the nodes of a specified batch corresponding to the rollback command to their state before the upgrade in response to a rollback command received.

[0103] For a description of the features in the embodiment corresponding to the node upgrade control device, please refer to the relevant description of the embodiment corresponding to the node upgrade control method, which will not be repeated here.

[0104] Embodiments of this application also provide an electronic device, including a memory and a processor, wherein the memory stores a computer program and the processor is configured to run the computer program to perform the steps in any of the above-described embodiments of the node upgrade control method.

[0105] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above-described node upgrade control method embodiments at runtime.

[0106] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[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. 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.

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: If the cluster system is using the second upgrade mode and there is a next batch of the current batch in 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.

7. The node upgrade control method according to any one of claims 1 to 6, 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.

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

Images