CN116860394A - Batch restarting method, equipment and storage medium of CKE nodes - Google Patents
Batch restarting method, equipment and storage medium of CKE nodes Download PDFInfo
- Publication number
- CN116860394A CN116860394A CN202310834147.XA CN202310834147A CN116860394A CN 116860394 A CN116860394 A CN 116860394A CN 202310834147 A CN202310834147 A CN 202310834147A CN 116860394 A CN116860394 A CN 116860394A
- Authority
- CN
- China
- Prior art keywords
- nodes
- cke
- node
- batch
- application interface
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 48
- 230000002159 abnormal effect Effects 0.000 claims description 34
- 238000012545 processing Methods 0.000 claims description 8
- 238000004891 communication Methods 0.000 claims description 6
- 230000004044 response Effects 0.000 claims description 3
- 238000004519 manufacturing process Methods 0.000 abstract description 6
- 238000012423 maintenance Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 4
- 238000011084 recovery Methods 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000005856 abnormality Effects 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000007613 environmental effect Effects 0.000 description 1
- 238000000802 evaporation-induced self-assembly Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000009257 reactivity Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1438—Restarting or rejuvenating
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Retry When Errors Occur (AREA)
Abstract
The application provides a batch restarting method, equipment and storage medium of CKE nodes. The method comprises the following steps: receiving a query request sent by a user on a front-end application interface, wherein the query request is used for requesting to acquire the running state information of CKE nodes in a data area selected by the user; returning the running state information of the selected CKE node to the front-end application interface; receiving batch target CKE nodes selected by a user on a front-end application interface; and calling proxy service in the data area according to a trigger instruction sent by the user at the front-end application interface, and restarting the batch of target nodes. The method increases the number of CKE nodes restarted at the same time, improves the batch restarting speed of the CKE nodes, and can quickly recover production.
Description
Technical Field
The present application relates to computer technologies, and in particular, to a batch restarting method, apparatus, and storage medium for CKE nodes.
Background
CKE (Chinaunicom Kubernetes Engine) is a multi-Kubernetes cluster deployment platform based on Mesos management, provides a series of complete functions such as efficient deployment, resource management, service discovery and dynamic expansion for containerized applications, solves the problem of environmental consistency in user development, testing and operation and maintenance processes, improves the convenience of large-scale container cluster management, helps users reduce cost and improves efficiency. Nodes (KubeNode) of CKE instances interact through a private network, and when an underlying physical network or a virtual network is abnormal in a large scale and has a long duration, the CKE nodes need to be restarted for recovery.
In the prior art, the problem instance node of CKE is restarted by manpower, so that the time consumption for restarting is huge, and the recovery production is quite unfavorable.
Disclosure of Invention
The application provides a batch restarting method, equipment and a storage medium of CKE nodes, which are used for solving the problem of huge time consumption for manually restarting the CKE nodes.
In a first aspect, the present application provides a batch restarting method of CKE nodes, including:
receiving a query request sent by a user on a front-end application interface, wherein the query request is used for requesting to acquire the running state information of CKE nodes in a data area selected by the user;
returning the running state information of the selected CKE node to the front-end application interface;
receiving batch target CKE nodes selected by a user on the front-end application interface;
and calling the proxy service in the data area according to a trigger instruction sent by the user at the front-end application interface, and restarting the batch of target nodes.
In a second aspect, the present application provides a batch restarting device for CKE nodes, including:
the receiving module is used for receiving a query request sent by a user on a front-end application interface, wherein the query request is used for requesting to acquire the running state information of CKE nodes in a data area selected by the user; receiving batch target CKE nodes selected by a user on the front-end application interface;
the response module is used for returning the running state information of the selected CKE node to the front-end application interface;
and the control module is used for calling the proxy service in the data area according to a trigger instruction sent by the user at the front-end application interface and restarting the batch of target nodes.
In a third aspect, the present application provides a batch restarting device of CKE nodes, including: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes the computer-executable instructions stored by the memory to implement the batch restart method of CKE nodes as described in any of the above.
In a fourth aspect, the present application provides a computer-readable storage medium comprising: the computer readable storage medium has stored therein computer executable instructions that when executed by a processor are for implementing a batch restart method of CKE nodes as described in any of the above.
According to the batch restarting method, equipment and storage medium for CKE nodes, provided by the application, the query request sent by a user on the front-end application interface is received, and the query request is used for requesting to acquire the running state information of the CKE nodes in the data area selected by the user; returning the running state information of the selected CKE node to the front-end application interface; receiving batch target CKE nodes selected by a user on a front-end application interface; and calling proxy service in the data area according to a trigger instruction sent by the user at the front-end application interface, and restarting the batch of target nodes. Because the user needs to select batch target CKE nodes on the front-end interface application and restart the batch target nodes, when the virtual network is abnormal on a large scale, the application can realize batch restarting of the CKE nodes, improves the restarting speed of the CKE nodes and can quickly restore production.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
FIG. 1 is a flow chart of one embodiment of a method for batch restarting of CKE nodes provided by the present application;
FIG. 2 is a flowchart illustrating an embodiment of a batch restart method for CKE nodes according to the present application;
FIG. 3 is a flowchart of an embodiment of a method for batch restarting of CKE nodes according to the present application;
FIG. 4 is a flowchart illustrating a method for batch restarting of CKE nodes according to one embodiment of the present application;
FIG. 5 is a flowchart of a complete embodiment of a method for batch restarting of CKE nodes according to the present application;
FIG. 6 is a schematic diagram of a batch restarting device of CKE nodes according to an embodiment of the present application;
fig. 7 is a schematic diagram of batch restarting equipment of CKE nodes according to an embodiment of the present application.
Specific embodiments of the present application have been shown by way of the above drawings and will be described in more detail below. The drawings and the written description are not intended to limit the scope of the inventive concepts in any way, but rather to illustrate the inventive concepts to those skilled in the art by reference to the specific embodiments.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.
First, the terms involved in the present application will be explained:
chinaunicom Kubernetes Engine (CKE): refers to a Kubernetes (k 8 s) cluster management engine developed based on Mesos, and k8s clusters can be conveniently managed through CKE. The technical layer is a frame work of the Mesos, comprising a central scheduler and an executor. CKE uses Mesos as a bottom IaaS resource management, uses Mesos to manage k8s clusters, and nodes Kubenode of CKE examples interact through a private network, and when a virtual network is abnormal on a large scale, CKE nodes need to be restarted for recovery;
mesos: the system is referred to as an open source distributed resource management framework under Apache, which is called as a kernel of a distributed system;
agent service: an Agent is a computing entity that resides in an environment, can continuously and autonomously act, and has characteristics such as residence, reactivity, sociability, initiative, and the like. The CKE example nodes are divided into a plurality of areas, each area is provided with a corresponding Agent service, and the Agent service can be used for calling the CKE example node restarting interface of the corresponding area and executing a restarting command.
In the prior art, the CKE node is restarted manually, so that the time for restarting the CKE node manually is long, and the recovery of production service is not facilitated.
Aiming at the problems, the CKE node batch restarting method provided by the application can realize that a user inquires the state of the CKE node on a visual interface and performs batch restarting operation on the selected CKE node. The specific technical conception is as follows:
and inquiring the running state information of the CKE nodes on the front-end application interface by a user, selecting the CKE nodes needing to be restarted according to the running state information, performing batch restarting operation, and calling proxy service in the data area according to a restarting command sent by the user on the front-end application interface to restart the CKE nodes needing to be restarted in batches.
The following describes the technical scheme of the present application and how the technical scheme of the present application solves the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Fig. 1 is a flowchart of an embodiment of a batch restarting method of CKE nodes according to the present application, as shown in fig. 1, an execution body of the method may be a control device or a management platform for batch restarting of CKE nodes, where the device/platform may execute the following steps in a hardware manner, a software manner, or a combination of hardware and software manner. The method comprises the following steps:
s101, receiving a query request sent by a user on a front-end application interface, wherein the query request is used for requesting to acquire the running state information of CKE nodes in a data area selected by the user;
the user facing the front-end application interface may be an operation and maintenance staff, and the operation and maintenance staff may query the operation state of the nodes by selecting the data area name and the nodes included on the front-end application interface of a website controlling batch restarting of CKE nodes.
The data area name refers to the name of the area where the CKE node is located, and the current running state of the node may be an abnormal state or a normal running state.
The website for controlling batch restarting of CKE nodes can be generally divided into a front-end application interface and a management platform. The front-end application interface is usually oriented to operation and maintenance staff, the operation and maintenance staff selects a data area name and a node state through the front-end application interface, the management platform can screen out corresponding CKE nodes after receiving a query request sent by a user through the front-end interface, the corresponding CKE node state information is fed back and displayed in the front-end interface, and the state of the CKE nodes can be represented through a CKE node list.
S102, returning the running state information of the selected CKE node to a front-end application interface;
the management platform can call the interface of the CKE product to acquire the running state information of the selected CKE node, and the running state information of the CKE node is returned to the front-end application interface for display.
Wherein, the CKE product interface may obtain the operation status information of the CKE node.
Wherein, the operation state information of the CKE node may include: node identification and running state; further, the information such as the name of the data area, the name of the instance, the host, the node IP and the like can be further included.
S103, receiving batch target CKE nodes selected by a user on a front-end application interface;
the nodes of CKE product examples rely on private networks for interaction, and abnormal nodes in the data area can be caused by large-scale abnormality of the underlying physical network or the virtual network, especially under the condition of large-scale abnormal nodes. The operation and maintenance staff can select nodes in batches through the front-end application interface for restarting operation according to the running state of CKE nodes displayed on the front-end application interface. In order to improve the operation efficiency of restarting and subsequent nodes, an estimation can be made on the nodes which may have abnormality in advance, and the nodes may be in a normal operation state at present, but have relevance to the abnormal nodes, for example: adjacent nodes on physical distance, or service processing association between nodes, etc. And the restarting control can be carried out on the adjacent nodes of the abnormal node or the nodes with business association of the abnormal node in the current normal operation nodes.
The CKE node to be restarted may be selected by an operation and maintenance staff, or may be determined by a management platform and pushed to a front end interface. The CKE node may be selected according to a node state, an abnormal node or a running node may be selected, or a node recommended to be restarted may be pushed to a front-end application interface after being selected by the server, and the operation of determining the node to be restarted may be specifically as follows:
among the CKE nodes selected may be nodes that include a state anomaly, which may generally be referred to as: the CKE node is in a down state. The abnormal node that needs to be restarted may be a node that maintains an abnormal state for more than a set time.
S104, according to a trigger instruction sent by a user at the front-end application interface, invoking proxy service in the data area, and restarting the batch target nodes.
The management platform receives information of operation nodes needing restarting, which is transmitted by the front-end application interface, and can call Agent service of a corresponding area, the Agent service of the corresponding area executes restarting commands on corresponding CKE nodes according to the node information transmitted by the management platform, and returns restarting results of all nodes to the management platform, and the management platform returns the restarting results of all nodes to the front-end application interface.
The information of the operation node needing to be restarted includes: host IP address, instance name, node name, host user, and password information. The Agent service corresponding to the data center logs in the host according to the host IP address, the host user and the password, and executes a restarting command according to the instance name and the node name in the node information.
Wherein, CKE nodes are divided into a plurality of areas, and different areas correspond to different Agent services.
The method comprises the steps of receiving a query request sent by a user on a front-end application interface, wherein the query request is used for requesting to acquire running state information of CKE nodes in a data area selected by the user; returning the running state information of the selected CKE node to the front-end application interface; receiving batch target CKE nodes selected by a user on a front-end application interface; and calling proxy service in the data area according to a trigger instruction sent by the user at the front-end application interface, and restarting the batch of target nodes. Because the user needs to select batch target CKE nodes on the front-end interface application and restart the batch target nodes, when the virtual network is abnormal on a large scale, the application can realize batch restarting of the CKE nodes, improves the restarting speed of the CKE nodes and can quickly restore production.
Fig. 2 is a flowchart of an embodiment of a batch restart method for CKE nodes according to the present application, where the method includes:
s201, calling a CKE product interface to obtain the running state information of CKE nodes in a data area, wherein the running state information comprises: node identification and operational status.
Wherein, step S201 is a specific manner of returning the running state of the selected CKE node to the front-end application interface, which is further provided before step S102 above:
and the management platform calls the CKE product interface to acquire the running state information of the CKE nodes in the data area selected by the front-end application interface.
The operation state information includes: the area name, the instance name, the host computer and the IP address of the node corresponding to the node.
The operation state information of the node may include: node identification and running state; further, the system can also comprise information such as a data area name, an instance name, a host computer where the system is located, a node IP and the like, and the running state information is displayed on a front-end application interface.
And displaying the running state information of the CKE nodes on a front-end application interface in the form of a list.
S202, nodes with abnormal running states, or nodes with abnormal running states and nodes with partial normal running states in the data area.
Wherein, step S202 is further described for batch target CKE nodes based on the previous step S103:
the operation and maintenance staff selects CKE nodes needing restarting in batches on the front-end application interface, the operation state of the CKE nodes can be normal operation state nodes or abnormal operation state nodes, and the abnormal operation state nodes can be in a downtime state under the general condition of the CKE nodes.
S203, determining a recommended restarting node according to the position relation between nodes in the data area and the service processing relevance between the nodes;
in order to improve the operation efficiency of restarting and subsequent nodes, the nodes which are possibly abnormal can be estimated in advance, and the nodes are possibly in a normal operation state at present, but are recommended to users as recommended restarting nodes due to the relevance with the abnormal nodes.
Determining nodes with abnormal running states in the data area, and determining the abnormal running states and adjacent nodes thereof as recommended restarting nodes; or determining the abnormal running state node and the node with the business association as the recommended restart node.
Adjacent nodes on physical distance, or service processing association between nodes, etc. And the restarting control can be carried out on the adjacent nodes of the abnormal node or the nodes with business association of the abnormal node in the current normal operation nodes.
S204, sending the information of recommending the restarting node to a front-end application interface.
And sending the node information for recommending restarting to a front-end application interface, and selecting whether to execute restarting operation on the recommended restarting node by an operation and maintenance worker.
In the prior art, when the virtual network is abnormal on a large scale, CKE nodes need to be restarted one by one manually, and the time consumption is huge.
According to the application, the running state of CKE nodes can be checked on the front-end application interface, the CKE nodes can be selected in batches for restarting, the recommended restarting nodes can be determined according to the position relation among the nodes in the data area and the service processing relevance among the nodes, the recommended restarting nodes are displayed on the front-end application interface, prompt reference is made to a user, the restarting time is reduced, abnormal conditions can be processed more timely, and the method is very beneficial to recovering production services.
FIG. 3 is a flowchart of an embodiment of a method for batch restarting of CKE nodes according to the present application, wherein the flowchart is shown in FIG. 3: management platform 301, proxy service 302, front-end application interface 303.
Receiving a restarting result of batch target nodes returned by the proxy service 302 in the data area;
the management platform 301 accepts the results of batch reboot CKE nodes returned by the proxy service 302 within the data area.
The restart result is returned to the front-end application interface 303. The management platform 301 returns the restart result to the front-end application interface 303, and the front-end application interface 303 displays the restart result.
FIG. 4 is a flowchart illustrating an embodiment of a batch restart method for CKE nodes according to the present application for performing a restart operation, as shown in FIG. 4: front-end application interface 401, management platform 402, proxy service 403, bulk target node information 404.
The management platform 402 receives the restart command transmitted by the front-end application interface 401, and the proxy service 403 of the data area receives the batch target node information 404 transmitted by the management platform 402, and restarts the batch target node.
The user restarts the batch target nodes according to the front-end application interface 401, the management platform 402 receives the batch target node information 404 transmitted by the front-end application interface 401, the management platform 402 calls the proxy service 403 corresponding to the data area, the proxy service 403 corresponding to the data area receives the batch target node information 404 transmitted by the management platform 402, executes a restart command on the batch target nodes, returns a restart result of all the nodes to the management platform 402, and the management platform 402 returns the restart result of all the nodes to the front-end application interface 401 for display.
Bulk target node information 404 includes: the proxy service of the data area logs in to the host according to the host IP address, the host user name and the password, and executes a restarting command according to the instance name and the node name.
The information of the operation node needing to be restarted includes: host IP, instance name, node name, host user, and password information. The Agent service corresponding to the data area logs in the host according to the host IP, the host user and the password, and executes a restarting command according to the CKE instance name and the node name in the node information.
Fig. 5 is a flowchart of a complete embodiment of a batch restarting method of CKE nodes according to the present application, where fig. 5 shows:
the user selects a data area and a node state on the front-end application interface, checks the running state of the node, can select an abnormal node, can select the running node, then the management platform calls the CKE product interface to acquire the related information of the selected node, and returns the related information to the front-end application interface for display, wherein the display mode can be list display.
The user selects an abnormal node on the front-end application interface, calls the management platform to restart the interfaces of CKE products in batches, calls the Agent service of the corresponding area, transmits the abnormal node information of the front-end application interface to the Agent service, corresponds to the Agent service of the data area, executes a restart command, and then returns a restart result to the front-end application interface.
Fig. 6 is a schematic diagram of a batch restarting device of CKE nodes according to an embodiment of the present application, and as shown in fig. 6, a batch restarting device 60 of CKE nodes includes: a receiving module 601, a responding module 602 and a control module 603;
the receiving module 601 is configured to receive a query request sent by a user on a front-end application interface, where the query request is used to request to obtain operation state information of CKE nodes in a data area selected by the user; receiving batch target CKE nodes selected by a user on a front-end application interface;
the response module 602 is configured to return operation state information of the selected CKE node to the front-end application interface;
and the control module 603 is configured to invoke proxy services in the data area according to a trigger instruction sent by the user at the front-end application interface, and restart the batch target nodes.
One possible embodiment of the present application provides a batch restarting device of CKE nodes, and fig. 7 is a schematic diagram of the batch restarting device of CKE nodes provided by the embodiment of the present application, and as shown in fig. 7, the batch restarting device of CKE nodes includes: a processor 701, a memory 702, and a communication interface 703, wherein the processor 701, the memory 702, and the communication interface 703 are connected by a bus 704;
memory 702 stores computer-executable instructions;
processor 701 executes computer-executable instructions stored by memory 702 to implement a batch restart method for CKE nodes as described above.
The specific implementation process of the processor 701 can be referred to the above method embodiment, and its implementation principle and technical effects are similar, and this embodiment will not be described herein again.
In the embodiment shown in fig. 7, it should be understood that the processor may be a central processing unit (english: central Processing Unit, abbreviated as CPU), or may be other general purpose processors, digital signal processors (english: digital Signal Processor, abbreviated as DSP), application specific integrated circuits (english: application Specific Integrated Circuit, abbreviated as ASIC), or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in a processor for execution.
The Memory may comprise high-speed Memory (Random Access Memory, RAM) or may further comprise Non-volatile Memory (NVM), such as at least one disk Memory.
The bus may be an industry standard architecture (Industry Standard Architecture, ISA) bus, an external device interconnect (Peripheral Component, PCI) bus, or an extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, among others. The buses may be divided into address buses, data buses, control buses, etc. For ease of illustration, the buses in the drawings of the present application are not limited to only one bus or to one type of bus.
In one possible embodiment of the present application, there is also provided a computer-readable storage medium having stored therein computer-executable instructions for implementing a batch restart method for CKE nodes as above when executed by a processor.
The computer readable storage medium described above may be implemented by any type or combination of volatile or nonvolatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disk. Computer readable storage media can be any available media that can be accessed by a general purpose or special purpose computer.
An exemplary readable storage medium is coupled to the processor such the processor can read information from, and write information to, the readable storage medium. In the alternative, the computer-readable storage medium may be integral to the processor. The processor and the computer readable storage medium may reside in an application specific integrated circuit (Application Specific Integrated Circuits, ASIC for short). The processor and the computer-readable storage medium may also reside as discrete components in a device.
The division of units is merely a logical function division, and there may be another division manner when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method of the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the method embodiments described above may be performed by hardware associated with program instructions. The foregoing program may be stored in a computer-readable storage medium. The program, when executed, performs steps including the method embodiments described above; and the aforementioned storage medium includes: various media that can store program code, such as ROM, RAM, magnetic or optical disks.
Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. This application is intended to cover any variations, uses, or adaptations of the application following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the application pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It is to be understood that the application is not limited to the precise arrangements and instrumentalities shown in the drawings, which have been described above, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (10)
1. A batch restart method of CKE nodes, comprising:
receiving a query request sent by a user on a front-end application interface, wherein the query request is used for requesting to acquire the running state information of CKE nodes in a data area selected by the user;
returning the running state information of the selected CKE node to the front-end application interface;
receiving batch target CKE nodes selected by a user on the front-end application interface;
and calling the proxy service in the data area according to a trigger instruction sent by the user at the front-end application interface, and restarting the batch of target nodes.
2. The method of claim 1, wherein before returning the operational status information of the selected CKE node to the front-end application interface, further comprising:
calling the CKE product interface to acquire the running state information of the CKE nodes in the data area, wherein the running state information comprises the following components: node identification and operational status.
3. The method of claim 2, wherein the operating state information further comprises:
the area name, the instance name, the host computer and the IP address of the node corresponding to the node.
4. The method of claim 1, wherein the bulk target CKE node may comprise: and the nodes with abnormal running states or the nodes with abnormal running states and the nodes with normal part of running states in the data area.
5. The method of claim 4, wherein after the returning the operational status information of the selected CKE node to the front-end application interface, further comprising:
determining a recommended restarting node according to the position relation between nodes in the data area and the service processing relevance between the nodes;
and sending the information of the recommended restart node to the front-end application interface.
6. The method of claim 5, wherein determining a recommended restart node based on the positional relationship between nodes in the data region and the traffic handling association between nodes comprises:
determining a node with abnormal running state in the data area, and determining the abnormal running state node and adjacent nodes thereof as the recommended restarting node;
or determining the abnormal running state node and the node with business association as the recommended restarting node.
7. The method according to claim 1, wherein the method further comprises:
receiving a restarting result of the batch of target nodes returned by the proxy service in the data area;
and returning the restarting result to the front-end application interface.
8. A batch restart apparatus of CKE nodes, comprising:
the receiving module is used for receiving a query request sent by a user on a front-end application interface, wherein the query request is used for requesting to acquire the running state information of CKE nodes in a data area selected by the user; receiving batch target CKE nodes selected by a user on the front-end application interface;
the response module is used for returning the running state information of the selected CKE node to the front-end application interface;
and the control module is used for calling the proxy service in the data area according to a trigger instruction sent by the user at the front-end application interface and restarting the batch of target nodes.
9. A batch restart apparatus of CKE nodes, comprising: the device comprises a processor, a memory and a communication interface, wherein the processor, the memory and the communication interface are connected through a bus;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored by the memory to implement the batch restart method of CKE nodes of any of claims 1-7.
10. A computer readable storage medium having stored therein computer executable instructions which when executed by a processor are for implementing a batch restart method of CKE nodes according to any of claims 1-7.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202310834147.XA CN116860394A (en) | 2023-07-07 | 2023-07-07 | Batch restarting method, equipment and storage medium of CKE nodes |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202310834147.XA CN116860394A (en) | 2023-07-07 | 2023-07-07 | Batch restarting method, equipment and storage medium of CKE nodes |
Publications (1)
Publication Number | Publication Date |
---|---|
CN116860394A true CN116860394A (en) | 2023-10-10 |
Family
ID=88235329
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202310834147.XA Pending CN116860394A (en) | 2023-07-07 | 2023-07-07 | Batch restarting method, equipment and storage medium of CKE nodes |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN116860394A (en) |
-
2023
- 2023-07-07 CN CN202310834147.XA patent/CN116860394A/en active Pending
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN108388599B (en) | Electronic device, data migration and calling method and storage medium | |
US11392461B2 (en) | Method and apparatus for processing information | |
US8601466B2 (en) | Software deployment method and system, software deployment server and user server | |
CN114257551A (en) | Distributed current limiting method and system and storage medium | |
CN114168239B (en) | Window display method, device, equipment and storage medium | |
US20120227057A1 (en) | Driver Shimming | |
CN110196749B (en) | Virtual machine recovery method and device, storage medium and electronic device | |
CN111143031A (en) | Method and device for changing capacity of virtual machine | |
CN110659104B (en) | Service monitoring method and related equipment | |
CN111506331A (en) | Server BMC refreshing method, system, terminal and storage medium | |
JP2006338225A (en) | Automatic installation method of computer | |
US11861214B2 (en) | Memory device forensics and preparation | |
WO2020096845A1 (en) | Performing actions opportunistically in connection with reboot events in a cloud computing system | |
CN116627702A (en) | Method and device for restarting virtual machine in downtime | |
CN116860394A (en) | Batch restarting method, equipment and storage medium of CKE nodes | |
CN116450165A (en) | Method, system, terminal and storage medium for quickly building environment and deploying program | |
CN109634721B (en) | Method and related device for starting communication between virtual machine and host | |
CN113961366A (en) | Kernel function calling method of operating system and computer equipment | |
CN109445904B (en) | Information processing method and device and computer storage medium | |
CN112711444A (en) | Virtualization method and system for power grid monitoring service unit | |
CN113722011B (en) | Application interface starting method, device, equipment and storage medium | |
CN117951681A (en) | Application starting method, device, equipment and storage medium | |
CN115905271B (en) | Virus library updating method and device and multi-engine detection system | |
CN110297741B (en) | Background task monitoring method and device | |
CN113965530B (en) | Service starting method, device and storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination |