WO2016206501A1 - 一种网管系统中进程的恢复方法、装置和计算机可读存储介质 - Google Patents
一种网管系统中进程的恢复方法、装置和计算机可读存储介质 Download PDFInfo
- Publication number
- WO2016206501A1 WO2016206501A1 PCT/CN2016/082257 CN2016082257W WO2016206501A1 WO 2016206501 A1 WO2016206501 A1 WO 2016206501A1 CN 2016082257 W CN2016082257 W CN 2016082257W WO 2016206501 A1 WO2016206501 A1 WO 2016206501A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network management
- management system
- system process
- resource application
- module
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/28—Error detection; Error correction; Monitoring by checking the correct order of processing
Definitions
- the present application relates to, but is not limited to, the field of communications, and in particular, to a method, an apparatus, and a computer readable storage medium for recovering a process in a network management system.
- the Subnet Manager process works. Each subnet manager manages multiple network elements. The network manager is responsible for forwarding messages to the subnet manager and collecting message summary reports from each subnet manager. Some faults often occur in the project. For example, if a subnet manager fails to exit the process, or the process resources are exhausted, it does not work properly. A management mechanism is needed to restart the failed process to ensure the normal operation of the entire network management system.
- the current practice is to add a background monitoring program to poll the status of each network management process. If a process is found to be absent, then the executable program corresponding to the process is restarted.
- this method can only solve the situation where the process exits abnormally. In the actual project, a certain process may be abnormal without exiting. For example, the process has a memory leak, and after a period of time, the system cannot successfully apply for new memory; or the system does not close some system resources after the process is used, such as a network set. Connections, file handles, registry access handles, etc., caused the re-application of these system resources to fail.
- the embodiment of the invention provides a method, a device and a computer readable storage medium for recovering a process in a network management system, which can solve the problem that the network management system fails due to the system resource application not being released in the related art.
- a method for recovering a process in a network management system comprising:
- the system resource application quantity obtained by the network management system process in the preset time period according to the preset time period includes: obtaining the system resource application quantity of the operating system process according to the preset time period, and applying the system resource application quantity of the operating system process As the system resource application volume of the network management system process, the operating system process corresponds to the network management system process.
- the method further includes:
- the identifier of the operating system process corresponding to the network management system process is updated, and the corresponding relationship between the network management system process and the identifier is established.
- determining whether the system resource application quantity of the network management system process meets the preset condition includes: determining whether the system resource application quantity of the network management system process reaches a preset threshold; or determining the system resource application quantity of the network management system process in the preset time period. Whether the amount of growth has reached the preset increase.
- the process of restarting the network management system includes: closing the network management system process and loading information corresponding to the network management system process.
- the information corresponding to the network management system process includes: an identifier of the network management system process, an executable file of the network management system process, a startup information of the network management system process, and a system resource threshold corresponding to the network management system process.
- the restarting the network management system process includes: restarting the network management system process during an idle period of the network management system corresponding to the network management system process.
- a recovery device for a process in a network management system comprising:
- the acquiring module is configured to obtain, according to a preset time period, a system resource application quantity of the network management system process in a preset time period.
- the determining module is configured to determine whether the system resource application quantity of the network management system process meets the preset condition.
- the module is restarted, and the network management system process is restarted when it is determined that the system resource application quantity of the network management system process meets the preset condition.
- the obtaining module includes: a first acquiring sub-module, configured to acquire a system resource application quantity of the operating system process according to the preset time period, and use the system resource application quantity of the operating system process as the system resource application quantity of the network management system process,
- the operating system process corresponds to the network management system process.
- the device further includes: an update module, configured to update an identifier of an operating system process corresponding to the network management system process, and establish a correspondence between the network management system process and the identifier.
- an update module configured to update an identifier of an operating system process corresponding to the network management system process, and establish a correspondence between the network management system process and the identifier.
- the determining module includes:
- the first determining sub-module is configured to determine whether the system resource application quantity of the network management system process reaches a preset threshold.
- the second determining sub-module is configured to determine whether the amount of increase in the system resource application amount of the network management system process in the preset time period reaches a preset increase amount.
- the restart module includes:
- the first restart sub-module module is configured to close the network management system process and load information corresponding to the network management system process.
- the information corresponding to the network management system process includes:
- the identifier of the NMS system process, the executable file of the NMS system process, the startup information of the NMS system process, and the system resource threshold corresponding to the NMS process is the identifier of the NMS system process, the executable file of the NMS system process, the startup information of the NMS system process, and the system resource threshold corresponding to the NMS process.
- the restarting module further includes:
- the second restart sub-module is configured to restart the network management system process during an idle period of the network management system corresponding to the network management system process.
- a computer readable storage medium storing computer executable instructions that, when executed by a processor, implement a method of recovering a process in the network management system.
- the system resource application amount of the network management system process is monitored in real time, and the network management system process that currently occupies excessive system resources can be discovered in time to find a potentially abnormal network management system process.
- FIG. 1 is a flowchart of a method for restoring a process in a network management system according to an embodiment of the present invention
- FIG. 2 is a schematic structural diagram of a network management system according to an embodiment of the present invention.
- FIG. 3 is a schematic structural diagram of a network management system according to an embodiment of the present invention.
- FIG. 4 is a structural block diagram of a process recovery device in a network management system according to an embodiment of the present invention.
- FIG. 1 is a flowchart of a method for restoring a process in a network management system according to an embodiment of the present invention. As shown in FIG. 1, the process includes steps S101 to S103. :
- the network management system process that occupies too much system resources in the network management system can be discovered in time to find a potentially abnormal network management system process.
- the network management system failure caused by the system resource application not being released in the related technology is solved, and the technical effect of reducing the network management system failure rate and improving the network management system availability is achieved.
- the network management system includes a network manager, one or more subnet managers, and the network manager process works in conjunction with one or more subnet manager processes.
- 2 is a schematic structural diagram of a network management system according to an embodiment of the present invention. As shown in FIG. 2, the process of the network manager 11 is responsible for forwarding messages to the subnet managers 21, 22, and 23, and acquiring messages of multiple subnet managers. Perform a summary report. The processes of the subnet managers 21, 22, and 23 are responsible for managing the network elements in the respective subnets.
- the method for recovering the process in the network management system of the embodiment is described below with reference to the network management system shown in FIG. 2. It should be noted that the method for recovering the process in the network management system in the embodiment of the present invention is not limited to the one shown in FIG. In the network management system, the recovery method of the process in the network management system of the embodiment of the present invention is also applicable to the network management system of other configurations.
- FIG. 3 is a schematic structural diagram of a network management system according to an embodiment of the present invention.
- the monitoring module 31 is configured to monitor a network manager and a subnet manager in a network management system in real time, wherein the monitoring module 31 is pre-configured.
- the network management system process list required for the network management system to work normally and the information corresponding to each network management system process in the network management system process list.
- the network management system process in the network management system includes a network manager process 110 and a subnet manager process 210, 220, and 230.
- the monitoring module 31 is a process that is separately configured to monitor the process of the network management system.
- the monitoring module 31 needs to be configured with a corresponding network management system process list and a corresponding network management system process in the network management system process list. Information to ensure the normal operation of the network management system.
- the content configured in the monitoring module 31 includes:
- a list of network management system processes including network manager process 110, subnet manager processes 210, 220, 230.
- the information corresponding to each NMS system process in the NMS process list includes:
- ID of the NMS process such as the ID of the network manager process is 110
- subnet manager The process identifiers are 210, 220, and 230, respectively.
- the executable file of the network management system process is the file of the executable program loaded when the network management system process is restarted.
- the executable program of the subnet manager corresponding to the network element of different device types is different.
- the subnet manager 21 manages the network element of the network element type A
- the file of the executable program used is A1.exe
- the subnet manager 22 and the subnet manager 23 manage the network element of the network element type B
- the The file of the execution program is B1.exe
- the network manager 11 manages all the subnet managers, including the subnet manager 21, the subnet manager 22, and the subnet manager 23, and the file of the executable program used is C1.exe. .
- the startup information of the network management system process is the startup information required to restart the network management system process, such as the subnet ID and network listening port number.
- the network manager 11 does not need additional startup information, and the subnet managers 21, 22, and 23 need their respective subnet IDs, which are assumed to be 1201, 1202, and 1203, respectively, and are set to acquire respective managed networks through subnet IDs. yuan.
- the system resource threshold corresponding to the network management system process is the maximum number of system resource requests allowed by the gateway system process.
- the system resource threshold of the network management system process is 500M. This embodiment assumes that only the resource application amount of the system memory is monitored. The other system resources are not described here. However, the recovery method of the process in the network management system of this embodiment is also applicable.
- the monitoring module 31 After the monitoring module 31 is created, and the information corresponding to each network management system process in the network management system process list and the network management system process list is configured, the monitoring module 31 starts to perform steps S101 to S103:
- the monitoring module 31 Before performing step S101, the monitoring module 31 first establishes a correspondence table between the operating system process and the network management system process, so as to monitor the network management system integration during the execution of the operating system process.
- the operating system process is a process in the operating system where the network management system is located, such as the Windiws operating system.
- the operating system includes multiple operating system processes, and each operating system process has a unique operating system process identifier.
- establishing a correspondence table between the operating system process and the network management system process may include the following steps S201-S202:
- the monitoring module 31 traverses all operating system processes under the current operating system:
- the operation system is recorded.
- the identifier of the process such as 101;
- the subnet manager process 210 When the process named A1.exe is found, that is, the subnet manager process 210 records the identifier of the operating system process, such as 201;
- the subnet manager process 220, 230 records the identity of the operating system process, such as 202, 203.
- each operating system process is required to report its own startup information, that is, the startup information of the network management system process, that the network manager 11 does not need additional startup information, and the subnet managers 21, 22, and 23 need respective subnets.
- IDs are 1201, 1202, and 1203, respectively.
- the monitoring module 31 establishes a correspondence table between the operating system process and the network management system process, as shown in Table 1, where Table 1 is a correspondence table between the operating system process and the network management system process.
- the monitoring module 31 can implement system resources of the network management system processes 110, 210, 220, and 220 by periodically monitoring the system resource application amount of the operating system processes 101, 201, 202, and 203. Timing monitoring of the amount of application.
- step S101 acquires a network management system process in a preset time period according to a preset time period.
- the system resource application amount during the period includes: obtaining the system resource application amount of the operating system process according to the preset time period, and applying the system resource application quantity of the operating system process as the system resource application quantity of the network management system process, wherein the operating system process is Corresponding to the network management system process, the corresponding relationship can be as shown in Table 1.
- the preset time period in step S101 can be set according to actual requirements, for example, 1 hour, 10 minutes, that is, the system resource application amount of the network management system process within 1 hour or 10 minutes is obtained every 1 hour or 10 minutes.
- the system resource application quantity of the network management system process in a preset time period refers to the total amount of system resources (such as memory) applied by the network management system process within a preset time period.
- the monitoring module 31 can be configured with different preset time periods for different network management system processes, or different preset time periods for different system resource configurations. For example, if you need to obtain other system resources in the network management system, you can set different time periods, such as the number of files that the network management system process opens at the same time every 2 hours.
- Obtaining the system resource application amount of the operating system process is generally implemented by calling an application function interface provided by the operating system. For example, under the Windows operating system, obtaining the system resource (such as memory) application amount is by using the operating system process ID as an input parameter. Call the process class application process interface function to achieve.
- an application function interface provided by the operating system. For example, under the Windows operating system, obtaining the system resource (such as memory) application amount is by using the operating system process ID as an input parameter. Call the process class application process interface function to achieve.
- step S102 After the monitoring module 31 acquires the system resource application amount of the network management system process in the preset time period according to the preset time period, the monitoring module 31 executes step S102.
- the preset condition in step S102 can determine the system resource application quantity of the network management system process, and can also determine the increase amount of the system resource application quantity of the network management system process.
- determining whether the system resource application quantity of the network management system process meets the preset condition includes: determining whether the system resource application quantity of the network management system process reaches a preset threshold; or determining the system resource application quantity of the network management system process in the preset time period. Whether the amount of growth has reached the preset increase.
- the preset threshold and the preset increase amount can be set according to actual needs.
- the growth of the system resource application amount of the network management system process can be analyzed, thereby Find a potentially abnormal network management system process.
- the determination of the above two methods is beneficial to improve the accuracy of monitoring the system resource application amount of the network management system process, thereby achieving the technical effect of accurately analyzing the possibility of the network management system failure.
- step S102 it is determined whether the system resource application amount of the network management system process meets the preset bar. After the device determines that the system resource application quantity of the network management system process meets the preset condition, the network management system process is restarted, that is, step S103.
- the process of restarting the network management system includes: closing the network management system process and loading information corresponding to the network management system process. After the process of restarting the network management system is different, the identifier of the corresponding operating system process is different from that of the operating system process that is not reloaded. Therefore, the embodiment further includes: updating and managing the network management system after restarting the network management system process. ID of the operating system process corresponding to the system process, and re-establishes the corresponding relationship between the NMS process and the identifier.
- the monitoring module 31 monitors the operating system process with the ID of 101, that is, the system resource application amount (application memory amount) of the network manager process 110 is 502M, and the preset threshold is 500M, and the ID is 101.
- the operating system process, network manager process 110, and the executable file C1.exe can be loaded directly because there is no additional startup information.
- the process ID of the operating system process and the network management system process are updated. 2 shows:
- the monitoring module 31 monitors the operating system process with the process ID 202 in three consecutive time periods (the time period is 1 hour), that is, the system resource application amount (memory application amount) of the subnet manager process 220 is respectively 450M, 460M, 470M, it can be analyzed that the hourly increase of the memory application amount of the subnet manager process 220 is 10M, and the system resource application amount after 3 hours will exceed the preset threshold (500M). If the current network management system is in an idle period, such as 12:00 in the middle of the night, the subnet manager process 220 can be closed, and the executable file B1.exe is loaded, and the startup information subnet ID 1202 is loaded.
- the system resource application amount memory application amount
- 500M preset threshold
- the monitoring module 31 needs to update the correspondence table between the operating system process and the network management system process, and the corresponding operating system process corresponds to the network management system process.
- the table is shown in Table 3:
- the network management system process can be restarted immediately. In order to ensure the normal operation of the network management system, the network management system process may not be restarted immediately.
- the system resource application amount of the network management system process in the current preset time period reaches a preset threshold, but by analyzing the growth amount, it can be determined that it will exceed the preset threshold after a period of time, and is used in the idle period of the network management system. Restarting the network management system process is beneficial to ensuring the normal operation of the network management system and timely discovering the network management system process of the network management system. This ensures the availability of the network management system to the greatest extent.
- the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
- the technical solution of the present invention in essence or the contribution to the related art can be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, CD-ROM).
- the instructions include a number of instructions for causing a terminal device (which may be a cell phone, computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention.
- a recovery device for the process in the network management system.
- the device is used to implement the foregoing embodiments and preferred embodiments, and details are not described herein.
- the term "module” may implement a combination of software and/or hardware of a predetermined function.
- the apparatus described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware, is also possible and contemplated.
- FIG. 4 is a structural block diagram of a process recovery device in a network management system according to an embodiment of the present invention. As shown in FIG. 4, the device includes:
- the obtaining module 41 is configured to acquire, according to a preset time period, a system resource application quantity of the network management system process in a preset time period;
- the determining module 42 is configured to determine whether the system resource application quantity of the network management system process meets a preset condition
- the restarting module 43 is configured to restart the network management system process when determining that the system resource application quantity of the network management system process meets the preset condition.
- the obtaining module 41 includes: a first acquiring sub-module, configured to acquire a system resource application quantity of the operating system process according to a preset time period, and use the system resource application quantity of the operating system process as the system resource application quantity of the network management system process.
- the operating system process corresponds to the network management system process.
- the determining module 42 includes: a first determining sub-module, configured to determine whether the system resource application quantity of the network management system process reaches a preset threshold; and the second determining sub-module is configured to determine the network management system process in the preset time period. Whether the increase in the number of system resource applications reaches the preset increase.
- the restarting module 43 includes: a first restarting submodule module, configured to close the network management system process, and load information corresponding to the network management system process.
- the information corresponding to the network management system process includes: the identifier of the network management system process, the executable file of the network management system process, the startup information of the network management system process, and the system resource threshold corresponding to the network management system process.
- the restarting module 43 may further include: a second restarting submodule, configured to restart the network management system process during an idle period of the network management system corresponding to the network management system process.
- the recovery device of the process in the network management system of the embodiment further includes: an update module, configured to update an identifier of an operating system process corresponding to the network management system process, and establish a correspondence between the network management system process and the identifier.
- an update module configured to update an identifier of an operating system process corresponding to the network management system process, and establish a correspondence between the network management system process and the identifier.
- the recovery device of the process in the network management system of the embodiment obtains the system resource application quantity of the network management system process in the preset time period according to the preset time period, and determines whether the system resource application quantity of the network management system process is determined by the determining module 42.
- the network management system process is restarted by the restarting module 43 when the system resource application quantity of the network management system process is determined to meet the preset condition, and the network management system failure caused by the system resource application not being released in the related technology is solved.
- each of the above modules may be implemented by software or hardware.
- the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are located in multiple In the processor.
- a computer readable storage medium storing computer executable instructions that, when executed by a processor, implement a method of recovering a process in the network management system.
- the foregoing storage medium may be configured to be stored for performing the following Step code:
- S1 Obtain a system resource application quantity of the network management system process in a preset time period according to a preset time period.
- S2 Determine whether the system resource application quantity of the network management system process meets a preset condition.
- S3 Restart the network management system process when determining that the system resource application quantity of the network management system process meets the preset condition.
- the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory.
- ROM Read-Only Memory
- RAM Random Access Memory
- a mobile hard disk e.g., a hard disk
- magnetic memory e.g., a hard disk
- modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
- the steps shown or described are performed, or they are separately fabricated into individual integrated circuit modules, or a plurality of modules or steps thereof are fabricated as a single integrated circuit module.
- the invention is not limited to any specific combination of hardware and software.
- all or part of the steps of the above embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.
- the device/function module/functional unit in the above embodiment can be implemented by using a general-purpose computing device. Now, they can be concentrated on a single computing device or distributed over a network of multiple computing devices.
- the device/function module/functional unit in the above embodiment When the device/function module/functional unit in the above embodiment is implemented in the form of a software function module and sold or used as a stand-alone product, it can be stored in a computer readable storage medium.
- the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.
- the system resource application quantity of the network management system process is monitored in real time, and the network management system process that currently occupies excessive system resources can be discovered in time to find a potentially abnormal network management system process.
Abstract
一种网管系统中进程的恢复方法、装置和计算机可读存储介质，该方法包括：按照预设时间周期获取网管系统进程在预设时间周期内的系统资源申请量；判断网管系统进程的系统资源申请量是否符合预设条件；以及在判定网管系统进程的系统资源申请量符合预设条件时，重新启动网管系统进程。
Description
本申请涉及但不限于通信领域，尤其涉及一种网管系统中进程的恢复方法、装置和计算机可读存储介质。
随着网管系统越来越庞大，功能越来越多，管理的设备种类和数量也越来越多，进而出现了需要多个进程协作管理的需求，比如一个网络管理器(Manager)进程协同多个子网管理器(Subnet Manager)进程工作，每个子网管理器管理多个网元，网络管理器负责把消息转发到子网管理器以及收集来自每个子网管理器的消息汇总上报。工程中经常出现一些故障，比如某个子网管理器出现故障进程退出了，或者进程资源耗尽不能正常工作了，需要有一个管理机制来重启发生故障的进程来确保整个网管系统的正常工作。
目前的做法是加一个后台监控程序，轮询每一个网管进程的状态，如果发现某个进程不在了，那么就重新启动这个进程对应的可执行程序。但是这种方法只能解决进程异常退出的情景。实际工程中，某个进程可能会出现异常而不退出的情况，比如，进程存在内存泄露，一段时间后无法从系统成功申请新的内存；或者进程使用完毕后没有关闭一些系统资源，比如网络套接字、文件句柄、注册表访问句柄等，导致这些系统资源的再次申请失败。这些因系统资源申请而没有正确释放造成的后果是累积性的，在一段时间内不影响整个系统的正常工作，但是随着进程工作时间的增加，系统的负担也会逐渐加重，直到不能正常工作。而这些问题的定位往往比较困难，在定位前需要有一个应急的方法。
针对相关技术中系统资源申请没有得到释放造成的网管系统故障的问题，目前尚未提出有效的解决方案。
发明内容
以下是对本文详细描述的主题的概述。本概述并非是为了限制权利要求
的保护范围。
本发明实施例提供了一种网管系统中进程的恢复方法、装置和计算机可读存储介质，能够解决相关技术中系统资源申请没有得到释放造成的网管系统故障的问题。
一种网管系统中进程的恢复方法，包括：
按照预设时间周期获取网管系统进程在预设时间周期内的系统资源申请量。
判断网管系统进程的系统资源申请量是否符合预设条件。
在判定网管系统进程的系统资源申请量符合预设条件时，重新启动网管系统进程。
可选地，按照预设时间周期获取网管系统进程在预设时间周期内的系统资源申请量包括：按照预设时间周期获取操作系统进程的系统资源申请量，将操作系统进程的系统资源申请量作为网管系统进程的系统资源申请量，其中，操作系统进程是与网管系统进程对应的。
可选地，该方法还包括：
在重新启动所述网管系统进程之后，更新与网管系统进程对应的操作系统进程的标识，并建立网管系统进程与标识的对应关系。
可选地，判断网管系统进程的系统资源申请量是否符合预设条件包括：判断网管系统进程的系统资源申请量是否达到预设门限；或者判断预设时间周期内网管系统进程的系统资源申请量的增长量是否达到预设增长量。
可选地，重新启动网管系统进程包括：关闭网管系统进程，并加载网管系统进程对应的信息。
可选地，网管系统进程对应的信息包括：网管系统进程的标识、网管系统进程的可执行文件、网管系统进程的启动信息以及网管系统进程对应的系统资源门限。
可选地，重新启动网管系统进程包括：在与网管系统进程所对应的网管系统的空闲时段重新启动网管系统进程。
一种网管系统中进程的恢复装置，包括：
获取模块，设置为按照预设时间周期获取网管系统进程在预设时间周期内的系统资源申请量。
判断模块，设置为判断网管系统进程的系统资源申请量是否符合预设条件。
重启模块，设置为在判定网管系统进程的系统资源申请量符合预设条件时，重新启动网管系统进程。
可选地，获取模块包括：第一获取子模块，设置为按照预设时间周期获取操作系统进程的系统资源申请量，将操作系统进程的系统资源申请量作为网管系统进程的系统资源申请量，其中，操作系统进程是与网管系统进程对应的。
可选地，该装置还包括：更新模块，设置为更新与网管系统进程对应的操作系统进程的标识，并建立网管系统进程与标识的对应关系。
可选地，判断模块包括：
第一判断子模块，设置为判断网管系统进程的系统资源申请量是否达到预设门限。
第二判断子模块，设置为判断预设时间周期内网管系统进程的系统资源申请量的增长量是否达到预设增长量。
可选地，重启模块包括：
第一重启子模块模块，设置为关闭网管系统进程，并加载网管系统进程对应的信息。
可选地，网管系统进程对应的信息包括：
网管系统进程的标识、网管系统进程的可执行文件、网管系统进程的启动信息以及网管系统进程对应的系统资源门限。
可选地，重启模块还包括：
第二重启子模块，设置为在与网管系统进程所对应的网管系统的空闲时段重新启动网管系统进程。
一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现所述的网管系统中进程的恢复方法。
通过本发明实施例的方案，采用实时监测网管系统进程的系统资源申请量的方式，能够及时发现当前占用过多系统资源的网管系统进程，从而找到潜在的异常的网管系统进程。通过将占用系统资源过多的网管系统进程重新启动，解决了相关技术中系统资源申请没有得到释放造成的网管系统故障的问题，达到了最大程度的保证网管系统可用性的效果。
附图概述
图1是根据本发明实施例的网管系统中进程的恢复方法的流程图；
图2是根据本发明实施例的网管系统结构示意图；
图3是根据本发明实施例的网管系统结构布局示意图；
图4是根据本发明实施例的网管系统中进程的恢复装置的结构框图。
下面结合附图对本发明的实施方式进行描述。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
在本实施例中提供了一种网管系统中进程的恢复方法，图1是根据本发明实施例的网管系统中进程的恢复方法的流程图，如图1所示，该流程包括步骤S101～S103：
S101、按照预设时间周期获取网管系统进程在预设时间周期内的系统资源申请量。
S102、判断网管系统进程的系统资源申请量是否符合预设条件；
S103、在判定网管系统进程的系统资源申请量符合预设条件时，重新启动网管系统进程。
通过上述步骤，能够及时地发现网管系统中占用系统资源过多的网管系统进程，从而找到潜在异常的网管系统进程。通过重新启动占用系统资源过多的网管系统进程，解决了相关技术中系统资源申请没有得到释放造成的网管系统故障，达到了降低网管系统故障发生率，提高网管系统可用性的技术效果。
网管系统包括一个网络管理器、一个或者多个子网管理器，网络管理器进程协同一个或者多个子网管理器进程工作。图2是根据本发明实施例的网管系统结构示意图，如图2所示，网络管理器11的进程负责将消息转发至子网管理器21、22、23，并获取多个子网管理器的消息进行汇总上报。子网管理器21、22、23的进程分别负责管理各自子网内的网元。下面以图2中所示的网管系统说明该实施例的网管系统中进程的恢复方法，需要说明的是，本发明实施例中的网管系统中进程的恢复方法并不仅限于图2中所示的网管系统，对于其他结构的网管系统，本发明实施例的网管系统中进程的恢复方法同样适用。
可选地，本发明预先创建网管系统的监测模块，该监测模块可以设置为执行上述步骤S101至步骤S103。图3是根据本发明实施例的网管系统结构布局示意图，如图3所示，该监测模块31设置为实时监测网管系统中的网络管理器和子网管理器，其中，该监测模块31中预先配置有网管系统正常工作所需的网管系统进程列表以及网管系统进程列表中每个网管系统进程对应的信息。其中，网管系统中的网管系统进程包括网络管理器进程110，子网管理器进程210、220、230。
监测模块31为一个单独地设置为监测网管系统进程的进程，对于不同的网管系统工程组网，需要对监测模块31配置相应的网管系统进程列表以及网管系统进程列表中每个网管系统进程对应的信息，以保证网管系统的正常工作。可选地，监测模块31中配置的内容包括：
网管系统进程列表，包括网络管理器进程110，子网管理器进程210、220、230。
网管系统进程列表中每个网管系统进程对应的信息包括：
网管系统进程的标识，比如网络管理器进程的标识为110，子网管理器
进程的标识分别为210、220、230。
网管系统进程的可执行文件，为重新启动网管系统进程时加载的可执行程序的文件。通常情况下，不同设备类型的网元对应的子网管理器的可执行程序是不同的。比如，子网管理器21管理网元类型A的网元，使用的可执行程序的文件为A1.exe，子网管理器22和子网管理器23管理网元类型B的网元，使用的可执行程序的文件为B1.exe，网络管理器11管理所有的子网管理器，包括子网管理器21，子网管理器22和子网管理器23，使用的可执行程序的文件是C1.exe。
网管系统进程的启动信息，为重新启动网管系统进程时所需的启动信息，比如子网ID，网络监听端口号等。比如，网络管理器11不需要额外的启动信息，而子网管理器21、22、23需要各自的子网ID，假设分别为1201、1202、1203，设置为通过子网ID获取各自管理的网元。
网管系统进程对应的系统资源门限，为网关系统进程允许的系统资源申请量的最大值，比如设置网管系统进程的系统资源门限为500M。该实施例假设只监测系统内存的资源申请量，对于其他的系统资源此处不再介绍，但是，该实施例的网管系统中进程的恢复方法同样可以适用。
在创建监测模块31，并配置好网管系统进程列表以及网管系统进程列表中每个网管系统进程对应的信息之后，该监测模块31开始执行步骤S101至步骤S103：
在执行步骤S101之前，监测模块31首先建立操作系统进程与网管系统进程的对应表，以便于在执行操作系统进程中对网管系统集成进行监测。其中，操作系统进程为网管系统所在的操作系统中的进程，比如Windiws操作系统。操作系统下包括多个操作系统进程，每个操作系统进程对应有唯一的操作系统进程标识。
可选地，建立操作系统进程与网管系统进程的对应表可以包括以下步骤S201～S202：
S201、监测模块31遍历当前操作系统下的所有操作系统进程：
当找到名称为C1.exe的进程时，即网络管理器进程110，记录此操作系
统进程的标识，比如101；
当找到名称为A1.exe的进程时，即子网管理器进程210，记录此操作系统进程的标识，比如201；
当找到名称为B1.exe的进程时，即子网管理器进程220、230，记录此操作系统进程的标识，比如202、，203。
S202、要求每个操作系统进程上报自己的启动信息，即网管系统进程的启动信息，分别为网络管理器11不需要额外的启动信息，而子网管理器21、22、23需要各自的子网ID，分别为1201、1202、1203。
通过上述步骤，监测模块31建立了操作系统进程与网管系统进程的对应表，如表1所示，其中，表1为操作系统进程与网管系统进程的对应表。
表1
建立操作系统进程与网管系统进程的对应表，监测模块31通过定时监测操作系统进程101、201、202、203的系统资源申请量便可以实现对网管系统进程110、210、220、220的系统资源申请量的定时监测。
可选地，步骤S101按照预设时间周期获取网管系统进程在预设时间周
期内的系统资源申请量包括：按照预设时间周期获取操作系统进程的系统资源申请量，将操作系统进程的系统资源申请量作为网管系统进程的系统资源申请量，其中，操作系统进程是与网管系统进程对应的，其对应关系可以如表1所示。
步骤S101中的预设时间周期可以根据实际需求设定，比如1个小时，10分钟，即每隔1小时或者10分钟获取一次网管系统进程在1小时或者10分钟内的系统资源申请量。网管系统进程在预设时间周期内的系统资源申请量是指在预设时间周期内，该网管系统进程申请的系统资源(比如内存)总量。监测模块31可以对不同的网管系统进程配置有不同的预设时间周期，也可以对不同系统资源配置有不同的预设时间周期。比如，如果需要获取网管系统内的其他系统资源，可以采取设定不同的时间周期，比如每2小时采集一次网管系统进程的文件同时打开的数量。获取操作系统进程的系统资源申请量一般是通过调用操作系统提供的应用函数接口来实现的，比如Windows操作系统下，获取系统资源(比如内存)申请量是通过使用操作系统进程ID作为输入参数，调用进程类应用过程接口函数来实现的。
监测模块31在执行步骤S101按照预设时间周期获取网管系统进程在预设时间周期内的系统资源申请量之后，执行步骤S102。步骤S102中的预设条件可以判定网管系统进程的系统资源申请量，也可以判定网管系统进程的系统资源申请量的增长量。
可选地，判断网管系统进程的系统资源申请量是否符合预设条件包括：判断网管系统进程的系统资源申请量是否达到预设门限；或者判断预设时间周期内网管系统进程的系统资源申请量的增长量是否达到预设增长量。其中，预设门限和预设增长量可以根据实际需求设定。
通过判断网管系统进程的系统资源申请量是否达到预设门限，或者通过多次的对比多次网管系统进程的系统资源申请的对比，能够分析出网管系统进程的系统资源申请量的增长量，从而找到潜在异常的网管系统进程。通过上述两种方式的判定，有利于提高对网管系统进程的系统资源申请量监测的准确度，进而达到准确分析网管系统故障可能性的技术效果。
在执行步骤S102判断网管系统进程的系统资源申请量是否符合预设条
件之后，在判定在判定网管系统进程的系统资源申请量符合预设条件时，重新启动网管系统进程，即步骤S103。
当判定网管系统进程的系统资源申请量达到预设门限，或者预设时间周期内网管系统进程的系统资源申请量的增长量达到预设增长量时，重新启动该网管系统进程。
可选地，重新启动网管系统进程包括：关闭网管系统进程，并加载网管系统进程对应的信息。由于重新启动网管系统进程之后对应的操作系统进程的标识与未重新加载网管系统进程之前对应的操作系统进程的标识不同，所以，该实施例还包括：在重新启动网管系统进程之后，更新与网管系统进程对应的操作系统进程的标识，并重新建立网管系统进程与标识的对应关系。
比如，监测模块31监测到ID为101的操作系统进程，即网络管理器进程110的系统资源申请量(申请内存量)为502M，已经超过了预设门限500M，则关闭该ID为101对应的操作系统进程，即网络管理器进程110，并加载可执行文件C1.exe，由于没有额外的启动信息，则可以直接加载。由于加载后的进程ID往往与之前的进程ID 101不同，比如为102，监测模块31需要更新操作系统进程与网管系统进程的对应表，更新后的操作系统进程与网管系统进程的对应表如表2所示：
表2
再比如，监测模块31在连续的三个时间周期(时间周期为1小时)监测到进程ID为202的操作系统进程，即子网管理器进程220的系统资源申请量(内存申请量)分别为450M、460M、470M，则可以分析出该子网管理器进程220的内存申请量的每小时的增长量为10M，则3小时之后的系统资源申请量将会超过预设门限(500M)。如果当前时刻网管系统处于空闲时段，比如半夜12:00，则可以关闭该子网管理器进程220，并加载可执行文件B1.exe，加载启动信息子网ID 1202。同理，由于加载后的进程ID往往与之前的进程ID 202不同，比如为208，监测模块31需要更新操作系统进程与网管系统进程的对应表，更新后的操作系统进程与网管系统进程的对应表如表3所示：
表3
可选地，在判定网管系统进程的系统资源申请量达到预设门限，或者预
设时间周期内网管系统进程的系统资源申请量的增长量达到预设增长量时，可以立即重新启动网管系统进程，或者，为了保证网管系统正常工作，可以不立即重新启动网管系统进程，而是在网管系统的空闲时段重新启动网管系统进程。对于当前预设时间周期内的网管系统进程的系统资源申请量为达到预设门限，但是通过分析其增长量，可以判定其在一段时间后会超过预设门限的情况，采用在网管系统空闲时段重新启动该网管系统进程，既有利于保证网管系统的正常工作，又能够及时发现网管系统潜在异常的网管系统进程，达到了最大程度地保证了网管系统的可用性的效果。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明的技术方案本质上或者说对相关技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
在本实施例中还提供了一种网管系统中进程的恢复装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图4是根据本发明实施例的网管系统中进程的恢复装置的结构框图，如图4所示，该装置包括：
获取模块41，设置为按照预设时间周期获取网管系统进程在预设时间周期内的系统资源申请量；
判断模块42，设置为判断网管系统进程的系统资源申请量是否符合预设条件；
重启模块43，设置为在判定网管系统进程的系统资源申请量符合预设条件时，重新启动网管系统进程。
可选地，获取模块41包括：第一获取子模块，设置为按照预设时间周期获取操作系统进程的系统资源申请量，将操作系统进程的系统资源申请量作为网管系统进程的系统资源申请量，其中，操作系统进程是与网管系统进程对应的。
可选地，判断模块42包括：第一判断子模块，设置为判断网管系统进程的系统资源申请量是否达到预设门限；第二判断子模块，设置为判断预设时间周期内网管系统进程的系统资源申请量的增长量是否达到预设增长量。
可选地，重启模块43包括：第一重启子模块模块，设置为关闭网管系统进程，并加载网管系统进程对应的信息。其中，网管系统进程对应的信息包括：网管系统进程的标识、网管系统进程的可执行文件、网管系统进程的启动信息以及网管系统进程对应的系统资源门限。
可选地，重启模块43还可以包括：第二重启子模块，设置为在与网管系统进程所对应的网管系统的空闲时段重新启动网管系统进程。
可选地，该实施例的网管系统中进程的恢复装置还包括：更新模块，设置为更新与网管系统进程对应的操作系统进程的标识，并建立网管系统进程与标识的对应关系。
该实施例的网管系统中进程的恢复装置通过获取模块41按照预设时间周期获取网管系统进程在预设时间周期内的系统资源申请量，通过判断模块42判断网管系统进程的系统资源申请量是否符合预设条件，通过重启模块43在判定网管系统进程的系统资源申请量符合预设条件时，重新启动网管系统进程，解决了相关技术中系统资源申请没有得到释放造成的网管系统故障，达到了降低网管系统故障发生率，提高网管系统可用性的技术效果。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述模块分别位于多个处理器中。
一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现所述的网管系统中进程的恢复方法。
可选地，在本实施例中，上述存储介质可以被设置为存储用于执行以下
步骤的程序代码：
S1，按照预设时间周期获取网管系统进程在预设时间周期内的系统资源申请量。
S2，判断网管系统进程的系统资源申请量是否符合预设条件。
S3，在判定网管系统进程的系统资源申请量符合预设条件时，重新启动网管系统进程。
可选地，在本实施例中，上述存储介质可以包括但不限于：U盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
可选地，本实施例中的示例可以参考上述实施例及可选实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本发明的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，可选地，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中，所述计算机程序在相应的硬件平台上(如系统、设备、装置、器件等)执行，在执行时，包括方法实施例的步骤之一或其组合。
可选地，上述实施例的全部或部分步骤也可以使用集成电路来实现，这些步骤可以被分别制作成一个个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。
上述实施例中的装置/功能模块/功能单元可以采用通用的计算装置来实
现，它们可以集中在单个的计算装置上，也可以分布在多个计算装置所组成的网络上。
上述实施例中的装置/功能模块/功能单元以软件功能模块的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。上述提到的计算机可读取存储介质可以是只读存储器，磁盘或光盘等。
本发明实施例的方案，采用实时监测网管系统进程的系统资源申请量的方式，能够及时发现当前占用过多系统资源的网管系统进程，从而找到潜在的异常的网管系统进程。通过将占用系统资源过多的网管系统进程重新启动，解决了相关技术中系统资源申请没有得到释放造成的网管系统故障的问题，达到了最大程度的保证网管系统可用性的效果。
Claims (15)
- 一种网管系统中进程的恢复方法，包括：按照预设时间周期获取网管系统进程在所述预设时间周期内的系统资源申请量；判断所述网管系统进程的系统资源申请量是否符合预设条件；在判定所述网管系统进程的系统资源申请量符合所述预设条件时，重新启动所述网管系统进程。
- 根据权利要求1所述的方法，其中，所述按照预设时间周期获取网管系统进程在所述预设时间周期内的系统资源申请量包括：按照所述预设时间周期获取操作系统进程的系统资源申请量，将所述操作系统进程的系统资源申请量作为所述网管系统进程的系统资源申请量，其中，所述操作系统进程是与所述网管系统进程对应的。
- 根据权利要求2所述的方法，所述方法还包括：在重新启动所述网管系统进程之后，更新与所述网管系统进程对应的操作系统进程的标识，并建立所述网管系统进程与所述标识的对应关系。
- 根据权利要求1所述的方法，其中，所述判断所述网管系统进程的系统资源申请量是否符合预设条件包括：判断所述网管系统进程的系统资源申请量是否达到预设门限；或者判断所述预设时间周期内所述网管系统进程的系统资源申请量的增长量是否达到预设增长量。
- 根据权利要求1所述的方法，其中，所述重新启动所述网管系统进程包括：关闭所述网管系统进程，并加载所述网管系统进程对应的信息。
- 根据权利要求5所述的方法，其中，所述网管系统进程对应的信息包括：所述网管系统进程的标识、所述网管系统进程的可执行文件、所述网管系统进程的启动信息以及所述网管系统进程对应的系统资源门限。
- 根据权利要求1所述的方法，其中，重新启动所述网管系统进程包括：在与所述网管系统进程所对应的网管系统的空闲时段重新启动所述网管系统进程。
- 一种网管系统中进程的恢复装置，包括：获取模块，设置为按照预设时间周期获取网管系统进程在所述预设时间周期内的系统资源申请量；判断模块，设置为判断所述网管系统进程的系统资源申请量是否符合预设条件；重启模块，设置为在判定所述网管系统进程的系统资源申请量符合所述预设条件时，重新启动所述网管系统进程。
- 根据权利要求8所述的装置，其中，所述获取模块包括：第一获取子模块，设置为按照所述预设时间周期获取操作系统进程的系统资源申请量，将所述操作系统进程的系统资源申请量作为所述网管系统进程的系统资源申请量，其中，所述操作系统进程是与所述网管系统进程对应的。
- 根据权利要求9所述的装置，所述装置还包括：更新模块，设置为在重新启动所述网管系统进程之后，更新与所述网管系统进程对应的操作系统进程的标识，并建立所述网管系统进程与所述标识的对应关系。
- 根据权利要求8所述的装置，其中，所述判断模块包括：第一判断子模块，设置为判断所述网管系统进程的系统资源申请量是否达到预设门限；第二判断子模块，设置为判断所述预设时间周期内所述网管系统进程的系统资源申请量的增长量是否达到预设增长量。
- 根据权利要求8所述的装置，其中，所述重启模块包括：第一重启子模块模块，设置为关闭所述网管系统进程，并加载所述网管 系统进程对应的信息。
- 根据权利要求12所述的装置，其中，所述网管系统进程对应的信息包括：所述网管系统进程的标识、所述网管系统进程的可执行文件、所述网管系统进程的启动信息以及所述网管系统进程对应的系统资源门限。
- 根据权利要求8所述的装置，其中，所述重启模块还包括：第二重启子模块，设置为在与所述网管系统进程所对应的网管系统的空闲时段重新启动所述网管系统进程。
- 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令被处理器执行时实现权利要求1至8任一项所述的网管系统中进程的恢复方法。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510362547.0 | 2015-06-26 | ||
| CN201510362547.0A CN106294059A (zh) | 2015-06-26 | 2015-06-26 | 网管系统中进程的恢复方法及装置 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2016206501A1 true WO2016206501A1 (zh) | 2016-12-29 |
Family
ID=57584494
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2016/082257 WO2016206501A1 (zh) | 2015-06-26 | 2016-05-16 | 一种网管系统中进程的恢复方法、装置和计算机可读存储介质 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN106294059A (zh) |
| WO (1) | WO2016206501A1 (zh) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112925615A (zh) * | 2019-12-06 | 2021-06-08 | 烽火通信科技股份有限公司 | 一种进程恢复方法及系统 |
| CN112463358A (zh) * | 2020-10-29 | 2021-03-09 | 北京罗克维尔斯科技有限公司 | 内存管理方法、装置、车载系统以及车辆 |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH09247148A (ja) * | 1996-03-08 | 1997-09-19 | Nec Corp | ネットワーク管理システム |
| US5751963A (en) * | 1996-03-29 | 1998-05-12 | Mitsubishi Denki Kabushiki Kaisha | Hierarchical network management system operating as a proxy agent for enhancing processing efficiency |
| CN101103335A (zh) * | 2005-03-28 | 2008-01-09 | 三菱电机株式会社 | 应用管理装置和存放其软件的存储媒体 |
| CN103810048A (zh) * | 2014-03-11 | 2014-05-21 | 国家电网公司 | 一种面向资源利用最优的线程数量自动调整方法及装置 |
| CN104598368A (zh) * | 2014-12-22 | 2015-05-06 | 浙江大学 | 一种移动终端性能诊断方法 |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100504807C (zh) * | 2006-10-13 | 2009-06-24 | 中兴通讯股份有限公司 | 一种通信设备系统中内存泄漏的检测方法 |
| CN101908018B (zh) * | 2010-07-20 | 2012-09-26 | 北京海泰方圆科技有限公司 | 一种判断内存泄露的系统及方法 |
| CN102999427B (zh) * | 2011-09-19 | 2015-06-17 | 汉王科技股份有限公司 | 内存空洞检测和清除的方法和装置 |
| CN103425592B (zh) * | 2013-08-05 | 2016-08-10 | 大唐移动通信设备有限公司 | 一种多进程系统中的内存管理方法及装置 |
| CN104503828B (zh) * | 2014-12-12 | 2018-12-11 | 广东欧珀移动通信有限公司 | 一种进程管理方法及终端 |
| CN104731683B (zh) * | 2015-03-10 | 2018-02-13 | 惠州Tcl移动通信有限公司 | 一种手机内存监控的方法及系统 |
-
2015
- 2015-06-26 CN CN201510362547.0A patent/CN106294059A/zh active Pending
-
2016
- 2016-05-16 WO PCT/CN2016/082257 patent/WO2016206501A1/zh active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH09247148A (ja) * | 1996-03-08 | 1997-09-19 | Nec Corp | ネットワーク管理システム |
| US5751963A (en) * | 1996-03-29 | 1998-05-12 | Mitsubishi Denki Kabushiki Kaisha | Hierarchical network management system operating as a proxy agent for enhancing processing efficiency |
| CN101103335A (zh) * | 2005-03-28 | 2008-01-09 | 三菱电机株式会社 | 应用管理装置和存放其软件的存储媒体 |
| CN103810048A (zh) * | 2014-03-11 | 2014-05-21 | 国家电网公司 | 一种面向资源利用最优的线程数量自动调整方法及装置 |
| CN104598368A (zh) * | 2014-12-22 | 2015-05-06 | 浙江大学 | 一种移动终端性能诊断方法 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106294059A (zh) | 2017-01-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10511480B2 (en) | Message flow management for virtual networks | |
| CN108132837B (zh) | 一种分布式集群调度系统及方法 | |
| GB2505644A (en) | Managing network configurations | |
| CN109656742B (zh) | 一种节点异常处理方法、装置及存储介质 | |
| US20190036798A1 (en) | Method and apparatus for node processing in distributed system | |
| WO2018019242A1 (zh) | 网站服务器的自恢复方法和自恢复系统 | |
| CN110830283A (zh) | 故障检测方法、装置、设备和系统 | |
| CN109639818B (zh) | 一种云环境下的服务发现方法、装置、服务器和存储介质 | |
| WO2016045439A1 (zh) | 一种vnfm容灾保护的方法、装置和nfvo、存储介质 | |
| US10942831B2 (en) | Automating and monitoring rolling cluster reboots | |
| WO2018001046A1 (zh) | 智能网业务的恢复方法、装置及系统 | |
| CN110618864A (zh) | 一种中断任务恢复方法及装置 | |
| WO2019019457A1 (zh) | 控制中心装置、业务系统处理的方法、系统及存储介质 | |
| CN107729213B (zh) | 一种后台任务监控方法及装置 | |
| US20130326261A1 (en) | Failover of interrelated services on multiple devices | |
| WO2016206501A1 (zh) | 一种网管系统中进程的恢复方法、装置和计算机可读存储介质 | |
| CN107508700B (zh) | 容灾方法、装置、设备及存储介质 | |
| EP2110748A2 (en) | Cluster control apparatus, control system, control method, and control program | |
| JP6421516B2 (ja) | サーバ装置、冗長構成サーバシステム、情報引継プログラム及び情報引継方法 | |
| CN110620798A (zh) | Ftp连接的控制方法、系统、设备和存储介质 | |
| CN106897128B (zh) | 一种分布式应用退出方法、系统以及服务器 | |
| CN110555009B (zh) | 一种网络文件系统nfs服务的处理方法及装置 | |
| CN111309456B (zh) | 一种任务执行方法及系统 | |
| US20150244780A1 (en) | System, method and computing apparatus to manage process in cloud infrastructure | |
| US20240012632A1 (en) | Coordinating updates to an agent platform appliance in which agents of cloud services are deployed |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 16813617 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 16813617 Country of ref document: EP Kind code of ref document: A1 |