Automatic version upgrading method, computer program product and electronic equipment

Abstract

The invention provides an automatic version upgrading method, a computer program product and electronic equipment, and the method comprises the steps: receiving an upgrading instruction, the upgrading instruction at least comprises an upgrading type and version package information, and the upgrading type comprises one of the following: a first upgrading type, a second upgrading type, a third upgrading type and a fourth upgrading type, the first upgrading type is pilot upgrading and does not push a version package immediately, the second upgrading type is full-node upgrading and does not push the version package immediately, the third upgrading type is pilot upgrading and pushes the version package immediately, and the fourth upgrading type is full-node upgrading and pushes the version package immediately; obtaining a corresponding version package according to the information of the version package; and determining a corresponding upgrading strategy according to the upgrading type, and executing the upgrading strategy, so that the application node completes upgrading according to the version package. According to the method and the device, the problems of high error rate and low upgrading efficiency in the upgrading process caused by numerous nodes involved in the distributed system in the prior art are solved.

Description

Technical Field

[0001] The present application relates to the technical field of version upgrade, and in particular to a version automatic upgrade method, a computer-readable storage medium, a computer program product, and an electronic device. Background Art

[0002] During the regular upgrade process of a distributed system, since many nodes are involved, the new version needs to be uploaded to the corresponding nodes and take effect within a limited time. This process has a high error rate and low upgrade efficiency.

[0003] Currently, there are many problems with the manual upload version upgrade method, such as slow upgrade speed, prone to errors, no support for simultaneous upgrade of multiple systems, and easy omissions or operational errors. Summary of the invention

[0004] The main purpose of the present application is to provide a version automatic upgrade method, a computer-readable storage medium, a computer program product and an electronic device, so as to at least solve the problem in the prior art that the distributed system has a high error rate and low upgrade efficiency in the upgrade process due to the involvement of numerous nodes.

[0005] In order to achieve the above-mentioned purpose, according to one aspect of the present application, a method for automatic version upgrade is provided, there are multiple application nodes, the method comprising: receiving an upgrade instruction, the upgrade instruction at least comprising information about an upgrade type and a version package, the upgrade type comprising one of the following: a first upgrade type, a second upgrade type, a third upgrade type and a fourth upgrade type, the first upgrade type being a pilot upgrade without immediately pushing the version package, the second upgrade type being a full-node upgrade without immediately pushing the version package, the third upgrade type being a pilot upgrade with an immediate push of the version package, the fourth upgrade type being a full-node upgrade with an immediate push of the version package, wherein the first upgrade type indicates that a target number of application nodes need to be upgraded and do not need to be upgraded. Immediately notify the application nodes to download the version package, the target number is less than the total number of application nodes, the second upgrade type indicates that all the application nodes need to be upgraded and there is no need to immediately notify the application nodes to download the version package, the third upgrade type indicates that the target number of application nodes need to be upgraded and the application nodes need to be immediately notified to download the version package, and the fourth upgrade type indicates that all the application nodes need to be upgraded and there is a need to immediately notify the application nodes to download the version package; according to the information of the version package, obtain the corresponding version package; according to the upgrade type, determine the corresponding upgrade strategy, and execute the upgrade strategy so that the application nodes complete the upgrade according to the version package.

[0006] Optionally, the upgrade type is the first upgrade type. According to the upgrade type, a corresponding upgrade strategy is determined, and the upgrade strategy is executed so that the application node completes the upgrade according to the version package, including: upon receiving an upload instruction, uploading the version package to a distributed file system, wherein the upload instruction is an instruction generated in response to a first predetermined operation acting on an interface of a management and control platform; upon receiving a send instruction, sending a download instruction to the target number of application nodes so that the application nodes download the version package from the distributed file system, wherein the send instruction is an instruction generated in response to a second predetermined operation acting on the interface; upon receiving a download success instruction sent by the application node, sending an operation instruction to the application node so that the application node performs a restart operation or a hot load operation to complete the upgrade, and the download success instruction indicates that the application node has successfully downloaded the version package.

[0007] Optionally, the upgrade type is the third upgrade type. According to the upgrade type, a corresponding upgrade strategy is determined, and the upgrade strategy is executed so that the application node completes the upgrade according to the version package, including: upon receiving an upload instruction, uploading the version package to a distributed file system, wherein the upload instruction is an instruction generated in response to a first predetermined operation acting on an interface of a management and control platform; sending a download instruction to the target number of application nodes so that the application nodes download the version package from the distributed file system; upon receiving a download success instruction sent by the application node, sending an operation instruction to the application node so that the application node performs a restart operation or a hot load operation to complete the upgrade, and the download success instruction indicates that the application node has successfully downloaded the version package.

[0008] Optionally, the upgrade type is the fourth upgrade type. According to the upgrade type, a corresponding upgrade strategy is determined, and the upgrade strategy is executed so that the application node completes the upgrade according to the version package, including: uploading the version package to the distributed file system; sending a download instruction to all the application nodes so that the application nodes download the version package from the distributed file system; upon receiving a download success instruction sent by the application node, sending an operation instruction to the application node so that the application node performs a restart operation or a hot load operation to complete the upgrade, and the download success instruction indicates that the application node has successfully downloaded the version package.

[0009] Optionally, the upgrade type is the second upgrade type. According to the upgrade type, a corresponding upgrade strategy is determined, and the upgrade strategy is executed so that the application node completes the upgrade according to the version package, including: an upload step, uploading the version package to the distributed file system; a first sending step, upon receiving a sending instruction, sending a download instruction to the target number of application nodes, so that the application nodes download the version package from the distributed file system, wherein the sending instruction is an instruction generated in response to a second predetermined operation acting on the interface of the management and control platform; a second sending step, upon receiving a download success instruction sent by the application node, sending an operation instruction to the application node, so that the application node performs a restart operation or a hot load operation to complete the upgrade, and the download success instruction indicates that the application node has successfully downloaded the version package; a loop step, repeatedly executing the upload step, the first sending step and the second sending step in sequence at least once until all the application nodes have completed the upgrade.

[0010] Optionally, the distributed file system includes FastDFS (Fast Distributed File System). After sending an operation instruction to the application node, the method further includes: receiving an upgrade success instruction sent by the application node to display an upgrade success status on an interface of a management and control platform, wherein the upgrade success instruction indicates that the application node has been successfully upgraded, and the upgrade success status is a status indicating that the application node has been successfully upgraded.

[0011] Optionally, the method further includes: in the case where the download success instruction is not received, receiving a first resend instruction, and resending the download instruction to the application node, wherein the first resend instruction is an instruction generated in response to a third predetermined operation acting on the interface; in the case where the upgrade success instruction is not received, receiving a second resend instruction, and resending the operation instruction to the application node, wherein the second resend instruction is an instruction generated in response to a fourth predetermined operation acting on the interface.

[0012] According to another aspect of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute any one of the above-described automatic version upgrade methods.

[0013] According to another aspect of the present application, a computer program product is provided, comprising computer instructions, wherein when the computer instructions are executed by a processor, any one of the above-described automatic version upgrade methods is implemented.

[0014] According to another aspect of the present application, an electronic device is provided, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include a method for executing any one of the described automatic version upgrade methods.

[0015] Applying the technical solution of the present application, there are multiple application nodes, which first receive an upgrade instruction including information about the upgrade type and version package, then obtain the corresponding version package according to the information of the version package, and then determine the corresponding upgrade strategy according to the upgrade type, and finally execute the upgrade strategy so that the application node completes the upgrade according to the version package, wherein the upgrade type includes one of a first upgrade type, a second upgrade type, a third upgrade type and a fourth upgrade type, the first upgrade type is a pilot upgrade without immediately pushing the version package, the second upgrade type is a full-node upgrade without immediately pushing the version package, the third upgrade type is a pilot upgrade with an immediate push of the version package, and the fourth upgrade type is a full-node upgrade with an immediate push of the version package. Compared with the problem of high error rate and low upgrade efficiency in the distributed system in the prior art due to the involvement of numerous nodes, the present application can automatically obtain the corresponding version package and determine the upgrade strategy according to the upgrade type by receiving upgrade instructions including upgrade type and version package information. This means that the upgrade process does not require human intervention, reduces human errors, and improves the efficiency and reliability of the upgrade. In addition, four different upgrade types are provided to adapt to different upgrade needs and scenarios, and personalized customized upgrades are supported. By setting clear upgrade types and corresponding clear upgrade strategies, upgrades can be performed according to the specific circumstances of each node, reducing uncertainty in the upgrade process. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The drawings constituting part of the present application are used to provide a further understanding of the present application. The exemplary embodiments and descriptions of the present application are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0017] Figure 1 A hardware structure block diagram of a mobile terminal for executing an automatic version upgrade method provided in an embodiment of the present application is shown;

[0018] Figure 2 A schematic diagram of a process of an automatic version upgrade method provided according to an embodiment of the present application is shown;

[0019] Figure 3 A schematic diagram of the system architecture of a version automatic upgrade method provided according to an embodiment of the present application is shown.

[0020] The above drawings include the following reference numerals:

[0021] 102, processor; 104, memory; 106, transmission device; 108, input and output devices. DETAILED DESCRIPTION

[0022] It should be noted that, in the absence of conflict, the embodiments and features in the embodiments of the present application can be combined with each other. The present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0023] In order to enable those skilled in the art to better understand the solution of the present application, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present application.

[0024] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present application described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0025] As introduced in the background technology, the distributed system in the prior art involves many nodes, resulting in a high error rate and low upgrade efficiency in the upgrade process. To solve the above problems, the embodiments of the present application provide a version automatic upgrade method, a computer-readable storage medium, a computer program product and an electronic device.

[0026] The technical solutions in the embodiments of the present invention will be described clearly and completely below in conjunction with the accompanying drawings in the embodiments of the present invention.

[0027] The method embodiments provided in the embodiments of the present application can be executed in a mobile terminal, a computer terminal or a similar computing device. Taking running on a mobile terminal as an example, Figure 1 1 is a hardware structure block diagram of a mobile terminal of an automatic version upgrade method according to an embodiment of the present invention. Figure 1 As shown, the mobile terminal may include one or more ( Figure 1Only one is shown in the figure) a processor 102 (the processor 102 may 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, wherein the mobile terminal may also include a transmission device 106 and an input / output device 108 for communication functions. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the mobile terminal. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations shown.

[0028] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the version automatic upgrade method in the embodiment of the present invention. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, the above method is implemented. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories can be connected to the mobile terminal via a network. Examples of the above-mentioned network include but are not limited to the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof. The transmission device 106 is used to receive or send data via a network. The above-mentioned specific network example may include a wireless network provided by a communication provider of the mobile terminal. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as 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 may be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.

[0029] In this embodiment, a method for automatic version upgrade running on a mobile terminal, a computer terminal or a similar computing device is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0030] Figure 2 Flowchart of the method for automatic version upgrade according to an embodiment of the present application. Figure 2 As shown, the method comprises the following steps:

[0031] Step S201, receiving an upgrade instruction, the upgrade instruction at least including information about an upgrade type and a version package, the upgrade type including one of the following: a first upgrade type, a second upgrade type, a third upgrade type and a fourth upgrade type, the first upgrade type being a pilot upgrade without immediately pushing the version package, the second upgrade type being a full-node upgrade without immediately pushing the version package, the third upgrade type being a pilot upgrade with an immediate push of the version package, the fourth upgrade type being a full-node upgrade with an immediate push of the version package, wherein the first upgrade type indicates that a target number of the application nodes need to be upgraded and it is not necessary to immediately notify the application nodes to download the version package, the target number being less than the total number of the application nodes, the second upgrade type indicating that all of the application nodes need to be upgraded and it is not necessary to immediately notify the application nodes to download the version package, the third upgrade type indicating that the target number of application nodes need to be upgraded and it is necessary to immediately notify the application nodes to download the version package, and the fourth upgrade type indicating that all of the application nodes need to be upgraded and it is necessary to immediately notify the application nodes to download the version package;

[0032] Step S202, obtaining the corresponding version package according to the information of the version package;

[0033] Step S203: Determine a corresponding upgrade strategy according to the upgrade type, and execute the upgrade strategy so that the application node completes the upgrade according to the version package.

[0034] Through the above embodiment, there are multiple application nodes, firstly, an upgrade instruction including information of an upgrade type and a version package is received, then according to the information of the version package, a corresponding version package is obtained, and then according to the upgrade type, a corresponding upgrade strategy is determined, and finally the upgrade strategy is executed, so that the application node completes the upgrade according to the version package, wherein the upgrade type includes one of a first upgrade type, a second upgrade type, a third upgrade type and a fourth upgrade type, the first upgrade type is a pilot upgrade without immediately pushing the version package, the second upgrade type is a full-node upgrade without immediately pushing the version package, the third upgrade type is a pilot upgrade with an immediate push of the version package, and the fourth upgrade type is a full-node upgrade with an immediate push of the version package. Compared with the problem of high error rate and low upgrade efficiency in the distributed system in the prior art due to the involvement of numerous nodes, the present application can automatically obtain the corresponding version package and determine the upgrade strategy according to the upgrade type by receiving upgrade instructions including upgrade type and version package information. This means that the upgrade process does not require human intervention, reduces human errors, and improves the efficiency and reliability of the upgrade. In addition, four different upgrade types are provided to adapt to different upgrade needs and scenarios, and personalized customized upgrades are supported. By setting clear upgrade types and corresponding clear upgrade strategies, upgrades can be performed according to the specific circumstances of each node, reducing uncertainty in the upgrade process.

[0035] Specifically, different upgrade types will present different front-end upgrade interfaces (i.e., the interface of the management and control platform).

[0036] In an optional scheme, the above-mentioned upgrade type is the above-mentioned first upgrade type. According to the above-mentioned upgrade type, the corresponding upgrade strategy is determined, and the above-mentioned upgrade strategy is executed so that the above-mentioned application node completes the upgrade according to the above-mentioned version package, including: when an upload instruction is received, the above-mentioned version package is uploaded to the distributed file system, wherein the above-mentioned upload instruction is an instruction generated in response to a first predetermined operation acting on the interface of the management and control platform; when a send instruction is received, a download instruction is sent to the above-mentioned target number of the above-mentioned application nodes, so that the above-mentioned application nodes download the above-mentioned version package from the above-mentioned distributed file system, wherein the above-mentioned send instruction is an instruction generated in response to a second predetermined operation acting on the above-mentioned interface; when a download success instruction is received from the above-mentioned application node, an operation instruction is sent to the above-mentioned application node, so that the above-mentioned application node performs a restart operation or a hot load operation to complete the upgrade, and the above-mentioned download success instruction indicates that the above-mentioned application node has successfully downloaded the above-mentioned version package. In this embodiment, uploading the version package to the distributed file system can effectively manage and distribute the version package, further improving the efficiency and reliability of the upgrade process. By specifying a target number of application nodes for upgrading, fine control of the upgrade process can be achieved. For example, a pilot upgrade can be performed on a small number of nodes first to verify the stability of the new version before full promotion. After the application node successfully downloads the version package, a restart or hot loading operation is performed by sending an operation instruction to ensure that the new version takes effect immediately. At the same time, the hot loading operation can also reduce service interruption time and improve system availability.

[0037] Specifically, if the user selects the first upgrade type, the system item on the interface will be in a [locked] state, and the user needs to click the lock to upload the version package. However, at this time, the management and control platform will not upgrade the system item. The operator needs to select some application nodes of the system item to pilot the [version download] notification.

[0038] Specifically, the version package download address and package name data are sent to the application node.

[0039] Specifically, distributed file system: A distributed file system is a plug-and-play system that is deployed in the consumer and provider systems respectively. It is responsible for handling the interaction between consumers and providers. The system adopts a distributed architecture and can be flexibly deployed in various systems to provide high availability and stability. Application node: An application node is a node in a distributed file system. Its main responsibility is to receive data information pushed by the management and control platform, and to register or pull applications from the registration center when it starts, and to register application information with the management and control platform. Management and control platform: The management and control platform is a configuration management platform developed to adapt to the distributed file system. It can obtain configuration information in both directions, support the management and control platform to push data, and obtain the required configuration information and send system monitoring information through heartbeat detection. Through the management and control platform, the stable operation of the system can be effectively guaranteed.

[0040] According to some exemplary embodiments of the present application, the upgrade type is the third upgrade type, and according to the upgrade type, the corresponding upgrade strategy is determined, and the upgrade strategy is executed so that the application node completes the upgrade according to the version package, including: in the case of receiving an upload instruction, uploading the version package to the distributed file system, wherein the upload instruction is an instruction generated in response to a first predetermined operation acting on the interface of the control platform; sending a download instruction to the target number of application nodes, so that the application node downloads the version package from the distributed file system; in the case of receiving a download success instruction sent by the application node, sending an operation instruction to the application node, so that the application node performs a restart operation or a hot load operation to complete the upgrade, and the download success instruction indicates that the application node has successfully downloaded the version package. In this embodiment, the system can identify and send download instructions to the target number of application nodes, which means that a specific node group can be upgraded instead of all nodes in the entire network, so that the upgrade process can be more finely controlled, and the application node can automatically download and upgrade to the new version, thereby further improving the efficiency and reliability of the distributed system upgrade, further reducing the possibility of human error, and allowing the new version to be deployed to the selected application node faster.

[0041] Specifically, if the user selects the third upgrade type, the system item on the interface will be in the [locked] state, and the user needs to click the lock to upload the version package. At this time, the management and control will automatically issue a [version download] notification to the target number of application nodes under the system item.

[0042] In other embodiments, the above-mentioned upgrade type is the above-mentioned fourth upgrade type. According to the above-mentioned upgrade type, the corresponding upgrade strategy is determined, and the above-mentioned upgrade strategy is executed so that the above-mentioned application node completes the upgrade according to the above-mentioned version package, including: uploading the above-mentioned version package to the distributed file system; sending a download instruction to all the above-mentioned application nodes so that the above-mentioned application nodes download the above-mentioned version package from the above-mentioned distributed file system; in the case of receiving the download success instruction sent by the above-mentioned application node, sending an operation instruction to the above-mentioned application node so that the above-mentioned application node performs a restart operation or a hot load operation to complete the upgrade, and the above-mentioned download success instruction indicates that the above-mentioned application node has successfully downloaded the above-mentioned version package. In this embodiment, sending a download instruction to all application nodes ensures that all nodes can start downloading the new version package at the same time, which can further speed up the upgrade process.

[0043] Specifically, if the user selects the fourth upgrade type, the management and control platform will upload the version package under the selected system item to the distributed file system. After the upload is successful, the system item on the interface is in a [check] state, and the management and control platform will automatically issue a [version download] notification to all application nodes under the system item.

[0044] According to some other exemplary embodiments of the present application, the above-mentioned upgrade type is the above-mentioned second upgrade type. According to the above-mentioned upgrade type, the corresponding upgrade strategy is determined, and the above-mentioned upgrade strategy is executed so that the above-mentioned application node completes the upgrade according to the above-mentioned version package, including: an upload step, uploading the above-mentioned version package to the distributed file system; a first sending step, upon receiving a sending instruction, sending a download instruction to the above-mentioned target number of the above-mentioned application nodes, so that the above-mentioned application nodes download the above-mentioned version package from the above-mentioned distributed file system, wherein the above-mentioned sending instruction is an instruction generated in response to a second predetermined operation acting on the interface of the management and control platform; a second sending step, upon receiving a download success instruction sent by the above-mentioned application node, sending an operation instruction to the above-mentioned application node, so that the above-mentioned application node performs a restart operation or a hot load operation to complete the upgrade, and the above-mentioned download success instruction indicates that the above-mentioned application node has successfully downloaded the above-mentioned version package; a loop step, repeatedly executing the above-mentioned upload step, the above-mentioned first sending step and the above-mentioned second sending step in sequence at least once until all of the above-mentioned application nodes have completed the upgrade. In this embodiment, the application nodes are upgraded in batches until all the application nodes are upgraded. In this way, the upgrade of all the application nodes can be completed without affecting the stability of the entire system, thereby ensuring the controllability of the upgrade process.

[0045] Specifically, if the user selects the second upgrade type, the management and control platform will upload the version package under the selected system item to the distributed file system. At this time, the system item on the interface is in the [check] state, but the management and control platform will not upgrade the system item. The operator is required to select some application nodes under the system item for pilot [version download] notification and repeat the process to achieve version upgrade of the remaining application nodes until all application nodes have completed the version upgrade (i.e., upgrade the application nodes in batches).

[0046] In some other optional schemes of the present application, the above-mentioned distributed file system includes FastDFS, and after sending the operation instruction to the above-mentioned application node, the above-mentioned method further includes: receiving the upgrade success instruction sent by the above-mentioned application node to display the upgrade success status on the interface of the management and control platform, wherein the above-mentioned upgrade success instruction indicates that the above-mentioned application node has been successfully upgraded, and the above-mentioned upgrade success status is a status indicating that the above-mentioned application node has been successfully upgraded. In this embodiment, the upgrade success status displayed on the interface of the management and control platform provides an intuitive view for the user, so that the user can clearly see which application nodes have been successfully upgraded and which have not been upgraded, thereby facilitating the management and monitoring of the entire upgrade process.

[0047] Specifically, after the application node is successfully upgraded, the upgrade status is automatically updated to the management and control platform for status display.

[0048] In some further optional schemes of the present application, the above method further includes: receiving a first resend instruction, and resending the above download instruction to the above application node, in the case where the above download success instruction is not received, wherein the above first resend instruction is an instruction generated in response to a third predetermined operation acting on the above interface; receiving a second resend instruction, and resending the above operation instruction to the above application node, in the case where the above upgrade success instruction is not received, wherein the above second resend instruction is an instruction generated in response to a fourth predetermined operation acting on the above interface. In this embodiment, through the resend mechanism, the system can more stably handle various abnormal situations that may occur during the upgrade process, ensuring that the system can still maintain normal upgrade operations when facing unstable factors, thereby further improving the stability and reliability of the overall system.

[0049] Specifically, exception handling: If no response is received from the application node during the [version download] process or a "reception failure" prompt is displayed, you can manually send and retry the upgrade on the interface; if a non-000000 is returned or no response is received from the application node during the [version upgrade] process, you can manually send and retry the upgrade on the interface.

[0050] Specifically, Figure 3 The system architecture diagram of a version automatic upgrade method provided according to an embodiment of the present application is shown. Figure 3 As shown in the figure, start upgrading: this module is the starting point of upgrading process automation. After receiving the successful response at the front end of the control platform, a Web request is initiated to the back end interface of the control platform through HTTP+Json, thereby triggering the upgrading process; upload version package: after the upgrading is successfully triggered, the control platform will call the upload API (Application Programming Interface) of FastDFS (distributed file system) through HTTP protocol to upload the version package to FastDFS distributed file system. This module ensures the safe transmission and storage of the version package; version upgrading: after the version package is successfully uploaded to FastDFS, the front end of the control platform will initiate a Web request and call the back end interface to generate a notification task through HTTP+Json. This task will notify the application node to download the version package uploaded to FastDFS, thereby realizing the version upgrading; restart / hot loading: after the version package is successfully downloaded, the front end of the control platform will initiate a Web request again and call the back end interface to generate a notification task through HTTP+Json. This task will notify the application node to perform a restart or hot loading operation, thereby completing the entire upgrading process.

[0051] Specifically, Figure 3 In the process, the management and control platform sends instructions to the application node, so that the application node downloads the version package and restarts / hot loads. The application node returns the download results and upgrade results to the management and control platform through heartbeat.

[0052] In order to enable those skilled in the art to more clearly understand the technical solution of the present application, the implementation process of the automatic version upgrade method of the present application will be described in detail below in combination with specific embodiments. For example, the user needs to upgrade the service type version and selects the full node upgrade. On the management and control platform, the user can select the version package name to be upgraded and click the [Start Upgrade] button. In the pop-up interface, the user selects [Service Upgrade], and the system will enter the [Version Push], [Version Download] and [Version Upgrade] interfaces. In the [Version Push] module, the user can intuitively see the upload progress of multiple version packages. After waiting for the version package to be uploaded successfully, the management and control platform will automatically send the [Version Download] notification task to the application node. At this time, the user can view the download progress in the [Version Download] module. When the [Version Download] notification is successful, the management and control platform will automatically send the [Version Upgrade] notification task to the application node. The application node automatically updates the upgrade status to the management and control platform. The user can view the upgrade progress and wait for the progress bar to reach 100%, which means that the upgrade is completed. The whole process is designed to ensure the smooth upgrade of the service, improve the user experience, and ensure the stability of the system.

[0053] Specifically, in the version automatic upgrade method of the present application, 1) supports personalized customized upgrades: for systems with a large number of application nodes, grayscale release is particularly important during upgrades. In addition to supporting general upgrades, the upgrade process automation of the management and control platform also supports personalized customized upgrades. Before the upgrade, the upgraded application nodes are divided into batches as needed, and a pause is set between batches. During the upgrade process, each batch needs to wait for the previous batch to be upgraded and verified successfully before upgrading other batches; 2) Multi-threaded asynchronous execution of upgrade tasks: The upgrade process automation of the management and control platform adopts a multi-threaded asynchronous mode. During the upgrade, the management and control platform generates upgrade tasks. Each application node obtains the upgrade task of the application node through regular interaction with the management and control, and actively reports the upgrade result after the upgrade is completed. The management and control platform supports hundreds of application nodes to obtain tasks and task status updates at the same time; 3) The visual interface dynamically updates the upgrade status: During the entire upgrade process, the application node will continuously report the current upgrade status and update it to the management and control platform. The management and control platform can monitor the upgrade progress and status in real time. When the application node is unresponsive for a long time or the returned result is abnormal, it will be dynamically updated on the management and control platform. The upgrade personnel can grasp the upgrade progress in real time, view the abnormal cause of the abnormal application node, and re-issue the upgrade instruction.

[0054] In summary, support personalized customization upgrades: by setting clear upgrade types and operation scopes, ensure that each upgrade can be operated flexibly; support automatic version upgrades: set the personalized customized version to [Push immediately] and [Full Node] upgrade, which can achieve one-click version upgrades, improve upgrade efficiency, and reduce the complexity of manual operations; real-time monitoring and alarm push: real-time monitoring of the upgrade process, timely alarms when problems are found, so that operation and maintenance personnel can quickly take measures to solve the problems; support version batch upgrades: batch system upgrades can be completed by selecting multiple systems, thereby improving upgrade efficiency. By implementing these methods, we can realize the automation of version upgrades, improve upgrade efficiency, reduce operation and maintenance costs and error rates, and ensure the stable operation of the service system.

[0055] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0056] An embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium includes a stored program, wherein when the program is running, the device where the computer-readable storage medium is located is controlled to execute the above-mentioned version automatic upgrade method.

[0057] Specifically, the version automatic upgrade method includes:

[0058] Step S201, receiving an upgrade instruction, the upgrade instruction at least including information about an upgrade type and a version package, the upgrade type including one of the following: a first upgrade type, a second upgrade type, a third upgrade type and a fourth upgrade type, the first upgrade type being a pilot upgrade without immediately pushing the version package, the second upgrade type being a full-node upgrade without immediately pushing the version package, the third upgrade type being a pilot upgrade with an immediate push of the version package, the fourth upgrade type being a full-node upgrade with an immediate push of the version package, wherein the first upgrade type indicates that a target number of the application nodes need to be upgraded and it is not necessary to immediately notify the application nodes to download the version package, the target number being less than the total number of the application nodes, the second upgrade type indicating that all of the application nodes need to be upgraded and it is not necessary to immediately notify the application nodes to download the version package, the third upgrade type indicating that the target number of application nodes need to be upgraded and it is necessary to immediately notify the application nodes to download the version package, and the fourth upgrade type indicating that all of the application nodes need to be upgraded and it is necessary to immediately notify the application nodes to download the version package;

[0059] Step S202, obtaining the corresponding version package according to the information of the version package;

[0060] Step S203: Determine a corresponding upgrade strategy according to the upgrade type, and execute the upgrade strategy so that the application node completes the upgrade according to the version package.

[0061] Optionally, the upgrade type is the first upgrade type. According to the upgrade type, a corresponding upgrade strategy is determined, and the upgrade strategy is executed so that the application node completes the upgrade according to the version package, including: upon receiving an upload instruction, uploading the version package to the distributed file system, wherein the upload instruction is an instruction generated in response to a first predetermined operation acting on the interface of the management and control platform; upon receiving a send instruction, sending a download instruction to the target number of application nodes so that the application node downloads the version package from the distributed file system, wherein the send instruction is an instruction generated in response to a second predetermined operation acting on the interface; upon receiving a download success instruction sent by the application node, sending an operation instruction to the application node so that the application node performs a restart operation or a hot load operation to complete the upgrade, and the download success instruction indicates that the application node has successfully downloaded the version package.

[0062] Optionally, the above-mentioned upgrade type is the above-mentioned third upgrade type. According to the above-mentioned upgrade type, the corresponding upgrade strategy is determined, and the above-mentioned upgrade strategy is executed so that the above-mentioned application node completes the upgrade according to the above-mentioned version package, including: upon receiving an upload instruction, uploading the above-mentioned version package to the distributed file system, wherein the above-mentioned upload instruction is an instruction generated in response to a first predetermined operation acting on the interface of the management and control platform; sending a download instruction to the above-mentioned target number of the above-mentioned application nodes, so that the above-mentioned application nodes download the above-mentioned version package from the above-mentioned distributed file system; upon receiving a download success instruction sent by the above-mentioned application node, sending an operation instruction to the above-mentioned application node, so that the above-mentioned application node performs a restart operation or a hot loading operation to complete the upgrade, and the above-mentioned download success instruction indicates that the above-mentioned application node has successfully downloaded the above-mentioned version package.

[0063] Optionally, the above-mentioned upgrade type is the above-mentioned fourth upgrade type. According to the above-mentioned upgrade type, the corresponding upgrade strategy is determined, and the above-mentioned upgrade strategy is executed so that the above-mentioned application node completes the upgrade according to the above-mentioned version package, including: uploading the above-mentioned version package to the distributed file system; sending a download instruction to all the above-mentioned application nodes, so that the above-mentioned application nodes download the above-mentioned version package from the above-mentioned distributed file system; upon receiving the download success instruction sent by the above-mentioned application node, sending an operation instruction to the above-mentioned application node, so that the above-mentioned application node performs a restart operation or a hot loading operation to complete the upgrade, and the above-mentioned download success instruction indicates that the above-mentioned application node has successfully downloaded the above-mentioned version package.

[0064] Optionally, the upgrade type is the second upgrade type. According to the upgrade type, a corresponding upgrade strategy is determined, and the upgrade strategy is executed so that the application node completes the upgrade according to the version package, including: an upload step, uploading the version package to the distributed file system; a first sending step, upon receiving a sending instruction, sending a download instruction to the target number of application nodes, so that the application node downloads the version package from the distributed file system, wherein the sending instruction is an instruction generated in response to a second predetermined operation acting on the interface of the management and control platform; a second sending step, upon receiving a download success instruction sent by the application node, sending an operation instruction to the application node, so that the application node performs a restart operation or a hot load operation to complete the upgrade, and the download success instruction indicates that the application node has successfully downloaded the version package; a loop step, repeatedly executing the upload step, the first sending step and the second sending step at least once in sequence until all of the application nodes are upgraded.

[0065] Optionally, the above-mentioned distributed file system includes FastDFS. After sending the operation instruction to the above-mentioned application node, the above-mentioned method also includes: receiving an upgrade success instruction sent by the above-mentioned application node to display the upgrade success status on the interface of the management and control platform, wherein the above-mentioned upgrade success instruction indicates that the above-mentioned application node has been successfully upgraded, and the above-mentioned upgrade success status is a status indicating that the above-mentioned application node has been successfully upgraded.

[0066] Optionally, the method further includes: in the case where the download success instruction is not received, receiving a first resend instruction, and resending the download instruction to the application node, wherein the first resend instruction is an instruction generated in response to a third predetermined operation acting on the interface; in the case where the upgrade success instruction is not received, receiving a second resend instruction, and resending the operation instruction to the application node, wherein the second resend instruction is an instruction generated in response to a fourth predetermined operation acting on the interface.

[0067] The present application also provides a computer program product, including computer instructions, which, when executed by a processor, implement at least the following method steps: Step S201, receiving an upgrade instruction, the upgrade instruction at least including information about an upgrade type and a version package, the upgrade type including one of the following: a first upgrade type, a second upgrade type, a third upgrade type, and a fourth upgrade type, the first upgrade type being a pilot upgrade without immediately pushing a version package, the second upgrade type being a full-node upgrade without immediately pushing a version package, the third upgrade type being a pilot upgrade with an immediate push of a version package, the fourth upgrade type being a full-node upgrade with an immediate push of a version package, wherein the first upgrade type indicates that a target number of application nodes need to be upgraded and do not need to be upgraded immediately Notify the above-mentioned application nodes to download the above-mentioned version package, the above-mentioned target number is less than the total number of the above-mentioned application nodes, the above-mentioned second upgrade type indicates that all of the above-mentioned application nodes need to be upgraded and there is no need to immediately notify the above-mentioned application nodes to download the above-mentioned version package, the above-mentioned third upgrade type indicates that the above-mentioned target number of application nodes need to be upgraded and the above-mentioned application nodes need to be immediately notified to download the above-mentioned version package, and the above-mentioned fourth upgrade type indicates that all of the above-mentioned application nodes need to be upgraded and there is a need to immediately notify the above-mentioned application nodes to download the above-mentioned version package; step S202, according to the information of the above-mentioned version package, obtain the corresponding above-mentioned version package; step S203, according to the above-mentioned upgrade type, determine the corresponding upgrade strategy, and execute the above-mentioned upgrade strategy, so that the above-mentioned application nodes complete the upgrade according to the above-mentioned version package.

[0068] Optionally, the upgrade type is the first upgrade type. According to the upgrade type, a corresponding upgrade strategy is determined, and the upgrade strategy is executed so that the application node completes the upgrade according to the version package, including: upon receiving an upload instruction, uploading the version package to the distributed file system, wherein the upload instruction is an instruction generated in response to a first predetermined operation acting on the interface of the management and control platform; upon receiving a send instruction, sending a download instruction to the target number of application nodes so that the application node downloads the version package from the distributed file system, wherein the send instruction is an instruction generated in response to a second predetermined operation acting on the interface; upon receiving a download success instruction sent by the application node, sending an operation instruction to the application node so that the application node performs a restart operation or a hot load operation to complete the upgrade, and the download success instruction indicates that the application node has successfully downloaded the version package.

[0069] Optionally, the above-mentioned upgrade type is the above-mentioned third upgrade type. According to the above-mentioned upgrade type, the corresponding upgrade strategy is determined, and the above-mentioned upgrade strategy is executed so that the above-mentioned application node completes the upgrade according to the above-mentioned version package, including: upon receiving an upload instruction, uploading the above-mentioned version package to the distributed file system, wherein the above-mentioned upload instruction is an instruction generated in response to a first predetermined operation acting on the interface of the management and control platform; sending a download instruction to the above-mentioned target number of the above-mentioned application nodes, so that the above-mentioned application nodes download the above-mentioned version package from the above-mentioned distributed file system; upon receiving a download success instruction sent by the above-mentioned application node, sending an operation instruction to the above-mentioned application node, so that the above-mentioned application node performs a restart operation or a hot loading operation to complete the upgrade, and the above-mentioned download success instruction indicates that the above-mentioned application node has successfully downloaded the above-mentioned version package.

[0070] Optionally, the above-mentioned upgrade type is the above-mentioned fourth upgrade type. According to the above-mentioned upgrade type, the corresponding upgrade strategy is determined, and the above-mentioned upgrade strategy is executed so that the above-mentioned application node completes the upgrade according to the above-mentioned version package, including: uploading the above-mentioned version package to the distributed file system; sending a download instruction to all the above-mentioned application nodes, so that the above-mentioned application nodes download the above-mentioned version package from the above-mentioned distributed file system; upon receiving the download success instruction sent by the above-mentioned application node, sending an operation instruction to the above-mentioned application node, so that the above-mentioned application node performs a restart operation or a hot loading operation to complete the upgrade, and the above-mentioned download success instruction indicates that the above-mentioned application node has successfully downloaded the above-mentioned version package.

[0071] Optionally, the upgrade type is the second upgrade type. According to the upgrade type, a corresponding upgrade strategy is determined, and the upgrade strategy is executed so that the application node completes the upgrade according to the version package, including: an upload step, uploading the version package to the distributed file system; a first sending step, upon receiving a sending instruction, sending a download instruction to the target number of application nodes, so that the application node downloads the version package from the distributed file system, wherein the sending instruction is an instruction generated in response to a second predetermined operation acting on the interface of the management and control platform; a second sending step, upon receiving a download success instruction sent by the application node, sending an operation instruction to the application node, so that the application node performs a restart operation or a hot load operation to complete the upgrade, and the download success instruction indicates that the application node has successfully downloaded the version package; a loop step, repeatedly executing the upload step, the first sending step and the second sending step at least once in sequence until all of the application nodes are upgraded.

[0072] Optionally, the above-mentioned distributed file system includes FastDFS. After sending the operation instruction to the above-mentioned application node, the above-mentioned method also includes: receiving an upgrade success instruction sent by the above-mentioned application node to display the upgrade success status on the interface of the management and control platform, wherein the above-mentioned upgrade success instruction indicates that the above-mentioned application node has been successfully upgraded, and the above-mentioned upgrade success status is a status indicating that the above-mentioned application node has been successfully upgraded.

[0073] Optionally, the method further includes: in the case where the download success instruction is not received, receiving a first resend instruction, and resending the download instruction to the application node, wherein the first resend instruction is an instruction generated in response to a third predetermined operation acting on the interface; in the case where the upgrade success instruction is not received, receiving a second resend instruction, and resending the operation instruction to the application node, wherein the second resend instruction is an instruction generated in response to a fourth predetermined operation acting on the interface.

[0074] An embodiment of the present application also provides an electronic device, comprising: one or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include methods for executing any one of the above-mentioned automatic version upgrade methods.

[0075] Obviously, those skilled in the art should understand that the above modules or steps of the present invention can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order than here, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0076] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0077] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0078] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0079] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0080] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0081] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0082] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0083] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0084] From the above description, it can be seen that the above embodiments of the present application achieve the following technical effects:

[0085] In the version automatic upgrade method of the present application, there are multiple application nodes, which first receive an upgrade instruction including information about the upgrade type and the version package, then obtain the corresponding version package according to the information of the version package, and then determine the corresponding upgrade strategy according to the upgrade type, and finally execute the upgrade strategy so that the application node completes the upgrade according to the version package, wherein the upgrade type includes one of a first upgrade type, a second upgrade type, a third upgrade type and a fourth upgrade type, the first upgrade type is a pilot upgrade without immediately pushing the version package, the second upgrade type is a full-node upgrade without immediately pushing the version package, the third upgrade type is a pilot upgrade with an immediate push of the version package, and the fourth upgrade type is a full-node upgrade with an immediate push of the version package. Compared with the problem of high error rate and low upgrade efficiency in the distributed system in the prior art due to the involvement of numerous nodes, the present application can automatically obtain the corresponding version package and determine the upgrade strategy according to the upgrade type by receiving upgrade instructions including upgrade type and version package information. This means that the upgrade process does not require human intervention, reduces human errors, and improves the efficiency and reliability of the upgrade. In addition, four different upgrade types are provided to adapt to different upgrade needs and scenarios, and personalized customized upgrades are supported. By setting clear upgrade types and corresponding clear upgrade strategies, upgrades can be performed according to the specific circumstances of each node, reducing uncertainty in the upgrade process.

[0086] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A version automatic upgrade method, characterized in that: There are multiple application nodes, and the method includes: Receive an upgrade instruction, the upgrade instruction at least including information about an upgrade type and a version package, the upgrade type including one of the following: a first upgrade type, a second upgrade type, a third upgrade type, and a fourth upgrade type, the first upgrade type being a pilot upgrade without immediately pushing the version package, the second upgrade type being a full-node upgrade without immediately pushing the version package, the third upgrade type being a pilot upgrade with an immediate version package push, and the fourth upgrade type being a full-node upgrade with an immediate version package push, wherein the first upgrade type indicates that a target number of application nodes need to be upgraded and it is not necessary to immediately notify the application nodes to download the version package, and the target number is less than the total number of application nodes, the second upgrade type indicates that all of the application nodes need to be upgraded and it is not necessary to immediately notify the application nodes to download the version package, the third upgrade type indicates that the target number of application nodes need to be upgraded and it is necessary to immediately notify the application nodes to download the version package, and the fourth upgrade type indicates that all of the application nodes need to be upgraded and it is necessary to immediately notify the application nodes to download the version package; According to the information of the version package, obtain the corresponding version package; According to the upgrade type, a corresponding upgrade strategy is determined, and the upgrade strategy is executed so that the application node completes the upgrade according to the version package.

2. The method for automatic version upgrade according to claim 1, characterized in that: The upgrade type is the first upgrade type, and according to the upgrade type, a corresponding upgrade strategy is determined, and the upgrade strategy is executed so that the application node completes the upgrade according to the version package, including: In the case of receiving an upload instruction, uploading the version package to a distributed file system, wherein the upload instruction is an instruction generated in response to a first predetermined operation acting on an interface of the management and control platform; In the case of receiving a sending instruction, sending a download instruction to the target number of application nodes so that the application nodes download the version package from the distributed file system, wherein the sending instruction is an instruction generated in response to a second predetermined operation acting on the interface; When receiving a download success instruction sent by the application node, an operation instruction is sent to the application node so that the application node performs a restart operation or a hot load operation to complete the upgrade. The download success instruction indicates that the application node has successfully downloaded the version package.

3. The method for automatic version upgrade according to claim 1, characterized in that: The upgrade type is the third upgrade type, and according to the upgrade type, a corresponding upgrade strategy is determined, and the upgrade strategy is executed so that the application node completes the upgrade according to the version package, including: In the case of receiving an upload instruction, uploading the version package to a distributed file system, wherein the upload instruction is an instruction generated in response to a first predetermined operation acting on an interface of the management and control platform; Sending a download instruction to the target number of application nodes, so that the application nodes download the version package from the distributed file system; When receiving a download success instruction sent by the application node, an operation instruction is sent to the application node so that the application node performs a restart operation or a hot load operation to complete the upgrade. The download success instruction indicates that the application node has successfully downloaded the version package.

4. The method for automatic version upgrade according to claim 1, characterized in that: The upgrade type is the fourth upgrade type, and according to the upgrade type, a corresponding upgrade strategy is determined, and the upgrade strategy is executed so that the application node completes the upgrade according to the version package, including: Uploading the version package to a distributed file system; Sending a download instruction to all the application nodes, so that the application nodes download the version package from the distributed file system; When receiving a download success instruction sent by the application node, an operation instruction is sent to the application node so that the application node performs a restart operation or a hot load operation to complete the upgrade. The download success instruction indicates that the application node has successfully downloaded the version package.

5. The method for automatic version upgrade according to claim 1, characterized in that: The upgrade type is the second upgrade type, and according to the upgrade type, a corresponding upgrade strategy is determined, and the upgrade strategy is executed so that the application node completes the upgrade according to the version package, including: An uploading step, uploading the version package to a distributed file system; A first sending step, in the case of receiving a sending instruction, sending a download instruction to the target number of application nodes, so that the application nodes download the version package from the distributed file system, wherein the sending instruction is an instruction generated in response to a second predetermined operation acting on the interface of the management and control platform; A second sending step, in the case of receiving a download success instruction sent by the application node, sending an operation instruction to the application node, so that the application node performs a restart operation or a hot load operation to complete the upgrade, wherein the download success instruction indicates that the application node has successfully downloaded the version package; A loop step is to repeat the uploading step, the first sending step and the second sending step in sequence at least once until all the application nodes have completed the upgrade.

6. The method for automatic version upgrade according to any one of claims 2 to 5, characterized in that: The distributed file system includes FastDFS. After sending the operation instruction to the application node, the method further includes: An upgrade success instruction sent by the application node is received to display an upgrade success status on the interface of the management and control platform, wherein the upgrade success instruction indicates that the application node has been successfully upgraded, and the upgrade success status is a status indicating that the application node has been successfully upgraded.

7. The method for automatic version upgrade according to claim 6, characterized in that: The method further comprises: In the case where the download success instruction is not received, receiving a first resending instruction, and resending the download instruction to the application node, wherein the first resending instruction is an instruction generated in response to a third predetermined operation acting on the interface; In the case where the upgrade success instruction is not received, a second resending instruction is received, and the operation instruction is resent to the application node, wherein the second resending instruction is an instruction generated in response to a fourth predetermined operation acting on the interface.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein when the program is executed, the device where the computer-readable storage medium is located is controlled to execute the automatic version upgrade method according to any one of claims 1 to 7.

9. A computer program product comprising computer instructions, characterized in that When the computer instructions are executed by the processor, the version automatic upgrade method described in any one of claims 1 to 7 is implemented.

10. An electronic device, characterized in that: include: One or more processors, a memory, and one or more programs, wherein the one or more programs are stored in the memory and are configured to be executed by the one or more processors, and the one or more programs include a method for executing the automatic version upgrade method described in any one of claims 1 to 7.

Images