Application version upgrading method of cluster node, electronic equipment and readable storage medium

Abstract

The invention discloses an application version upgrading method of cluster nodes, electronic equipment and a readable storage medium. The method comprises the following steps: blocking distribution equipment of a first cluster node; switching a first customer service group of the first cluster node to a call and information system (CIS) of a second cluster node; and upgrading the application version of the first cluster node under the condition that the access user number of the first cluster node is smaller than a first threshold value and the login number of the seat is smaller than a second threshold value.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of computer technology, and in particular to a method for upgrading an application version of a cluster node, an electronic device, and a readable storage medium. Background Art

[0002] Grayscale release refers to a release method that smoothly transitions unreleased functions to released functions. Both the old and new versions of the application are deployed in the production environment at the same time, allowing some non-grayscale users to continue using the old version of the application in the non-grayscale environment, while the other grayscale users use the new version of the application in the grayscale environment for grayscale testing. If the grayscale users have no negative feedback during the test, all users will be gradually migrated to the new version. If it does not meet expectations, the grayscale will be canceled and the grayscale traffic will be redirected back to the old product. This release method can effectively avoid the risks that may arise in product releases and effectively ensure the accuracy of product releases. Therefore, grayscale release is currently a common method used by companies to implement releases in production environments.

[0003] In the related art, when upgrading an old version of an application in a grayscale environment, business losses will occur. Specifically, when upgrading an old version of an application in a grayscale environment, the service of the server in the grayscale environment is directly stopped, which will cause the business being processed on the server to be interrupted. Although the upgrade is done when the business is not busy, it will still have a significant impact on the online system, causing business losses. Summary of the invention

[0004] The embodiments of the present application provide a method for upgrading an application version of a cluster node, an electronic device, and a readable storage medium, which can solve the problem of business loss when upgrading an old version of an application.

[0005] In order to solve the above technical problems, this application is implemented as follows:

[0006] In a first aspect, a method for upgrading an application version of a cluster node is provided, the method comprising: blocking a distribution device of a first cluster node; switching a first customer service group of the first cluster node to a call and information system CIS of a second cluster node; and upgrading the application version of the first cluster node when the number of access users of the first cluster node is less than a first threshold and the number of logins of agents is less than a second threshold.

[0007] In a second aspect, an electronic device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the cluster node application version upgrade method as described in the first aspect are implemented.

[0008] In a third aspect, a readable storage medium is provided, characterized in that a program or instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the method for upgrading the application version of the cluster node as described in the first aspect are implemented.

[0009] The technical solution provided by this application may have the following beneficial effects:

[0010] In an embodiment of the present application, by blocking the distribution device of the first cluster node, the first customer service group of the first cluster node is switched to the call and information system CIS of the second cluster node, so that subsequent services will not be allocated to the first cluster node, and then when the number of access users of the first cluster node is less than a first threshold and the number of logins of the agents is less than a second threshold, the application version of the first cluster node is upgraded, thereby achieving an upgrade of the application version of the first cluster node without affecting the currently ongoing services of the first cluster node, and enabling lossless services when upgrading the old version of the application. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0012] Figure 1 A schematic diagram of a process for upgrading an application version of a cluster node provided by an exemplary embodiment of the present application is shown;

[0013] Figure 2 A schematic diagram showing a flow chart of another method for upgrading an application version of a cluster node provided by an exemplary embodiment of the present application;

[0014] Figure 3 A schematic diagram of the structure of a cloud system provided by an exemplary embodiment of the present application is shown;

[0015] Figure 4 A schematic diagram showing a flow chart of another method for upgrading an application version of a cluster node provided by an exemplary embodiment of the present application;

[0016] Figure 5 A schematic structural diagram of an electronic device provided by an exemplary embodiment of the present application is shown. DETAILED DESCRIPTION

[0017] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0018] Figure 1 A schematic diagram showing a process flow of a cluster node application version upgrade method provided by an exemplary embodiment of the present application is shown. Figure 1 , the method comprises the following steps:

[0019] Step 102: Blocking the distribution device of the first cluster node;

[0020] Among them, after the distribution device of the first cluster node is blocked, the distribution device can be determined to be blocked by heartbeat detection, and a selection message is sent to the distribution device of the first cluster node. The distribution device does not respond, thereby confirming that the distribution device is abnormal and subsequent services will not be allocated to the distribution device.

[0021] Step 104: Switching the first customer service group of the first cluster node to the call and information system (CIS) of the second cluster node;

[0022] Among them, after the distribution device of the first cluster node is blocked and the first customer service group of the first cluster node is switched to the CIS of the second cluster node, subsequent services will not be allocated to the distribution device of the first cluster node, but to the distribution device of the second cluster node. New incoming users will not enter the first cluster node, and new agents will not log in to the first cluster node. New agents will directly log in to the second cluster node, so as not to affect subsequent services.

[0023] Step 106: When the number of access users of the first cluster node is less than a first threshold and the number of login seats is less than a second threshold, the application version of the first cluster node is upgraded.

[0024] The number of users accessing the first cluster node being less than the first threshold may include that no user is currently on a call, or that a user is currently on a call but the call can be ignored. The number of agents logged in being less than the second threshold may include that no agent is currently logged in, or that currently logged in agents can be ignored.

[0025] In an embodiment of the present application, before upgrading the application version of the second cluster node, the distribution device of the first cluster node is first blocked so that subsequent services will not be allocated to the first cluster node, and the first customer service group of the first cluster node is switched to the CIS of the second cluster node so that subsequent services are allocated to the second cluster node and subsequent services can be performed normally. Then, for the users currently connected to the first cluster node and the seats that have logged in, the number of users currently connected to the first cluster node and the number of seats logged in are detected to determine the number of users currently connected and the number of seats logged in. When it is detected that the number of users connected to the first cluster node is less than the first threshold and the number of seats logged in is less than the second threshold, it can be determined that the service of the first cluster node at this time has been completed, or part of the service will not be affected, for example, no user is talking or the current call can be ignored, and no seat is logged in or the currently logged in seat can be ignored, then the application version of the first cluster node can be upgraded, so that the application version of the first cluster node is upgraded without affecting the current service of the first cluster node, so that the service can be achieved without loss when upgrading the old version of the application.

[0026] In one implementation, the above step 104 may include: sending a synchronization file and a switching message to the second cluster node, wherein the synchronization file includes information of the first customer service group, and the switching message is used to indicate switching the first customer service group to the second cluster node.

[0027] In an embodiment of the present application, the switching of the first customer service group of the first cluster node can be achieved by sending a synchronization file and a switching message to the second cluster node. According to the switching message, it can be known that the first customer service group needs to be switched to the second cluster node, and then the switching of the first customer service group is achieved according to the synchronization file.

[0028] In one implementation, after the above step 104, the above method may further include: sending a first re-login notification message to the logged-in agents in the first customer service group, where the first re-login notification message is used to notify the agents to re-login to the second cluster node.

[0029] In an embodiment of the present application, after the first customer service group of the first cluster node is switched to the second cluster node, a first re-login notification message is sent to the logged-in seats in the first customer service group, and the logged-in seats are enabled to log in again through the first re-login notification message. Because the first customer service group has been switched to the second cluster node, the seats that had previously logged in to the first cluster node now log in again to the second cluster node, so that the logged-in seats in the first cluster node log in again to the second cluster node, thereby being able to continue normal execution.

[0030] Figure 2A flowchart showing another method for upgrading an application version of a cluster node provided by an exemplary embodiment of the present application in one implementation manner is shown. Figure 2 , the method comprises the following steps:

[0031] Step 202: Block the distribution device of the first cluster node.

[0032] Step 204: Switch the first customer service group of the first cluster node to the CIS of the second cluster node.

[0033] Step 206: When the number of access users of the first cluster node is less than the first threshold and the number of login seats is less than the second threshold, the application version of the first cluster node is upgraded.

[0034] Steps 202 to 206 are the same as the above-mentioned steps 102 to 106 , and the specific descriptions may refer to the above-mentioned steps 102 to 106 .

[0035] Step 208: Switch the test customer service group of the second cluster node to the upgraded CIS of the first cluster node.

[0036] The customer service group of the second cluster node is used as a test customer service group and switched to the CIS of the first cluster node, so that the logged-in agents of the test customer service group can log in to the first cluster node to verify the business services of the first cluster node.

[0037] Step 210: Verify the business service of the first cluster node by testing the test customer service group.

[0038] In the embodiment of the present application, after the application version of the first cluster node is upgraded, it is necessary to verify the upgraded first cluster node to determine whether there is a problem with the application version upgrade of the first cluster node. By switching the test customer service group of the second cluster node to the CIS of the first cluster node, the agents logged in by the test customer service group are logged in to the first cluster node, and the test customer service group is tested at the first cluster node to verify whether there is a problem when the test customer service group performs business services at the first cluster node, thereby determining whether there is a problem with the application version upgrade of the first cluster node.

[0039] In one implementation, after the above step 210, the above method further includes: if the verification fails, canceling the application version upgrade of the first cluster node.

[0040] In an embodiment of the present application, after verifying the business service of the first cluster node, if the verification fails and it is determined that there is a problem with the upgraded application version of the first cluster node, the application version upgrade of the first cluster node is canceled, so that the application version of the first cluster node is rolled back to the version before the upgrade.

[0041] In one implementation, the above-mentioned revoking the application version upgrade of the first cluster node may include the following steps:

[0042] Step 211: Roll back the application version of the first cluster node to the version before the upgrade;

[0043] Step 212: Unblock the distribution device of the first cluster node, so that subsequent services can continue to be executed on the first cluster node.

[0044] Step 213: Switch the first customer service group back to the CIS of the first cluster node; switch the first customer service group from the CIS of the second cluster node back to the CIS of the first cluster node.

[0045] Step 214: Send a second re-login notification message to the logged-in agents in the first customer service group, where the second re-login notification message is used to notify the logged-in agents to re-login to the first cluster node.

[0046] In an embodiment of the present application, if the verification fails, the upgrade of the application version of the first cluster node is revoked. The application version of the first cluster node can be rolled back to the version before the upgrade, so that the distribution device of the first cluster node is unblocked, so that subsequent business can continue to be executed on the first cluster node, and then the first customer service group is switched from the second cluster node back to the CIS of the first cluster node, and a second re-login notification message is sent to the logged-in seats in the first customer service group, so that the seats logged in to the second cluster node re-login to the first cluster node, so that the first cluster node can continue to process business normally.

[0047] In an implementation, after the above step 210, the above method further includes: if the verification is successful, unblocking the distribution device of the first cluster node.

[0048] In an embodiment of the present application, after verifying the business service of the first cluster node after the application version is upgraded, if the verification passes and it is determined that there is no problem with the application version of the upgraded first cluster node, the blocking of the distribution device of the first cluster node is unblocked, so that the first cluster node after the application version is upgraded can perform business processing and complete the upgrade of the application version of the first cluster node.

[0049] In one implementation, after the above step 210, the above method further includes the following steps:

[0050] Step 220: If the verification is successful, the distribution device of the second cluster node is blocked;

[0051] Step 221: Switch the second customer service group of the second cluster node to the CIS of the first cluster node;

[0052] Step 222: When the number of access users of the second cluster node is less than the first threshold and the number of login seats is less than the second threshold, the application version of the second cluster node is upgraded.

[0053] In an embodiment of the present application, after verifying the business service of the first cluster node after the application version is upgraded, if the verification passes, it is determined that there is no problem with the application version of the upgraded first cluster node. After completing the upgrade of the application version of the first cluster node, the application version of the second cluster node is upgraded. The upgrade method is the same as the application version upgrade method of the first cluster node. First, the distribution device of the second cluster node is blocked so that subsequent business will not be allocated to the second cluster node. Then, the second customer service group of the second cluster node is switched to the CIS of the first cluster node, so that subsequent business is allocated to the first cluster node and can be executed normally. After that, the number of access users and the number of logged-in seats of the second cluster node are also detected in real time to determine the number of currently accessed users and the number of logged-in seats. When the number of access users of the second cluster node is less than the first threshold and the number of logged-in seats is less than the second threshold, it is determined that no business is ongoing at the second cluster node or some business will not be affected. For example, no user is calling or the current call can be ignored, and no seat is logged in or the currently logged-in seat can be ignored. In this way, the application version of the second cluster node can be upgraded, thereby achieving the upgrade of the application version of the second cluster node while ensuring that the business is intact.

[0054] Optionally, the second customer service group of the second cluster node is switched to the CIS of the first cluster node by sending the synchronization file of the second cluster node and the switching message of switching the second customer service group to the first cluster node to the first cluster node, so as to switch the second customer service group to the CIS of the first cluster node.

[0055] Optionally, after switching the second customer service group of the second cluster node to the CIS of the first cluster node, a re-login notification message can be sent to the logged-in agents in the second customer service group to notify the agents to re-login to the first cluster node and perform business normally in the first cluster node.

[0056] Optionally, the test customer service group of the first cluster node is switched to the CIS of the upgraded second cluster node, and the business services of the second cluster node are verified by testing the test customer service group. If the verification passes, it is determined that there is no problem with the application version upgrade of the second cluster node, and the distribution device of the second cluster node after the application version upgrade is unblocked, so that the second cluster node after the application version upgrade can execute business normally. If the verification fails, it is determined that there is a problem with the application version upgrade of the second cluster node, then the same steps as steps 211 to 214 above are executed to process the second cluster node with the problem with the application version upgrade, so that the second cluster node that has not been successfully upgraded can also continue to execute business normally.

[0057] It should be noted that the application version upgrade method of the cluster node provided in the embodiment of the present application is not limited to being implemented between two cluster nodes, but can also be implemented between multiple cluster nodes. The specific implementation steps can be found in the above embodiments.

[0058] Figure 3 A schematic diagram of the structure of a cloud system provided by an exemplary embodiment of the present application is shown in FIG. Figure 3 The system 300 includes: a soft switch (SS) module 31, a session initiation protocol (SIP) proxy module 32, an interactive voice response (IVR) module 33, a call and information systems (CIS) module 34, a computer telephony integration (CTI) module 35, a database (DB) 36 and an agent center 37.

[0059] Among them, the SS module 31 is responsible for SIP docking with the outside; the SIP proxy module 32 forwards SIP messages of the User Datagram Protocol (UDP) message type, completes the SIP message distribution from SS, media server to other devices according to the corresponding distribution strategy and the status of the target server, and sends the message to the target server for processing; the IVR module 33 completes the message control of automatic services, and distributes the messages to the corresponding CIS module 34 in sequence; the CIS module mainly provides routing queuing and data processing functions, and the customer service group exists in this module; the CTI module 35 is used to control and call seats; DB 36 is used to store the relevant configuration of the entire system and the corresponding log data records during the operation process; the seat center 37 is a collection of seats.

[0060] Figure 4 A flow chart of another method for upgrading the application version of a cluster node provided by an exemplary embodiment of the present application is shown. The method can be applied to each module in the above-mentioned cloud system to upgrade site 1 and site 2. Figure 4 , the method comprises the following steps:

[0061] Step 401, blocking the SIP proxy of site 1.

[0062] After the SIP proxy device is blocked, the SIP proxy will not reply with confirmation when SS sends an option message to the SIP proxy device. SS then considers that the SIP proxy device is abnormal and will not distribute subsequent invite messages to the SIP proxy device. In other words, the SIP proxy of site 2 to which the newly incoming user is distributed realizes service blocking through heartbeat detection.

[0063] Step 402: Switch the virtual center of site 1 to the CIS of site 2.

[0064] After blocking the SIP proxy of site 1, although new incoming users will not enter site 1, the agents who previously belonged to site 1 can still log in to site 1. In order to achieve the purpose of grayscale release, that is, no new agents will log in to site 1 in the future, the virtual center of site 1 will be switched to site 2, so that the newly logged-in agents will directly log in to the CTI of site 2. The essence of switching the virtual center is to generate a virtual center synchronization file and a virtual center switching message, send them to the corresponding device, and send messages such as agent status information to CIS through CTI to restore the relevant data of agent information.

[0065] Step 403: Send an agent notification to the logged-in agents of the virtual center of site 1.

[0066] By sending the agent notification information, the newly logged-in agent logs in to site 2. However, the agent who was previously on a call at site 1 is still logged in to the CTI of site 1. Therefore, a re-login notification is sent to the agent who is still logged in to the virtual center of site 1. After re-login, the agent logs in to the CTI of site 2, thus realizing the function of delayed service exit.

[0067] Step 404: Detect the number of users accessing site 1 and the number of agents logging in.

[0068] The number of connected users and the number of logged-in agents are detected in real time through scripts. When there is no user call or the current call is considered to be negligible, and no agent is logged in or the currently logged-in agent is considered to be negligible, the application version of site 1 is automatically upgraded.

[0069] Step 405, upgrading site 1; upgrading the application version of site 1 using an automated upgrade process.

[0070] Step 406: Switch the test virtual center from site 2 to the CIS of site 1.

[0071] Among them, the test virtual center is switched to the CIS of site 1, and the seat to which it belongs can log in to the CTI of site 1.

[0072] Step 407, verify whether there is any problem with the upgrade of site 1. Verify the service by testing the virtual center. If the verification finds that there is a problem with the upgrade, execute steps 408 to 410; if the verification finds that there is no problem with the upgrade, execute steps 411 to 419.

[0073] Step 408, site 1 rolls back.

[0074] If the upgrade is verified to have problems, an automatic rollback is performed to roll back the application version 1 to the version between the upgrades.

[0075] Step 409, unblocking the SIP proxy of site 1.

[0076] After the equipment of site 1 is rolled back, the service of site 1 needs to be restored, so the SIP proxy device of site 1 is unblocked. After the SIP proxy device is unblocked, SS sends an option message to the SIP proxy device, and the SIP proxy will reply with a confirmation. SS then considers that the SIP proxy device is normal and distributes subsequent invite messages to the SIP proxy device, that is, new incoming users will be distributed to the SIP proxy of site 1.

[0077] Step 410: Switch the virtual center of site 1 back to the CIS of site 1 from site 2, and send an agent notification to the logged-in agents of the virtual center of site 1.

[0078] After unblocking the SIP proxy device of site 1, it is necessary to switch back the previous virtual center of site 1 and send a re-login notification to the previous seat so that site 1 can handle business normally.

[0079] Step 411, unblock the SIP proxy of site 1 and block the SIP proxy of site 2.

[0080] After the upgrade verification of site 1 is completed, the same method needs to be used to upgrade the application version of site 2. Unblock the SIP proxy of site 1 and block the SIP proxy of site 2 so that new incoming users are distributed to site 1.

[0081] Step 412: Switch the virtual centers of site 1 and site 2 to the CIS of site 1.

[0082] Switch all virtual centers to site 1 so that all subsequent agents can log in to site 1.

[0083] Step 413: Send an agent notification to all logged-in agents.

[0084] All agents of the virtual center of site 1 and the virtual center of site 2 on site 2 receive the re-login notification. After the agents re-login, they log in to the CTI of site 1, thereby smoothly switching the service to site 1.

[0085] Step 414: Detect the number of users accessing site 2 and the number of agents logging in.

[0086] After notifying the agent to log in again, you need to wait for the agent to log in again. The number of connected users and the number of agent logins are detected in real time through the script. When there is no user call or the current call is considered to be negligible, no agent is logged in or the currently logged in agent is considered to be negligible, the application version of site 2 is automatically upgraded.

[0087] Step 415, upgrading site 2; upgrading the application version of site 2 using an automated upgrade process.

[0088] Step 416: Switch the test virtual center of site 1 to the CIS of site 2.

[0089] When the server of site 2 is upgraded, the virtual centers of site 1 and site 2 are both on the CIS of site 1. At this time, it is necessary to verify the upgraded application version of site 2, and the test virtual center of site 2 needs to be switched from the CIS of site 1 back to the CIS of site 2.

[0090] Step 417, verify the upgrade of site 2; verify the service by testing the virtual center.

[0091] Step 418, unblock the SIP proxy of site 2.

[0092] After unblocking the SIP proxy device at site 2, SS sends an option message to the SIP proxy device. The SIP proxy will reply with a confirmation. SS then believes that the SIP proxy device is normal and will distribute subsequent invite messages to the SIP proxy device, so that new incoming users will be distributed to the SIP proxy at site 2.

[0093] Step 419 , the virtual center of site 2 is switched from site 1 back to the CIS of site 2 and an agent notification is sent to the agents who have logged in to the virtual center of site 2 .

[0094] After unblocking the SIP proxy device of site 2, it is necessary to switch back the previous virtual center of site 2 and send a re-login notification to the previous agent. After the agent re-logins, site 2 can handle business normally.

[0095] Optionally, blocking the SIP proxy device of the site can also be achieved in the following ways:

[0096] (1) Modify the configuration file of the site's SIP proxy device;

[0097] (2) Modify the load balancing configuration of the site's SIP proxy device;

[0098] (3) Set up a firewall to prohibit the site's SIP proxy device from communicating with the SS;

[0099] (4) The network route of the SIP proxy device at the configured site is not in the reachable IP address list of the SS.

[0100] The method of the embodiment of the present application can upgrade the application version of the site while ensuring that the service is intact.

[0101] Figure 5 A schematic diagram of the structure of an electronic device provided by an exemplary embodiment of the present application is shown, wherein the electronic device is used to execute the above-mentioned cluster node application version upgrade method. Figure 5 A schematic diagram of the structure of an electronic device for implementing various embodiments of the present application. The electronic device may have relatively large differences due to different configurations or performances, and may include a processor (processor) 501, a communication interface (Communications Interface) 502, a memory (memory) 503 and a communication bus 504, wherein the processor 501, the communication interface 502, and the memory 503 communicate with each other through the communication bus 504. The processor 501 may call a computer program stored in the memory 503 and executable on the processor 501 to perform the following steps:

[0102] Block the distribution device of the first cluster node; switch the first customer service group of the first cluster node to the call and information system CIS of the second cluster node; upgrade the application version of the first cluster node when the number of access users of the first cluster node is less than the first threshold and the number of logins of the agents is less than the second threshold.

[0103] The specific execution steps can refer to the various steps of the above-mentioned cluster node application version upgrade method embodiment, and can achieve the same technical effect. To avoid repetition, they will not be repeated here.

[0104] It should be noted that the electronic devices in the embodiments of the present application include: servers, terminals, or other devices except terminals.

[0105] The above electronic device structure does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. For example, the input unit may include a graphics processing unit (GPU) and a microphone, and the display unit may be configured with a display panel in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit includes a touch panel and at least one of other input devices. The touch panel is also called a touch screen. Other input devices may include, but are not limited to, a physical keyboard, function keys (such as volume control buttons, switch buttons, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0106] The memory can be used to store software programs and various data. The memory may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory may include a volatile memory or a non-volatile memory, or the memory may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM) and direct memory bus random access memory (DRRAM).

[0107] The processor may include one or more processing units; optionally, the processor integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to the operating system, user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor.

[0108] In an exemplary embodiment, a readable storage medium is also provided, in which at least one computer program is stored, and the computer program is loaded and executed by a processor to implement all or part of the steps in the above-mentioned cluster node application version upgrade method. For example, the readable storage medium can be a read-only memory (ROM), a random access memory (RAM), a compact disc read-only memory (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, etc.

[0109] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any modification, use or adaptation of the present application, which follows the general principles of the present application and includes common knowledge or customary techniques in the art that are not disclosed in the present application. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present application are indicated by the claims.

[0110] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A method for upgrading an application version of a cluster node, characterized in that: include: Blocking a distribution device of the first cluster node; Switching the first customer service group of the first cluster node to the call and information system CIS of the second cluster node; When the number of access users of the first cluster node is less than a first threshold and the number of login seats is less than a second threshold, the application version of the first cluster node is upgraded.

2. The method according to claim 1, characterized in that The switching of the first customer service group of the first cluster node to the call and information system CIS of the second cluster node includes: A synchronization file and a switching message are sent to the second cluster node, wherein the synchronization file includes information of the first customer service group, and the switching message is used to instruct to switch the first customer service group to the second cluster node.

3. The method according to claim 1, characterized in that After switching the first customer service group of the first cluster node to a call and information system CIS of the second cluster node, the method further includes: A first re-login notification message is sent to a logged-in agent in the first customer service group, where the first re-login notification message is used to notify the agent to re-login to the second cluster node.

4. The method according to any one of claims 1 to 3, characterized in that: After the application version of the first cluster node is upgraded, the method further includes: Switching the test customer service group of the second cluster node to the upgraded CIS of the first cluster node; By testing the test customer service group, the business service of the first cluster node is verified.

5. The method according to claim 4, characterized in that After verifying the business service of the first cluster node by testing the test customer service group, the method further includes: If the verification fails, the application version upgrade of the first cluster node is canceled.

6. The method according to claim 5, characterized in that The cancelling the application version upgrade of the first cluster node includes: Rolling back the application version of the first cluster node to the version before the upgrade; Unblocking a distribution device of the first cluster node; Switching the first customer service group back to the CIS of the first cluster node; A second re-login notification message is sent to the logged-in agent in the first customer service group, where the second re-login notification message is used to notify the logged-in agent to re-login to the first cluster node.

7. The method according to claim 4, characterized in that After verifying the business service of the first cluster node by testing the test customer service group, the method further includes: If the verification is successful, the distribution device of the first cluster node is unblocked.

8. The method according to claim 7, characterized in that The method further comprises: If the verification is successful, blocking the distribution device of the second cluster node; Switching the second customer service group of the second cluster node to the CIS of the first cluster node; When the number of access users of the second cluster node is less than a first threshold and the number of login seats is less than a second threshold, the application version of the second cluster node is upgraded.

9. An electronic device, characterized in that: The electronic device includes a processor and a memory, the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method for upgrading the application version of the cluster node as described in any one of claims 1 to 8 are implemented.

10. A readable storage medium, characterized in that: The readable storage medium stores a program or an instruction, and when the program or the instruction is executed by the processor, the steps of the method for upgrading the application version of the cluster node according to any one of claims 1 to 8 are implemented.

Images