EP1697846A2 - Einrichtung und verfahren zur steuerung und kontrolle von überwachungsdetektoren in einem knoten eines clustersystems - Google Patents
Einrichtung und verfahren zur steuerung und kontrolle von überwachungsdetektoren in einem knoten eines clustersystemsInfo
- Publication number
- EP1697846A2 EP1697846A2 EP04802700A EP04802700A EP1697846A2 EP 1697846 A2 EP1697846 A2 EP 1697846A2 EP 04802700 A EP04802700 A EP 04802700A EP 04802700 A EP04802700 A EP 04802700A EP 1697846 A2 EP1697846 A2 EP 1697846A2
- Authority
- EP
- European Patent Office
- Prior art keywords
- monitoring
- monitored
- resource
- detector
- resources
- 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.)
- Withdrawn
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3466—Performance evaluation by tracing or monitoring
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/34—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment
- G06F11/3409—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment
- G06F11/3433—Recording or statistical evaluation of computer activity, e.g. of down time, of input/output operation ; Recording or statistical evaluation of user activity, e.g. usability assessment for performance assessment for load management
Definitions
- the invention relates to a device in a node of a cluster system for checking and controlling monitoring detectors.
- the invention further relates to a method for the control and monitoring of monitoring detectors for at least two resources to be monitored in a cluster system.
- Cluster systems with multiple nodes within the cluster are often used for software that is said to be highly available.
- the cluster system has control and control software, which is also called Reliant Management Service RMS and which aHif monitors the highly available software that is running for the cluster. »The highly available software itself runs on one node of a cluster or is distributed among different nodes.
- the control software RMS can also be distributed across various nodes, ie in a decentralized manner.
- the control software RMS ends the application or the corresponding part of it and restarts it on another node.
- the RM service controlled so-called monitoring detectors monitor the highly available application or a part of the highly available application. These each monitor a specific part of the application, which is referred to as a resource, and report the status of the resource back to the RMS control software.
- FIG. 6 This shows a node N1, which is part of a cluster system.
- the knot Nl contains the Reliant Management Service RMS as control software.
- the highly available application APL is executed on the node N1, which in turn exchanges data with a memory management system FS via the connection C1.
- the RMS control software starts the individual monitoring detectors D1, D2 and D3.
- Each of these detectors is specially designed to monitor a specific resource of the highly available software APL.
- the detector D3 monitors the communication link C1 between the application APL and the file management system FS.
- Another detector D2 checks the highly available application APL on the basis of continuous queries as to whether it is still being executed and whether it is providing feedback.
- the third detector Dl checks, for example, the available temporary memory that is required for the highly available application APL.
- the RMS control takes suitable measures in the event of a failure of individual resources monitored by the monitoring detectors or other problems that occur. For example, it can terminate the highly available software and restart it on a second node (not shown).
- the individual monitoring detectors are started independently of each other by the RMS control software. However, this leads to a high system load on the node, since the individual detectors correspondingly consume memory space or computing capacity. In the worst case, due to an unfavorable configuration or a large number of monitored resources within a node, the monitoring detectors can consume most of the available computing capacity. There is then too little available for the actual application.
- the control software receives status messages from monitoring detectors whose actual execution and monitoring of the resource is not currently necessary. dig is. The processing of all returned status messages also increases the computing time and places an unnecessary burden on the control software.
- the object of the invention is therefore to provide a device in a node of a cluster system, with which the system load for the monitoring for mission-dependent requirements is adapted, but adequate monitoring of the resources is nevertheless ensured. It is also an object to provide a method for the control and monitoring of monitoring detectors which works efficiently with a low system load.
- a monitoring device is provided in a node of a cluster system for monitoring at least two resources to be monitored on the node of the cluster system.
- a priority can be assigned to the resources to be monitored, which represents a measure of the importance of the resource to be monitored.
- the device comprises a means for selecting a resource from the at least two resources to be monitored on the basis of the priorities assigned to the resources to be monitored.
- the device comprises at least one monitoring detector which is designed for the type of monitoring of the resource to be monitored.
- the device contains a means for assigning the monitoring detector to the resource to be monitored, and a means for executing the monitoring detector. This is designed in such a way that after a one-time monitoring of the resource by the monitoring detector carried out, the execution is ended or stopped by the means.
- the device forms a higher-level instance to which the individual resources to be monitored and in particular the monitoring detectors required for the resources to be monitored are subordinate.
- the execution of the individual monitoring detectors required for the resources to be monitored is no longer independent of one another, but is controlled in a combined manner by the device. This makes it possible to use the device to monitor only those resources whose monitoring is necessary at the current time.
- the device on the node also saves additional computing time, since the monitoring detector required for the resource to be monitored is only executed after a selection.
- the monitoring is carried out in such a way that the execution of the monitoring detector is stopped again after the monitoring has taken place. Monitoring is therefore only once.
- the device is, of course, designed in such a way that, if necessary, it also frequently selects the resource to be monitored and executes the monitoring detector required for this several times.
- the monitoring detector is not operated continuously, but is only executed until it has returned a status message regarding the resource to be monitored.
- the monitoring detector itself can be designed for repeated monitoring. This is particularly advantageous in the case of scattering measured values from the monitoring detector.
- the monitoring detector carries out several monitoring operations and then returns an entire status message which represents the individual measured values. The execution of the detector is ended after the status message has been transmitted.
- the method for monitoring at least two resources on a node of a cluster system comprises the steps: a) selection of one of the at least two resources to be monitored on the basis of the priority assigned to the resources to be monitored; b) selection of a monitoring detector required for the monitoring for the resource to be monitored; c) assigning resource parameters to the monitoring detector; d) starting or executing the monitoring detector and performing a monitoring of the resource once by the monitoring detector; e) reporting the result of the monitoring performed by the monitoring detector.
- monitoring of a resource to be monitored is not carried out continuously, but rather only by executing the monitoring detector assigned to the resource to be monitored once.
- the monitoring detector itself can of course monitor the resource to be monitored in a variety of ways and in particular also several times at short time intervals before it returns a result.
- only one result or status message is returned once per execution of the monitoring detector.
- the resource to be monitored at a time is selected based on the assigned priority. This saves computing time on the node of a cluster system, since the monitoring detector is only executed when this is necessary based on the assigned priority. In particular, the resources and the monitoring detectors are combined and viewed as a whole. Individual detectors are therefore no longer independent.
- a resource to be monitored is identified by an integration point within a file system of the Cluster system node.
- the monitoring detector is thus designed to check whether the integration point to be monitored is still valid.
- the integration point is provided by a second file system on a mass storage device, which is integrated in the file system of the node of the cluster system.
- the correct monitoring detector required for monitoring the resource is always selected based on the selected resource.
- the monitoring detector is designed to monitor an available hard disk or other mass storage.
- the resource to be monitored is an executed program and the monitoring detector required for this is a detector that checks whether the executed program is still active.
- Another resource to be monitored is a network connection with another node of the cluster system.
- the monitoring detector required for this is a detector that checks the status of the network connection.
- Another resource is a database to be monitored, the system load of the node, the processor load of a program being executed, or the free space available within the node of the cluster system.
- a monitoring detector is provided for each type of different resource, which performs a specific monitoring. There can be several different types of monitoring for a resource and therefore different monitoring detectors.
- the means for selection comprises a list in which the at least two resources to be monitored are stored in an order determined by their priority. This enables a particularly simple selection of the resource to be monitored by the device using the list of the resources to be monitored determined and executes the monitoring detectors.
- the list can be changed particularly easily by adding additional resources or removing resources from the list.
- the device is designed in such a way that, based on a resource selected from the list, it automatically provides the associated monitoring detector required for monitoring the resource.
- a fixed period of time is provided per time interval.
- the device is designed in such a way that the average time for executing a monitoring detector is less than the defined time period.
- the device is expediently designed for a selection of a resource and for a single execution of the assigned monitoring detector, until the total execution time of all the monitoring detectors executed once reaches the defined time period.
- This fixed time period therefore specifies a time window in each time interval in which the device can monitor resources. In other words, the maximum computing capacity or computing time required by the device can thus be determined within a time interval. This is possible because the monitoring detectors are started and controlled by the device and are consequently no longer independent of one another.
- a further development of the invention is characterized in that a second time period, which is required for monitoring the resource, is assigned to the resource to be monitored. This enables the facility to provide an accurate Make an estimate of the time required for monitoring. It is expedient if the device is designed to determine the period of time required for monitoring. This is expediently carried out by measuring the time on the monitoring detector.
- the device has a first interface, which is designed to emit status messages from the monitoring detector after the monitoring detector has been executed once. This allows important status messages to be reported to a higher-level control and control device in particular.
- the device comprises a second interface, which is designed to receive user commands. As a result, it is also possible for the user to monitor a resource at any time using a monitoring detector. This is particularly useful if a current status message is required by the resource to be monitored.
- the first or the second interface can be designed to receive resources to be monitored. In this way, new resources to be monitored can be communicated to the device or resources monitored by the device can be removed from the monitoring again.
- the device it is expedient to design the device as an independent process within the node of the cluster system.
- the facility thus forms an independent program.
- the monitoring detectors form sub-processes of the device during their execution.
- the monitoring detector is designed as an independently executable program. This is carried out once by the facility after selection of the resource to be monitored.
- the device has at least one idle subprocess which is executed on the node of the cluster system but is independent of the resource to be monitored.
- the means for executing the monitoring detector is designed to link the monitoring detector of the selected resource to be monitored with the independent sub-process. This development is particularly advantageous if the monitoring detector is designed as a function of a dynamic library or as a dynamic library.
- the device links the function of the dynamic library or the dynamic library at the time of execution to the idle subprocess, starts it and thus monitors the resource to be monitored. After the execution, the link is released.
- Such training is particularly speed and computing efficient.
- the monitoring detectors as functions in dynamic libraries or as dynamic libraries, improvements, extensions or error corrections are possible in a particularly simple and flexible manner. It also simplifies porting to other cluster operating systems.
- a first time period is defined in a time interval for the monitoring of the resources to be monitored. Monitoring detectors and the associated sub-processes are only executed as long as the specified time period is not exceeded. The process can be repeated until the specified time is reached.
- the first time period in the time interval thus defines a maximum computing capacity that is required for monitoring. It is expedient to select at least one of the two resources to be monitored from a list in which the resources to be monitored are stored in the order of their priorities. In a further training, the list is worked through until the specified period of time is reached.
- a resource to be monitored a second period of time, which specifies the duration for monitoring by the monitoring detector.
- the second time period can also be assigned to the monitoring detector.
- the second time period for monitoring is determined by the execution of the selected monitoring detector. This is particularly useful if the required period of time is not known from the outset or if parameters change during operation that affect the period of time for monitoring.
- an idle sub-process is started that does not consume any computing time and is also referred to as a sleeping process.
- the monitoring detector is linked to the idling sub-process and then executed. It is expedient to design the monitoring detector as a function of a dynamic library or as a dynamic library. Linking the monitoring detector to the idling sub-process is particularly quick as a result and efficient. After the result has been reported by the monitoring detector, the link is broken again and the idle process is put back to sleep. The idle process does not require any computing time on the node.
- the idling sub-process can be linked in succession with various monitoring detectors. Training on an idle sub-process is particularly flexible.
- FIG. 1 shows an exemplary embodiment of the device according to the invention
- FIG. 2 shows a diagram of the means for execution in the device
- FIG. 3 shows a schematic sequence
- FIG. 4 examples of resources within the cluster system
- FIG. 5 shows a chronological sequence of the resources to be monitored
- Figure ⁇ a known device with surveillance detectors.
- FIG. 4 shows two nodes C and C2 in a cluster system. These are interconnected via a network connection Nl.
- a highly available application APL is executed on the node C, which contains several resources to be monitored.
- the Reliant Management Service RMS is also executed on node C. This is a control and control software that is intended to monitor the high availability of the APL application. If necessary, it takes additional measures to ensure high availability. To do this, it is necessary to monitor the individual resources of the highly available APL application.
- the resources are two integration nodes within the file system of node C. These point to two external mass storage devices M1 and M2, which are designed as simple hard disk memories in this exemplary embodiment.
- the hard disk space Ml is mounted in the file system of the node C in the integration point "/ usr / opt", the hard disk space M2 in the integration point "/ usr / share”. It is necessary to check whether the mass storage devices M1 and M2 attached to these points in the file system are functional and whether data can be read from them or written to them.
- the highly available application APL accesses the database DB, which is executed on node C2. To do this, it is necessary to check the connection between the APL application on node C and the database DB on node C2. Finally, window manager X on node C is also monitored for the graphical user interface of the highly available application APL.
- a superordinate monitoring device DFW is provided for the monitoring of all these resources, which is connected to the Reliant Management Service RMS.
- the monitoring device DFW is also referred to as an instance or detector framework and is designed as an independent process on node C. Part of this facility are the detectors D1, D2, D3 and D4. These are responsible for the monitoring of resources and are controlled by the monitoring facility DFW.
- the resources to be monitored were transferred to the DFW instance by the Reliant Management Service RMS or communicated as parameters.
- FIG. 2 shows a more detailed block diagram of the monitoring device DFW according to the invention.
- the individual resources are monitored as in FIG. 4 by the individual detectors D1, D2, D3 and D4, which, however, are controlled by a control device KE. Like the detectors, this is part of the monitoring device and has further logic blocks which will be explained in detail later.
- the higher-level facility DFW is responsible for communication with the Reliant Management Service RMS via the interface Sl.
- it contains a control device KE, which receives information about the resources to be monitored from the system RMS. User data or user commands are also transferred to the control device KE via the interface S2.
- the control device KE controls and controls the individual monitoring detectors D1, D2, D3 and D4.
- the individual detectors are implemented by dynamic libraries Y.so, Z.so and X.so, which are started at runtime.
- the dynamic library Y.so contains all functions that are necessary for monitoring an integration point within the file system, ie to recognize that the two monitoring detectors D1 and D2 are implemented by the same library Y.so.
- the monitoring detectors even represent the same function in the Y.so library.
- the control device KE performs the function for monitoring in the dynamic library Y.so together with a set of parameters when the integration point of the mass storage devices M1 or M2 is monitored.
- the two monitoring detectors D1 and D2 thus contain the same function at runtime, but different parameters transferred to the function.
- the parameters for the detector Dl contain the information for monitoring the memory Ml, the parameters that were used for the detector D2 contain the necessary information for checking the mass memory M2.
- the set of parameters passed is the integration point in the file system for the memories M1 and M2 and, for example, the type of access right to be checked.
- the dynamic library Z.so contains all the necessary functions for monitoring the database connection DB between the node C and the node C2 in FIG. If a check is required, the control device KE starts the function from the dynamic library Z.so.
- the last dynamic library X contains the functions for the monitoring detector D4, which checks the status of the window manager for the graphical user interface.
- the instance DFW also provides a set of functions that can be used in common for all individual detectors. For example, this is the interface to the Reliant Management System RMS for the status messages, which are the same for all detectors.
- the execution of the individual monitoring detectors D1 to D4 is controlled and monitored by the control device KE.
- the monitoring detectors are thus completely embedded in the detector framework DFW and are no longer independent of this.
- Figure 1 explains in detail the structure of the control device KE, which in turn contains various devices or means.
- the figure shows a first list with the resources M1, DB and X to be monitored, the type of monitoring of the control device KE is known.
- the resources were communicated to the Detector Framework DFW by the Relian Management Service with the order for monitoring.
- the list contains all the information necessary for monitoring.
- a selection device KE1 is now provided, which selects one from the list of the resource to be monitored, in the exemplary embodiment the resource DB.
- the selection is based on a priority.
- other parameters for example the computing time previously used or the time required for monitoring, can also be taken into account.
- the selection means KE transfers the resource to be monitored to an assignment unit which, on the basis of the resource, selects the detector suitable for the type of monitoring and transfers the necessary parameters to it. After an assignment there is a resource RS1, RS2 or RS3 which is now ready for monitoring and is stored in a list as shown.
- the instance DFW also contains a number of subprocesses TH1 to TH ⁇ , the so-called threads, which are idle. Accordingly, they are dormant subprocesses that do not require any computing time, but can easily be linked to functions from dynamic libraries in order to monitor a resource.
- the threads have the advantage that no additional computing time has to be used for their start, but that once they are started they are waiting for their execution.
- the device KE3 links the free partial process TH2 with the functions of a dynamic library required for the monitoring the parameters dependent on the resource R3 and assigned by KE2 and executes the sub-process TH2.
- Starting, executing, stopping and synchronization are carried out in the embodiment by the POSIX (Portable Operating System Interface for UNIX) standard for UNIX operating systems.
- the device KE3 breaks the link again and puts the thread TH2 to sleep again. The thread can then be linked to another resource.
- a result message supplied by the monitoring detector is returned to the Reliant Management Service RMS by the instance DFW after execution as a status message.
- Access to shared data between the device KE and the sub-processes TH is sequenced via Semphore.
- the detectors can be designed using dynamic libraries that can be loaded and executed as required, a high degree of flexibility can be achieved.
- the dynamic libraries can be replaced by extended libraries at any time without having to stop or restart the Reliant Management Service RMS or the detector framework DFW. If the library expands or changes, the KE facility loads the new variant. Extensions, troubleshooting and dynamic reconfiguration are possible at any time.
- FIG 3 shows an embodiment of the instance DFW, which meets these two requirements.
- a time period is determined in a time interval in which the instance DFW may monitor resources.
- the time interval and the duration can be specified by a user. This can be a percentage value, for example 15% of the total computing time, or an absolute value, for example 100 ms in 1 second. Additional requirements, for example regarding hardware or software applications, can also be taken into account via the configuration file.
- a numerical priority value for each resource to be monitored is defined and assigned in a second configuration file P2. These are communicated to the control device of the instance DFW via the interfaces S1 and S2.
- the priority values are defined in the configuration file P2 by the Reliant Management Service RMS. For example, it is necessary to give resource X of the highly available application APL a higher priority assign as, for example, the resource for the integration point of the mass storage Ml. These priorities are used by the DFW instance to determine an order of monitoring. A resource with a higher priority should be monitored more often than a resource with a lower priority. For this purpose, the individual resources to be monitored are stored in a list L1 according to their priority.
- the following table shows the resources for the highly available application APL according to FIG. 4, their assigned priorities, the parameters to be transferred and the time after which a check must be carried out. This therefore determines a maximum value that must not be exceeded.
- the last column in the table shows the length of time that the monitoring detector started by the control device KE needs to check the associated resource.
- Table 1 List of resources with further information
- the control device KE now checks the remaining time according to the specification in the configuration file P1, the priorities of the resources, the time elapsed since the last check for each resource and the time period and selects a resource to be checked from this.
- the detector assigned to the selected resource is linked to a still free subprocess or thread, the parameters are transferred and the subprocess is executed. After the monitoring has ended, the link is released again and the subprocess is available for a new connection.
- the resource becomes the list again Ll supplied, however, the time elapsed since the last check and possibly the priority changes. In addition, it is useful to determine the time that the monitoring detector required for the execution, since conditions could have changed and monitoring now takes longer or shorter.
- control device KE or the monitoring device DFW increases the priority. This prevents waiting resources from never being checked due to insufficient priority.
- FIG. 5 shows such a time sequence for monitoring.
- Table 2 contains the resources Rl to R7, their respective original priority transferred from the Reliant Management System RMS to the detector framework DFW and the time taken for execution from a configuration file.
- the list L3 shown in FIG. 5 results.
- the resource R1 with its priority NP and its duration of 10 ms was only executed once and continues to run in the background. It is a resource for which a "non-polling" detector is provided. This is started and waits for a message from the linked resource. In contrast to "polling" detectors, polling is not active. This means that hardly any computing time is used. As soon as the detector R1 receives a message from the resource, it can be ended again by the detector framework DFW.
- the resource R2 has the highest priority 5 with a duration of 30 ms and is linked and executed with the associated monitoring detector.
- the control device KE of the detector framework DFW links resources R3 and R4, which also have priority 5, to an existing sub-process from its list, transfers the parameter sets of the resources to the dynamic library provided for monitoring, and manages the threads out.
- the resource R5 with its priority 3 can also be monitored within the time interval.
- the resource R6 with the same priority has an execution time of 100 ms and would therefore exceed the prescribed time interval of 450 ms.
- the execution time for the monitoring detector of the resource R7 is only 50 ms.
- monitoring of resource R7 is not carried out due to the requirement that only resources with priorities greater than 3 be checked.
- the resources R1 to R5 are actively monitored during the time interval of 3 seconds.
- the total time required for monitoring is the sum of the individual execution times, a total of 400 ms. However, it is when the monitoring is carried out within the time interval not fixed. The operating system scheduler takes on this task.
- the detector framework only has the requirement not to exceed the 450 ms duration in a time interval of 3s on average, or to use no more than 15% of the available computing time for monitoring.
- the new time interval begins after 3 seconds and the DFW instance starts the monitoring detectors again for the resources now provided.
- the resource R1 continues to run.
- a sub-process with the monitoring detector for resource R2 is also started due to high priority 5. Because resource R3 has been checked in the previous time interval, the priority of resource R3 in table L4 is reduced again to the original value 3. Because of the sufficient time available, the control device KE of the detector framework DFW links the resource again to a free thread and carries out surveillance.
- resource R4 After monitoring of resource R4 in the previous time interval, resource R4 now receives the original priority value 1 again. The same applies to resource R5. Since a check of resource R6 was not possible due to the lack of time in the previous time interval, the detector framework DFW increases the priority of resource R6 by one point to the value 4. Monitoring is now also carried out here. The total time for monitoring is now 170 ms.
- a resource to be monitored is started only once per time interval. However, it is possible, for example, to check resource R2 several times within the time interval of 450 ms. Furthermore, in this embodiment, the priority value is linked to the time of the last execution. The priority is in increased every time the resource was not monitored.
- the resources are often represented by data structures within the cluster's memory. These can be read by monitoring detectors which are formed by the dynamic libraries. This is particularly useful if the resources have different types of monitoring.
- the second interface S2 to a user interface makes it possible to issue commands for the immediate checking of a resource of the node. Furthermore, the configuration file of the instance DFW can also be read in again in order to implement dynamic changes.
- the device and the method according to the invention create a possibility of no longer using a number of monitoring detectors independently, but instead of carrying them out as a function of one another.
- a monitoring detector is executed once, the monitoring detector itself being able to check the resource to be monitored several times during its execution. It is possible to check several different aspects of the resource and to return a final overall status message.
- the shared "Detector Framework DFW” enables a particularly effective and time-saving programming through shared functions.
- the existing computing time of a node is optimally used and it also reacts dynamically to changes in the available computing time.
- DFW Detector Framework, monitoring device
Landscapes
- Engineering & Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
- Selective Calling Equipment (AREA)
Abstract
Description
Claims
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE10360535A DE10360535B4 (de) | 2003-12-22 | 2003-12-22 | Einrichtung und Verfahren zur Steuerung und Kontrolle von Überwachungsdetektoren in einem Knoten eines Clustersystems |
PCT/DE2004/002483 WO2005062172A2 (de) | 2003-12-22 | 2004-11-10 | Einrichtung und verfahren zur steuerung und kontrolle von überwachungsdetektoren in einem knoten eines clustersystems |
Publications (1)
Publication Number | Publication Date |
---|---|
EP1697846A2 true EP1697846A2 (de) | 2006-09-06 |
Family
ID=34683765
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP04802700A Withdrawn EP1697846A2 (de) | 2003-12-22 | 2004-11-10 | Einrichtung und verfahren zur steuerung und kontrolle von überwachungsdetektoren in einem knoten eines clustersystems |
Country Status (5)
Country | Link |
---|---|
US (1) | US8051173B2 (de) |
EP (1) | EP1697846A2 (de) |
JP (1) | JP4584268B2 (de) |
DE (1) | DE10360535B4 (de) |
WO (1) | WO2005062172A2 (de) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB0516554D0 (en) * | 2005-08-11 | 2005-09-21 | Ibm | Method, apparatus and computer program for enabling monitoring of a resource |
US20110002231A1 (en) * | 2009-04-21 | 2011-01-06 | David Philip Hole | System and method for adjusting monitoring of timeslots during data transmission |
US8812631B2 (en) * | 2011-05-11 | 2014-08-19 | International Business Machines Corporation | Method and arrangement for operating a computer cluster |
US10873501B2 (en) * | 2016-12-09 | 2020-12-22 | Vmware, Inc. | Methods, systems and apparatus to propagate node configuration changes to services in a distributed environment |
Family Cites Families (28)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US3932735A (en) * | 1970-08-24 | 1976-01-13 | Westinghouse Electric Corporation | Method of controlling supply of power |
US5542047A (en) * | 1991-04-23 | 1996-07-30 | Texas Instruments Incorporated | Distributed network monitoring system for monitoring node and link status |
DE69317982T2 (de) * | 1992-10-09 | 1998-11-19 | Sun Microsystems, Inc., Mountain View, Calif. 94043-1100 | Verfahren und Anlage zur Realzeitdatensammlung und Anzeigevorrichtung |
US5537542A (en) * | 1994-04-04 | 1996-07-16 | International Business Machines Corporation | Apparatus and method for managing a server workload according to client performance goals in a client/server data processing system |
US5717858A (en) * | 1994-10-17 | 1998-02-10 | Motorola, Inc. | Method and structure for prioritizing performance monitoring cells in an asynchronous transfer mode (ATM) system |
JPH08263325A (ja) * | 1995-03-20 | 1996-10-11 | Fujitsu Ltd | サーバ処理装置、サーバ内障害検出装置及びサーバ内障害検出方法 |
AU7360296A (en) * | 1995-09-11 | 1997-04-01 | Mcsb Technology Corporation | Performance assistant file system (pafs) method and apparatus |
FI955200A (fi) * | 1995-10-31 | 1997-05-01 | Nokia Mobile Phones Ltd | Yhteiskäytäntö half-duplex -liikennöintiä varten |
EP1081594A4 (de) * | 1998-05-27 | 2009-12-02 | Mitsubishi Electric Corp | Peripherale ausrüstung für programmierbaren kontrollierer und verfahren zu dessen überwachung |
CA2348071A1 (en) * | 1998-10-20 | 2000-04-27 | Ajay Deo | Method and apparatus for providing real-time call processing services in an intelligent network |
US6434613B1 (en) | 1999-02-23 | 2002-08-13 | International Business Machines Corporation | System and method for identifying latent computer system bottlenecks and for making recommendations for improving computer system performance |
US6633339B1 (en) * | 1999-03-31 | 2003-10-14 | Matsushita Electric Industrial Co., Ltd. | Method and device for seamless-decoding video stream including streams having different frame rates |
US6484088B1 (en) * | 1999-05-04 | 2002-11-19 | Ssi Technologies, Inc. | Fuel optimization system with improved fuel level sensor |
JP3309834B2 (ja) * | 1999-07-16 | 2002-07-29 | 日本電気株式会社 | Atm交換装置及びセルバッファ使用率監視方法 |
JP2001331333A (ja) * | 2000-05-18 | 2001-11-30 | Hitachi Ltd | 計算機システム及び計算機システムの制御方法 |
US6666676B2 (en) * | 2000-08-17 | 2003-12-23 | Comercial Acros Whirlpool S.A. De C.V. | Programmable burner for gas stoves |
US6662929B1 (en) * | 2000-11-17 | 2003-12-16 | Lockhead Martin Corporation | Parcel singulation software control logic |
US6854074B2 (en) * | 2000-12-01 | 2005-02-08 | Internetseer.Com Corp. | Method of remotely monitoring an internet web site |
US6763359B2 (en) * | 2001-06-06 | 2004-07-13 | International Business Machines Corporation | Learning from empirical results in query optimization |
CA2474879C (en) * | 2001-07-03 | 2013-04-09 | Imagine Broadband Limited | Method and system for monitoring service performance over a virtual private network connection by simulating end user activity |
JP2003177945A (ja) * | 2001-12-12 | 2003-06-27 | Hitachi Ltd | 計算機管理方法及びその実施システム並びにその処理プログラム |
JP3766332B2 (ja) * | 2002-02-12 | 2006-04-12 | アライドテレシスホールディングス株式会社 | 管理装置及びプログラム |
US7194000B2 (en) * | 2002-06-21 | 2007-03-20 | Telefonaktiebolaget L.M. Ericsson | Methods and systems for provision of streaming data services in an internet protocol network |
CN1333314C (zh) * | 2002-12-11 | 2007-08-22 | 雄图资讯股份有限公司 | 软件执行控制系统 |
US7451201B2 (en) * | 2003-09-30 | 2008-11-11 | International Business Machines Corporation | Policy driven autonomic computing-specifying relationships |
US7461376B2 (en) * | 2003-11-18 | 2008-12-02 | Unisys Corporation | Dynamic resource management system and method for multiprocessor systems |
US20060085530A1 (en) * | 2004-10-15 | 2006-04-20 | Emc Corporation | Method and apparatus for configuring, monitoring and/or managing resource groups using web services |
GB0426125D0 (en) * | 2004-11-27 | 2004-12-29 | Ibm | The connection of an application to a resource manager selected from a plurality of resource managers |
-
2003
- 2003-12-22 DE DE10360535A patent/DE10360535B4/de not_active Expired - Fee Related
-
2004
- 2004-11-10 JP JP2006545900A patent/JP4584268B2/ja not_active Expired - Fee Related
- 2004-11-10 WO PCT/DE2004/002483 patent/WO2005062172A2/de active Application Filing
- 2004-11-10 EP EP04802700A patent/EP1697846A2/de not_active Withdrawn
-
2006
- 2006-06-22 US US11/472,546 patent/US8051173B2/en not_active Expired - Fee Related
Non-Patent Citations (1)
Title |
---|
See references of WO2005062172A2 * |
Also Published As
Publication number | Publication date |
---|---|
US20070011315A1 (en) | 2007-01-11 |
JP2007515727A (ja) | 2007-06-14 |
JP4584268B2 (ja) | 2010-11-17 |
US8051173B2 (en) | 2011-11-01 |
DE10360535B4 (de) | 2006-01-12 |
DE10360535A1 (de) | 2005-07-21 |
WO2005062172A3 (de) | 2006-03-30 |
WO2005062172A2 (de) | 2005-07-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE69522046T2 (de) | Verfahren zur hierarchischen Betriebsmittelverwaltung | |
EP1901191B1 (de) | Verfahren und Anordnung zur Verwaltung von Lizenzen | |
DE69514444T2 (de) | Verfahren für die Ablauffolgeplanung von aufeinanderfolgenden Aufgaben mit Zeitzwangsbedingungen | |
DE69505218T2 (de) | Verfahren zur Fehleridentifizierung in einem komplexen System | |
DE60004886T2 (de) | System und verfahren zum bereitstellen einer sammlung von wiederverwendbaren fäden zum behandeln von gepufferten aufgaben | |
DE60220287T2 (de) | System und verfahren zur überwachung von software-warteschlangenanwendungen | |
EP0992903B1 (de) | Verfahren zur Durchführung von Kooperativem Multitasking in einem Nachrichtenübertragungsnetz und Netzelement dafür | |
DE3852997T2 (de) | Rechnersystem und Verfahren für die Überwachung von nichtstationären Datenstrukturen in einem Rechnersystem. | |
EP0807883B1 (de) | Kommunikationssystem mit Mitteln zum Austausch von Softwareprozessen | |
DE10059796A1 (de) | Steuerung der Lebensdauer von Aktivitäten für die Datenverarbeitung | |
EP0952520A2 (de) | Vorrichtung zur fehlertoleranten Ausführung von Programmen | |
DE2911677B2 (de) | Verfahren und Schaltungsanordnung zum Überwachen und Verhindern von Blockierungen in Datenverarbeitungssystemen mit mehreren Prozessoren | |
DE69518453T2 (de) | Verfahren und System zum Dynamischen Auswählen eines Kommunikationsmodus | |
WO2005073852A1 (de) | Verfahren zum betreiben einer anordnung mehrerer rechner bei einem rechnerausfall | |
DE102009004726A1 (de) | Systeme und Verfahren zum Verfolgen von Befehlszeigern und Datenzugriffen | |
DE102007041345B4 (de) | X-Core Bildrekonstruktionssystem (IRS) mit x-parallelen Recon-Pipelines | |
DE10360535B4 (de) | Einrichtung und Verfahren zur Steuerung und Kontrolle von Überwachungsdetektoren in einem Knoten eines Clustersystems | |
EP1514180A2 (de) | Reaktionszeit-beschränkung eines software-prozesses | |
EP2615511A1 (de) | Verfahren zur synchronen Ausführung von Programmen in einem redundanten Automatisierungssystem | |
DE69521337T2 (de) | Mechanismus für eine konfigurierung | |
EP1536328B1 (de) | Datenverarbeitungssystem mit automatisierbarer Verwaltung und Verfahren zur automatisierten Verwaltung eines Datenverarbeitungssystems | |
DE60110318T2 (de) | Verfahren und Vorrichtung zur Überwachung und Steuerung von elektronischen Geräten | |
DE10123822A1 (de) | Einrichtung zur Verwaltung einer Dienstverbindung zwischen einem Clientprozess mit einer Single-Thread-Bibliothek und einem Serverprozess | |
EP2178267B1 (de) | Verfahren zur Ausführung von Diensten in einem dezentralen Datennetz | |
DE19807436B4 (de) | System und Verfahren zur Steuerung und Überwachung von Programmen in einem Rechnerverbund |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
PUAK | Availability of information related to the publication of the international search report |
Free format text: ORIGINAL CODE: 0009015 |
|
17P | Request for examination filed |
Effective date: 20060531 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LU MC NL PL PT RO SE SI SK TR |
|
AX | Request for extension of the european patent |
Extension state: AL HR LT LV MK YU |
|
DAX | Request for extension of the european patent (deleted) | ||
RBV | Designated contracting states (corrected) |
Designated state(s): DE FR GB NL |
|
17Q | First examination report despatched |
Effective date: 20090827 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: FUJITSU TECHNOLOGY SOLUTIONS INTELLECTUAL PROPERTY |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
GRAJ | Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deleted |
Free format text: ORIGINAL CODE: EPIDOSDIGR1 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN |
|
INTG | Intention to grant announced |
Effective date: 20131125 |
|
18W | Application withdrawn |
Effective date: 20131119 |
|
INTC | Intention to grant announced (deleted) |