CN108595247B - Detection method, device and equipment - Google Patents
Detection method, device and equipment Download PDFInfo
- Publication number
- CN108595247B CN108595247B CN201810271370.7A CN201810271370A CN108595247B CN 108595247 B CN108595247 B CN 108595247B CN 201810271370 A CN201810271370 A CN 201810271370A CN 108595247 B CN108595247 B CN 108595247B
- Authority
- CN
- China
- Prior art keywords
- detection
- item
- application
- detected
- dependency
- 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.)
- Active
Links
Images
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
- 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
- G06F2009/45591—Monitoring or debugging support
Abstract
The specification discloses a detection method, a device and equipment, wherein the method divides all functions depended by an application into a strong dependence item and a weak dependence item, when the strong dependence item is detected to be passed, the application is prohibited from starting so as to prohibit an RS where the application is located from being mounted to an LVS, when the strong dependence item is detected to be passed and the weak dependence item is not passed, the application is indicated to have only slight defects at the moment, but the application is still usable as a whole, so that the application can be permitted to start so as to permit the RS to be mounted to the LVS, and the application is appropriately adjusted. Therefore, the reliability of the application is ensured, and the flexibility of detection is improved.
Description
Technical Field
The present disclosure relates to the field of computer technologies, and in particular, to a detection method, device, and apparatus.
Background
Currently, a method of providing a service using a Linux Virtual Server (LVS) is widely used, as shown in fig. 1.
Fig. 1 is a diagram of a network architecture for providing services using LVS. In fig. 1, an application for providing a service is installed on a Real Server (RS), when the application is started, the RS is mounted on an LVS, the LVS receives a request sent from an external device, distributes the request to each RS mounted on the LVS, and the RS processes the request, and returns a processing result to the external device through the LVS, that is, the LVS provides the service to the external device.
With the refinement of services, devices supporting different services are often physically isolated, for example, in fig. 1, the devices supporting different services are respectively placed in different rooms, each room provides services to the outside through its own LVS, and the RS of each room is mounted on its own LVS.
Because the service provided by one application often depends on a plurality of services, the premise that the application can normally provide the service is that the rooms in which the services are located can normally communicate with each other, and the equipment in the rooms has normal functions.
In order to ensure the reliability of an application, in the prior art, the LVS generally detects the application (for example, whether a port on which the RS is mounted to the LVS is available or not, or other network conditions of the RS, etc.), but the detection performed by the LVS is too limited and lacks flexibility, and therefore, a detection method is needed to improve the flexibility of the detection on the premise of ensuring the reliability of the application.
Disclosure of Invention
The specification provides a detection method, a detection device and detection equipment, which are used for solving the problems that detection performed by an LVS in the prior art is too limited and lacks flexibility.
The present specification provides a detection method comprising:
judging whether to trigger the detection of the application;
if the detection of the application is triggered, detecting a strong dependency item and a weak dependency item according to the strong dependency item and the weak dependency item which are preset for the application;
when the strong dependency item is detected to be passed and the weak dependency item is detected to be failed, allowing the application to be started so that a real server RS where the application is located is mounted on a Linux virtual server LVS, and adjusting the application according to the weak dependency item which is not detected to be passed;
and when the strong dependence item is not detected, prohibiting the application from starting so as to prohibit the RS from being mounted on the LVS.
This specification provides a detection apparatus, on which is installed an application, the apparatus comprising:
the judging module is used for judging whether to trigger the detection of the application;
the detection module is used for detecting a strong dependency item and a weak dependency item according to the strong dependency item and the weak dependency item which are preset aiming at the application if the judgment module determines to trigger the detection of the application;
the starting module allows the application to be started when the detection module passes the detection of the strong dependency item and fails to pass the detection of the weak dependency item, so that the device is mounted on a Linux Virtual Server (LVS), and the application is adjusted according to the weak dependency item which is not detected; and when the detection module fails to detect the strong dependence item, prohibiting the application from starting so as to prohibit the device from being mounted on the LVS.
The present specification provides a detection device having an application installed thereon, the device comprising one or more memories and a processor, the memories storing a program and configured to perform the following steps by the one or more processors:
judging whether to trigger the detection of the application;
if the detection of the application is triggered, detecting a strong dependency item and a weak dependency item according to the strong dependency item and the weak dependency item which are preset for the application;
when the strong dependency item is detected to be passed and the weak dependency item is detected to be failed, allowing the application to be started so that the equipment is mounted on a Linux Virtual Server (LVS), and adjusting the application according to the weak dependency item which is not detected to be passed;
and when the strong dependence item is not detected, prohibiting the application from starting so as to prohibit the equipment from being mounted on the LVS.
The technical scheme adopted by the specification can achieve the following beneficial effects:
compared with the method that the LVS only detects the network condition of the RS in the prior art, all functions on which the application depends are divided into a strong dependence item and a weak dependence item, when the strong dependence item is not detected, the application is prohibited from starting to prohibit the RS where the application is located from being mounted to the LVS, when the strong dependence item is detected and the weak dependence item is not passed, the application is indicated that only slight defects possibly exist at the moment, but the application is still usable as a whole, so that the application can be permitted to start to permit the RS to be mounted to the LVS, and the application is appropriately adjusted. Therefore, the reliability of the application is ensured, and the flexibility of detection is improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the specification and are incorporated in and constitute a part of this specification, illustrate embodiments of the specification and together with the description serve to explain the specification and not to limit the specification in a non-limiting sense. In the drawings:
FIG. 1 is a diagram of a network architecture for providing services using LVS;
FIG. 2 is a schematic diagram of the detection process provided herein;
FIG. 3 is a schematic diagram of the various test items relied upon by the application provided herein;
FIG. 4 is a detailed flow diagram for detecting strongly dependent items and weakly dependent items provided herein;
FIG. 5 is a schematic structural diagram of a detection device provided in the present specification;
fig. 6 is a schematic structural diagram of a detection apparatus provided in this specification.
Detailed Description
At present, the method for detecting an application by an LVS is to detect only a network condition of an RS where the application is located, for example, whether a port where the RS is mounted to the LVS is available is detected, but the availability of the port does not mean that the application is certainly available, and the application can normally provide services depending on the network condition, processes and connection numbers of the application on the RS, services of other rooms, and the like. Therefore, the present specification divides all functions on which an application depends into a strong dependency and a weak dependency, prohibits the application from starting if the strong dependency does not detect a pass, and permits the starting if the strong dependency does detect a pass and the weak dependency does not detect a pass, and can appropriately adjust the application.
In order to make those skilled in the art better understand the technical solutions in one or more embodiments of the present disclosure, the technical solutions in one or more embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in one or more embodiments of the present disclosure, and it is obvious that the described embodiments are only a part of the embodiments of the present disclosure, and not all embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step should fall within the scope of protection of the present specification.
Fig. 2 is a schematic view of a detection process provided in the present specification, which specifically includes the following steps:
s200: and judging whether the detection of the application is triggered, if so, executing the step S202, otherwise, returning to the step S200.
In this specification, an application is installed on an RS, the same application may be installed on multiple RSs, the RS may be installed on an LVS, the LVS provides services to the outside, when a certain RS is prohibited from being started or shielded by the LVS, the same application installed on other RSs can still provide services through the LVS, one room is provided with one LVS and multiple RSs, if the service provided by the application depends on other services, the room communication needs to be performed through the LVS, when one RS communicates with the RSs of other rooms, the RS can directly access the LVS of other rooms, and does not need to access through the LVS where its own room is located, which is the same as the network architecture shown in fig. 1.
For an application installed on the RS, the main body for detecting the application may be another application installed on the RS, or may be a plug-in or a functional module carried in the application.
In this specification, a method of determining whether to trigger detection of an application may specifically be that, when a start instruction for starting the application is received, the detection of the application is triggered. Of course, the method for triggering detection may also be other methods, for example, when the specified function of the application is triggered, the detection of the application is triggered, or when a preset detection time comes, the detection of the application is triggered, which is not limited in this application.
S202: and detecting the strong dependence items and the weak dependence items according to the strong dependence items and the weak dependence items which are set for the application in advance.
In this specification, all functions on which one application can normally provide a service are classified into strong dependencies and weak dependencies.
The strong dependency term refers to a plurality of detection terms which have a large influence on whether the application can provide the service, and if any one detection term is abnormal, the application cannot provide the service. For example, the plurality of detection items included in the strong dependency item may specifically be: whether the port of the RS where the application is mounted on the LVS is available or not or other network conditions of the RS, whether the process of the application on the RS is normal or not, whether the number of connections which can be provided by the RS is within a specified range or not and the like.
The weak dependency item refers to a plurality of detection items with small influence on whether the application can provide the service, and if any one or more detection items are abnormal, the application can still provide part of the service. For example, the plurality of detection items included in the weak dependency item may specifically be: whether the soft load addresses required to be accessed by the application can be subscribed, whether the RS where the application is located receives heartbeat responses of all other RSs, whether all protocol functions supported by the application are normal and the like. Obviously, the soft payload address that the application needs to access cannot be fully subscribed to, but can be only subscribed to one part, and the application can still provide services to the outside, so that the soft payload address is a weak dependency item. Of course, if all the soft load addresses cannot be subscribed to, it is likely that the communication between the RS and another server for providing the soft load addresses is not normal, and this is a strong dependency, as shown in fig. 3.
When detecting the strong dependency item and the weak dependency item, the strong dependency item can be preferentially detected, if the strong dependency item is not detected, the weak dependency item does not need to be detected, step S208 is directly executed, and if the strong dependency item is detected, the weak dependency item can be continuously detected. When detecting the strong dependence items, if the detection of all detection items contained in the strong dependence items passes, the detection of the strong dependence items can be determined to pass, and if at least one detection item does not pass, the detection of the strong dependence items is determined to not pass. Similarly, when the weak dependency is detected, if the detection of all the detection items included in the weak dependency passes, it is determined that the detection of the weak dependency passes, and if at least one detection item does not pass, it is determined that the detection of the weak dependency does not pass.
S204: and when the strong dependency item and the weak dependency item are detected to be passed, allowing the application to be started so as to mount the RS where the application is located on the LVS.
S206: and when the strong dependency item is detected to be passed and the weak dependency item is detected to be failed, allowing the application to be started so that the real server RS where the application is located is mounted on the Linux virtual server LVS, and adjusting the application according to the weak dependency item which is not detected to be passed.
S208: and when the strong dependence item is not detected, prohibiting the application from starting so as to prohibit the RS from being mounted on the LVS.
It can be known from the definitions of the strong dependency and the weak dependency that the application cannot provide the service when the strong dependency fails to be detected, and the application can still provide part of the service when the strong dependency passes but the weak dependency fails to be detected, so that if both pass, the application can be directly allowed to start, so that the RS where the application is located is mounted on the LVS. If the strong dependency detection passes but the weak dependency detection does not pass, the application is also allowed to be started so that the RS where the application is located is mounted on the LVS, and the application can be adjusted according to the weak dependency that the detection does not pass, specifically, the configuration parameters of the application and/or the RS where the application is located, and the like can be adjusted. E.g., adjusting the priority of the application, adjusting the priority of the RS in which the application resides, etc. If the strong dependency item is not detected, the application is prohibited from starting regardless of whether the weak dependency item is detected, so that the application is prohibited from being installed on the LVS of the RS.
Further, since it may be necessary to start the application (for example, to detect whether the process of the application on the RS is normal or not) and then perform detection when detecting the strong dependency and the weak dependency of the application, when the strong dependency cannot be detected, the method for prohibiting the application from starting may specifically be: the application is forced to close so that the LVS masks the RS where the application is located.
Because some functions that the application depends on may not be started immediately when the application is started to be detected, but may be started later, in order to improve the accuracy of detection, a method of detecting multiple times is adopted in this specification, and specifically, each detection item included in the strongly dependent item is detected; if the detection item passes the detection, other detection items included by the strong dependence item are continuously detected; if the detection item is not detected, judging whether the detection frequency of the detection item reaches a threshold value, if so, determining that the detection item is not detected, if not, detecting the detection item again until the detection item passes the detection or the detection frequency of the detection item reaches the threshold value.
Similarly, for each detection item included in the weak dependence item, the detection item is detected; if the detection item passes the detection, other detection items included by the weak dependence item are continuously detected; if the detection item is not detected, judging whether the detection frequency of the detection item reaches a threshold value, if so, determining that the detection item is not detected, if not, detecting the detection item again until the detection item passes the detection or the detection frequency of the detection item reaches the threshold value.
The threshold value can be set as required, for example, to 30. That is, for any detection item included in the strongly dependent item or the weakly dependent item, if there is one pass within 30 detections, the detection item is considered to pass the detection, and if there is no pass in 30 detections, the detection item is considered to fail the detection.
Considering the principle of preferentially detecting strong dependencies, the specific method for detecting both weak and future dependencies in this specification can be as shown in fig. 4.
Based on the same idea, the detection method provided for one or more embodiments of the present specification further provides a corresponding detection device, as shown in fig. 5.
An application is installed on the device;
a judging module 501, configured to judge whether to trigger detection of an application;
a detection module 502, configured to detect a strong dependency item and a weak dependency item according to the strong dependency item and the weak dependency item preset for the application if the determination module 501 determines to trigger the detection of the application;
a starting module 503, configured to allow the application to be started when the detection module 502 passes the detection on the strong dependency item and fails to pass the detection on the weak dependency item, so that the device is mounted on the Linux virtual server LVS, and adjust the application according to the weak dependency item that is not detected; when the detection module 502 fails to detect the strong dependency, the application is prohibited from starting to prohibit the device from being mounted on an LVS.
The determining module 501 is specifically configured to determine to trigger detection of an application when a start instruction for starting the application is received.
The detecting module 502 is specifically configured to preferentially detect the strong dependency; and if the strong dependence item passes the detection, detecting the weak dependence item.
The strong dependence item comprises a plurality of detection items; the weak dependency term comprises a plurality of detection terms;
the detecting module 502 is specifically configured to determine that the detection on the strong dependency item passes when all detection items included in the strong dependency item pass; when at least one detection item included in the strong dependence item is detected to be failed, determining that the detection to the strong dependence item is failed; and when at least one detection item included in the weak dependency item is detected to be failed, determining that the weak dependency item is detected to be failed.
The detecting module 502 is specifically configured to, for each detection item included in the strongly dependent item, detect the detection item; if the detection item passes the detection, other detection items included by the strong dependence item are continuously detected; if the detection item is not detected, judging whether the detection frequency of the detection item reaches a threshold value, if so, determining that the detection item is not detected, if not, detecting the detection item again until the detection item passes the detection or the detection frequency of the detection item reaches the threshold value.
The detecting module 502 is specifically configured to, for each detection item included in the weak dependency item, detect the detection item; if the detection item passes the detection, other detection items included by the weak dependence item are continuously detected; if the detection item is not detected, judging whether the detection frequency of the detection item reaches a threshold value, if so, determining that the detection item is not detected, if not, detecting the detection item again until the detection item passes the detection or the detection frequency of the detection item reaches the threshold value.
The specification also correspondingly provides a detection device, as shown in fig. 6. The device having an application installed thereon, the device comprising one or more memories and a processor, the memories storing programs and configured to perform the following steps by the one or more processors:
judging whether to trigger the detection of the application;
if the detection of the application is triggered, detecting a strong dependency item and a weak dependency item according to the strong dependency item and the weak dependency item which are preset for the application;
when the strong dependency item is detected to be passed and the weak dependency item is detected to be failed, allowing the application to be started so that the equipment is mounted on a Linux Virtual Server (LVS), and adjusting the application according to the weak dependency item which is not detected to be passed;
and when the strong dependence item is not detected, prohibiting the application from starting so as to prohibit the equipment from being mounted on the LVS.
In the 90 s of the 20 th century, improvements in a technology could clearly distinguish between improvements in hardware (e.g., improvements in circuit structures such as diodes, transistors, switches, etc.) and improvements in software (improvements in process flow). However, as technology advances, many of today's process flow improvements have been seen as direct improvements in hardware circuit architecture. Designers almost always obtain the corresponding hardware circuit structure by programming an improved method flow into the hardware circuit. Thus, it cannot be said that an improvement in the process flow cannot be realized by hardware physical modules. For example, a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), is an integrated circuit whose Logic functions are determined by programming the Device by a user. A digital system is "integrated" on a PLD by the designer's own programming without requiring the chip manufacturer to design and fabricate application-specific integrated circuit chips. Furthermore, nowadays, instead of manually making an Integrated Circuit chip, such Programming is often implemented by "logic compiler" software, which is similar to a software compiler used in program development and writing, but the original code before compiling is also written by a specific Programming Language, which is called Hardware Description Language (HDL), and HDL is not only one but many, such as abel (advanced Boolean Expression Language), ahdl (alternate Hardware Description Language), traffic, pl (core universal Programming Language), HDCal (jhdware Description Language), lang, Lola, HDL, laspam, hardward Description Language (vhr Description Language), vhal (Hardware Description Language), and vhigh-Language, which are currently used in most common. It will also be apparent to those skilled in the art that hardware circuitry that implements the logical method flows can be readily obtained by merely slightly programming the method flows into an integrated circuit using the hardware description languages described above.
The controller may be implemented in any suitable manner, for example, the controller may take the form of, for example, a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro) processor, logic gates, switches, an Application Specific Integrated Circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, the memory controller may also be implemented as part of the control logic for the memory. Those skilled in the art will also appreciate that, in addition to implementing the controller as pure computer readable program code, the same functionality can be implemented by logically programming method steps such that the controller is in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers and the like. Such a controller may thus be considered a hardware component, and the means included therein for performing the various functions may also be considered as a structure within the hardware component. Or even means for performing the functions may be regarded as being both a software module for performing the method and a structure within a hardware component.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functions of the various elements may be implemented in the same one or more software and/or hardware implementations of the present description.
As will be appreciated by one skilled in the art, embodiments of the present description may be provided as a method, system, or computer program product. Accordingly, the description may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the description may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The description has been presented with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to one or more embodiments of the description. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
This description may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. One or more embodiments of the specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The above description is merely one or more embodiments of the present disclosure and is not intended to limit the present disclosure. Various modifications and alterations to one or more embodiments of the present description will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement or the like made within the spirit and principle of one or more embodiments of the present specification should be included in the scope of the claims of the present specification.
Claims (13)
1. A method of detection, comprising:
judging whether to trigger the detection of the application;
if the detection of the application is triggered, detecting a strong dependency item and a weak dependency item according to the strong dependency item and the weak dependency item which are preset for the application;
when the strong dependency item is detected to be passed and the weak dependency item is detected to be failed, allowing the application to be started so that a real server RS where the application is located is mounted on a Linux virtual server LVS, and adjusting the application according to the weak dependency item which is not detected to be passed;
when the strong dependence item is not detected, prohibiting the application from starting so as to prohibit the RS from being mounted on the LVS;
wherein the content of the first and second substances,
the strong dependence item is a plurality of detection items which have great influence on whether the application can provide the service, and if any detection item is abnormal, the application cannot provide the service;
the weak dependency item refers to a plurality of detection items which have small influence on whether the application can provide the service, and if any one or more detection items are abnormal, the application can still provide part of the service;
the detecting of the strong dependence item specifically includes:
all detection items included in the strongly dependent items are detected to pass;
the detecting the weak dependency does not pass, specifically comprising:
at least one detection item included in the weakly dependent item is not detected.
2. The method of claim 1, wherein determining whether to trigger the detection of the application comprises:
when a start instruction for starting an application is received, it is determined that detection of the application is triggered.
3. The method according to claim 1, wherein the detecting the strong dependency and the weak dependency specifically comprises:
preferentially detecting the strong dependence item;
and if the strong dependence item passes the detection, detecting the weak dependence item.
4. The method of any one of claims 1 to 3, wherein the strongly dependent term comprises a plurality of detection terms; the weak dependency term comprises a plurality of detection terms;
the detection of the strong dependence item does not pass, and specifically comprises the following steps:
at least one detection item included in the strongly dependent item is not detected.
5. The method according to claim 4, wherein the detecting the strong dependency specifically comprises:
for each detection item included in the strong dependence item, detecting the detection item;
if the detection item passes the detection, other detection items included by the strong dependence item are continuously detected;
if the detection item is not detected, judging whether the detection frequency of the detection item reaches a threshold value, if so, determining that the detection item is not detected, if not, detecting the detection item again until the detection item passes the detection or the detection frequency of the detection item reaches the threshold value.
6. The method of claim 4, wherein detecting the weak dependency comprises:
for each detection item included in the weak dependence item, detecting the detection item;
if the detection item passes the detection, other detection items included by the weak dependence item are continuously detected;
if the detection item is not detected, judging whether the detection frequency of the detection item reaches a threshold value, if so, determining that the detection item is not detected, if not, detecting the detection item again until the detection item passes the detection or the detection frequency of the detection item reaches the threshold value.
7. A detection device having an application installed thereon, the device comprising:
the judging module is used for judging whether to trigger the detection of the application;
the detection module is used for detecting a strong dependency item and a weak dependency item according to the strong dependency item and the weak dependency item which are preset aiming at the application if the judgment module determines to trigger the detection of the application;
the starting module allows the application to be started when the detection module passes the detection of the strong dependency item and fails to pass the detection of the weak dependency item, so that the device is mounted on a Linux Virtual Server (LVS), and the application is adjusted according to the weak dependency item which is not detected; when the detection module fails to detect the strong dependence item, prohibiting the application from starting so as to prohibit the device from being mounted on an LVS;
wherein the content of the first and second substances,
the strong dependence item is a plurality of detection items which have great influence on whether the application can provide the service, and if any detection item is abnormal, the application cannot provide the service;
the weak dependency item refers to a plurality of detection items which have small influence on whether the application can provide the service, and if any one or more detection items are abnormal, the application can still provide part of the service;
the detecting of the strong dependence item specifically includes:
all detection items included in the strongly dependent items are detected to pass;
the detecting the weak dependency does not pass, specifically comprising:
at least one detection item included in the weakly dependent item is not detected.
8. The apparatus according to claim 7, wherein the determining module is specifically configured to determine that the detection of the application is triggered when a start instruction for starting the application is received.
9. The apparatus of claim 7, the detection module is specifically configured to preferentially detect the strong dependency; and if the strong dependence item passes the detection, detecting the weak dependence item.
10. The apparatus of any one of claims 7 to 9, wherein the strongly dependent term comprises a plurality of detection terms; the weak dependency term comprises a plurality of detection terms;
the detection module is specifically configured to determine that the detection of the strongly dependent item fails when the detection of at least one detection item included in the strongly dependent item fails.
11. The apparatus according to claim 10, wherein the detecting module is specifically configured to, for each detection item included in the strongly dependent item, detect the detection item; if the detection item passes the detection, other detection items included by the strong dependence item are continuously detected; if the detection item is not detected, judging whether the detection frequency of the detection item reaches a threshold value, if so, determining that the detection item is not detected, if not, detecting the detection item again until the detection item passes the detection or the detection frequency of the detection item reaches the threshold value.
12. The apparatus of claim 10, the detection module being specifically configured to, for each detection item included in the weakly dependent item, detect the detection item; if the detection item passes the detection, other detection items included by the weak dependence item are continuously detected; if the detection item is not detected, judging whether the detection frequency of the detection item reaches a threshold value, if so, determining that the detection item is not detected, if not, detecting the detection item again until the detection item passes the detection or the detection frequency of the detection item reaches the threshold value.
13. A detection device having an application installed thereon, the device comprising one or more memories and a processor, the memories storing programs and configured to perform the following steps by the one or more processors:
judging whether to trigger the detection of the application;
if the detection of the application is triggered, detecting a strong dependency item and a weak dependency item according to the strong dependency item and the weak dependency item which are preset for the application;
when the strong dependency item is detected to be passed and the weak dependency item is detected to be failed, allowing the application to be started so that the equipment is mounted on a Linux Virtual Server (LVS), and adjusting the application according to the weak dependency item which is not detected to be passed;
when the strong dependence item is not detected, prohibiting the application from starting so as to prohibit the equipment from being mounted on the LVS;
wherein the content of the first and second substances,
the strong dependence item is a plurality of detection items which have great influence on whether the application can provide the service, and if any detection item is abnormal, the application cannot provide the service;
the weak dependency item refers to a plurality of detection items which have small influence on whether the application can provide the service, and if any one or more detection items are abnormal, the application can still provide part of the service;
the detecting of the strong dependence item specifically includes:
all detection items included in the strongly dependent items are detected to pass;
the detecting the weak dependency does not pass, specifically comprising:
at least one detection item included in the weakly dependent item is not detected.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810271370.7A CN108595247B (en) | 2018-03-29 | 2018-03-29 | Detection method, device and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810271370.7A CN108595247B (en) | 2018-03-29 | 2018-03-29 | Detection method, device and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108595247A CN108595247A (en) | 2018-09-28 |
| CN108595247B true CN108595247B (en) | 2021-10-29 |
Family
ID=63623833
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810271370.7A Active CN108595247B (en) | 2018-03-29 | 2018-03-29 | Detection method, device and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108595247B (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101561774A (en) * | 2009-03-31 | 2009-10-21 | 深圳创维数字技术股份有限公司 | Monitoring method and monitoring system of self-defined protocol service program |
| EP2701068A1 (en) * | 2011-04-19 | 2014-02-26 | Murakumo Corporation | Network access system |
| CN104038376A (en) * | 2014-06-30 | 2014-09-10 | 浪潮(北京)电子信息产业有限公司 | Method and device for managing real servers and LVS clustering system |
| CN104423944A (en) * | 2013-08-29 | 2015-03-18 | 中国银联股份有限公司 | Software application system |
| CN104993953A (en) * | 2015-06-19 | 2015-10-21 | 北京奇虎科技有限公司 | Method for detecting network service state and device detecting network service state |
| KR20160044623A (en) * | 2014-10-15 | 2016-04-26 | 극동대학교 산학협력단 | Load Balancing Method for a Linux Virtual Server |
| CN106100940A (en) * | 2016-08-25 | 2016-11-09 | 上海斐讯数据通信技术有限公司 | A kind of network message supervising device and monitoring method thereof |
-
2018
- 2018-03-29 CN CN201810271370.7A patent/CN108595247B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101561774A (en) * | 2009-03-31 | 2009-10-21 | 深圳创维数字技术股份有限公司 | Monitoring method and monitoring system of self-defined protocol service program |
| EP2701068A1 (en) * | 2011-04-19 | 2014-02-26 | Murakumo Corporation | Network access system |
| CN104423944A (en) * | 2013-08-29 | 2015-03-18 | 中国银联股份有限公司 | Software application system |
| CN104038376A (en) * | 2014-06-30 | 2014-09-10 | 浪潮(北京)电子信息产业有限公司 | Method and device for managing real servers and LVS clustering system |
| KR20160044623A (en) * | 2014-10-15 | 2016-04-26 | 극동대학교 산학협력단 | Load Balancing Method for a Linux Virtual Server |
| CN104993953A (en) * | 2015-06-19 | 2015-10-21 | 北京奇虎科技有限公司 | Method for detecting network service state and device detecting network service state |
| CN106100940A (en) * | 2016-08-25 | 2016-11-09 | 上海斐讯数据通信技术有限公司 | A kind of network message supervising device and monitoring method thereof |
Non-Patent Citations (2)
| Title |
|---|
| Construction and Application of Linux Virtual Server Cluster for Scientific Computing;Hong Tang 等;《2008 IFIP International Conference on Network and Parallel Computing》;20081031;287-289 * |
| 服务器负载均衡技术研究;周莹莲 等;《计算机与数字工程》;20101231;第38卷(第4期);11-14 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108595247A (en) | 2018-09-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11113387B2 (en) | Method and apparatus for improving security of Java sandbox | |
| CN112560022B (en) | Method and device for detecting system interface call | |
| US9582339B2 (en) | Operation of software modules in parallel | |
| CN108304313B (en) | Device, client and method for data testing | |
| CN108304455B (en) | Method, device and equipment for processing service request | |
| US10628188B2 (en) | Disabling just-in-time translation for application functions | |
| CN109144600B (en) | Application program running method and device and computer readable medium | |
| CN108595247B (en) | Detection method, device and equipment | |
| KR20180033512A (en) | Accidental load suppression | |
| CN109582388B (en) | Parameter configuration method, device and equipment | |
| CN110244964B (en) | Operation and maintenance method, device and equipment based on operation and maintenance application | |
| CN113556260A (en) | Flow monitoring method and device, storage medium and electronic equipment | |
| US20160357950A1 (en) | Methods for configuring security restrictions of a data processing system | |
| CN110275782B (en) | Data processing method and device | |
| CN108388982B (en) | Task running method and device and electronic equipment | |
| AU2017235993B2 (en) | Dynamic loading and deployment of test files to prevent interruption of test execution | |
| CN109558249B (en) | Control method and device for concurrent operation | |
| KR101858594B1 (en) | Method and apparatus for detecting anti-reversing code | |
| CN114840427A (en) | Code testing and test case generating method and device | |
| CN106203087B (en) | Injection protection method, system, terminal and storage medium | |
| CN109903165B (en) | Model merging method and device | |
| CN111078435A (en) | Service processing method and device and electronic equipment | |
| US10899199B2 (en) | Control method and system for air-conditioner water chilling units and air conditioning system | |
| CN115964264A (en) | Cheating application detection method and device | |
| CN108459879B (en) | Method for preventing terminal from crashing and terminal |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20201021 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Innovative advanced technology Co.,Ltd. Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant before: Advanced innovation technology Co.,Ltd. Effective date of registration: 20201021 Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands Applicant after: Advanced innovation technology Co.,Ltd. Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands Applicant before: Alibaba Group Holding Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |