CA2241840A1 - Dynamic changes in configuration - Google Patents
Dynamic changes in configuration Download PDFInfo
- Publication number
- CA2241840A1 CA2241840A1 CA002241840A CA2241840A CA2241840A1 CA 2241840 A1 CA2241840 A1 CA 2241840A1 CA 002241840 A CA002241840 A CA 002241840A CA 2241840 A CA2241840 A CA 2241840A CA 2241840 A1 CA2241840 A1 CA 2241840A1
- Authority
- CA
- Canada
- Prior art keywords
- configuration
- configuration change
- transaction
- software components
- software
- 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.)
- Abandoned
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
Abstract
Configuration changes are dynamically applied to a cluster multiprocessing system by enqueuing a configuration change event. When the configuration change event is processed, the prior configuration is backed up and each software component applies a relevant portion of a configuration change transaction in an ordered, synchronized manner.
Each software component applies its portion of the transaction either by reinitialization or a logged transition operation. If the configuration change transaction fails, the software components roll back the portions of the configuration change already applied in an ordered, synchronized manner to restore the prior configuration. Multiple events for different configuration changes may be enqueued.
Each software component applies its portion of the transaction either by reinitialization or a logged transition operation. If the configuration change transaction fails, the software components roll back the portions of the configuration change already applied in an ordered, synchronized manner to restore the prior configuration. Multiple events for different configuration changes may be enqueued.
Description
DYNAMIC CHANGES IN CONFIGURATION
BACKGROUND OF THE INVENTION
1. Technical Field:
The present invention relates in general to cluster multiprocessing systems and in 5 particular to dynamic reconfiguration of cluster multiprocessing systems. Still more particularly, the present invention relates to dynamic reconfiguration of highly available cluster multiprocessing systems.
BACKGROUND OF THE INVENTION
1. Technical Field:
The present invention relates in general to cluster multiprocessing systems and in 5 particular to dynamic reconfiguration of cluster multiprocessing systems. Still more particularly, the present invention relates to dynamic reconfiguration of highly available cluster multiprocessing systems.
2. Description of the Related Art:
High availability (HA) is gaining widespread commercial acceptance as an alternative to fault tolerance for mission-critical computing platforms. Fault tolerant data processing systems rely on specialized hardware to detect hardware faults and switch to a redundant hardware component, regardless of whether the component is a processor, memory board, hard disk drive, adapter, power supply, etc. While providing seamless cutover and uninterrupted performance, fault tolerant systems are expensive due to the redundant hardware requirement. Additionally, fault tolerant systems do not address software errors, a more common source of data processing system failure.
High availability utilizes standard hardware, but provides software allowing resources to be shared system wide. When a node, component, or application fails, an 20 alternative path to the desired resource is quickly established. The brief interruption required to reestablish availability of the resource is acceptable in many situations. The hardware costs are significantly less than fault tolerant systems, and backup facilities may be utilized during normal operation.
Highly available systems are often implemented as clustered multiprocessor (CMP)25 systems. A cluster includes a plurality of nodes or processors connected to shared resources, such as shared external hard disks. Typically, each node runs a server or "back end" application permitting access to the shared resources. A node may "own" a set of resources--disks, volume groups, file systems, networks, networks addresses and/or applications--as long as that node is available. When that node goes down, access to the resources is provided through a different node.
An active configuration comprises a set of hardware and software entities together with a set of relationships among these entities, the combination of entities and relationships delivering services to users. Hardware entities specify nodes, adapters, shared disks, etc. while software entities specify failover and reintegration policies. For example, a particular software entity may specify that an application server should failover to node B when node A fails. It may also specify whether the application server should fail back to node A when node A reintegrates.
Within clustered multiprocessing systems, it would be advantageous to be able todynamically reconfigure an active cluster, changing the cluster configuration without having to stop and then restart cluster services. Dynamic change of an active configuration preferably changes the entity and relationship sets while the system is running, with as little disruption of service as possible. Such dynamic configuration changes are required when the cluster is serving mission-critical applications that cannot be brought down for long periods of time (and preferably are not brought down at all).
An example of a situation requiring persistent support for dynamic configurationchanges is performing a hardware upgrade within a four node cluster (nodes A, B, C and D). A user may need to bring down the node to be upgraded, such as node D, upgrade the hardware, rejoin node D to the cluster, and possibly make configuration changes. If node D were equipped with a faster processor and/or additional memory, for instance, the user may wish node D to become the primary system for an application server previously run on a different node. The user will desire to make these changes and will want the changes to be preserved across power outages and cluster reboots.
Another example of a situation requiring dynamic configuration changes involves transient dynamic configuration changes. If the workload of a node temporarily increases, the user may wish to move an application server previously run on that system to another node. Since the increased workload is not normal, the change need not be preserved across cluster reboots.
At least one prior art cluster software package--HACMP for AIX~, available from 5 International Business Machines Corporation of Armonk, New York--provides somedynamic reconfiguration capabilities. Each node includes a default configuration which is copied into the active configuration for the respective node at cluster start-up. The default configuration may be modified while the cluster is active and copied into the default configurations of other nodes. This modified default configuration is then copied into a 10 staging configuration in each active node. The new configuration is verified and, when the daemons for each cluster node are refreshed, copied into the active configuration for active nodes. Cluster services for an inactive nodes added by the reconfiguration may then be started.
The prior art system for dynamic reconfiguration has several limitations. First,multiple reconfigurations cannot be synchronized. When a second reconfiguration is initiated while a dynamic reconfiguration is in progress, the presence of a staging configuration on any cluster node acts as a lock preventing initiation of a new dynamic reconfiguration event.
Second, the prior art system cannot be utilized to effect dynamic changes when 20 multiple software components are involved in applying different parts of the changes to the configuration. Where a dynamic configuration change involving multiple software components fails, the changes already performed up to the point of failure must be rolled back. This is much more complex than dynamically changing only a single component, and reverting to an old configuration if the attempted configuration change fails. Thus, the 25 changes which may be made dynamically are limited.
It would be desirable, therefore, to provide an cluster multiprocessing system with support for dynamic changes involving multiple software components, and for synchronizing multiple dynamic reconfigurations. It would further be desirable to coordinate dynamic configuration changes with other events in a system and to make the dynamic changes in a fail safe manner.
SUMMARY OF THE INVENTION
it is therefore one object of the present invention to provide an improved cluster multiprocessing system.
It is another object of the present invention to provide an improved method of dynamic reconfiguration of cluster multiprocessing systems.
It is yet another object of the present invention to provide dynamic reconfiguration of highly available cluster multiprocessing systems synchronized across multiple software components.
The foregoing objects are achieved as is now described. Configuration changes are dynamically applied to a cluster multiprocessing system by enqueuing a configuration change event. When the configuration change event is processed, the prior configuration is backed up and each software component applies a relevant portion of a configuration change transaction in an ordered, synchronized manner. Each software component applies its portion of the transaction either by reinitialization or a logged transition operation. If the configuration change transaction fails, the software components roll back the portions of the configuration change already applied in an ordered, synchronized manner to restore the prior configuration. Multiple events for different configuration changes may be enqueued.
The above as well as additional objects, features, and advantages of the presentinvention will become apparent in the following detailed written description.
BRIEF DESCRIPTION OF THE DRAWINGS
The novel features believed characteristic of the invention are set forth in theappended claims. The invention itself however, as well as a preferred mode of use, further objects and advantages thereof, will best be understood by reference to the following CA 0224l840 l998-06-29 detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:
Figure 1 depicts a diagram of a cluster multiprocessing system in which a preferred embodiment of the present invention may be implemented;
Figure 2 is a queue structure which may be employed by a process for dynamicallyreconfiguring a highly available clustered multiprocessing system involving multiple software components in accordance with a preferred embodiment of the present invention;
and Figures 3A-3B depict a high level flowchart for a process of dynamically reconfiguring a highly available clustered multiprocessing system involving multiple software components in accordance with a preferred embodiment of the present inventions.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
With reference now to the figures, and in particular with reference to Figure 1, a diagram of a cluster multiprocessing system in which a preferred embodiment of the present invention may be implemented is depicted. System 102 includes a plurality of server nodes 104-110, each typically identified by a unique name. Each node 104-110 may be a symmetric multiprocessor (SMP) data processing system such as a RISC
System/6000~ system available from International Business Machines Corporation of Armonk, New York or a data processing system functioning as a Windows NTTM server.
Each node 104-110 within system 102 includes an operating system, such as the Advanced Interactive Executive (AIX~) operating system available from International Business Machines Corporation of Armonk, New York or the Windows NTTM operating system available from Microsoft Corporation of Redmond, Washington. Nodes 104-110 within system 102 also include high availability cluster software capable of running on top of or in conjunction with the operating system. This high availability cluster software will include the features described below.
Nodes 104-110 are connected to public local area networks 112-114, which may be an Ethernet, Token-Ring, fiber distributed data interface (FDDI), or other network. Public networks 112-114 provide clients 116-120 with access to servers 104-110. Clients 116-120 are data processing systems which may access nodes 104-110, each running a "front end" or client application which queries server applications running on nodes 104-110.
Typically, each node 104-110 runs server or "back end" applications which accessdata on shared external disks 122-126 via disk buses 128-130. Nodes 104-110 may also be connected by an additional network 132 or networks. For example, a private network may provide point-to-point connection between nodes 104-110 within system 102, with no access provided to clients 116-120. The private network, if available, may be utilized for lock traffic, and may be an Ethernet, Token-Ring, FDDI, or serial optical channel connector (SOCC) network. A serial network may also provide point-to-point communication between nodes 104-110, used for control messages and heartbeat traffic in the event that an alternative subsystem fails.
As depicted in the exemplary embodiment, system 102 may include some level of redundancy to eliminate single points of failure. For example, each node 104-110 may be connected to each public network 112-114 by two network adapters: a service adapter providing the primary active connection between a node and network and a standbyadapter which substitutes for the service adapter in the event that the service adapter fails.
Thus, when a resource within system 102 becomes unavailable, alternative resources may be quickly substituted for the failed resource.
Those of ordinary skill in the art will appreciate that the hardware depicted in the exemplary embodiment of Figure 1 may vary. For example, a system may include more or fewer nodes, additional clients, and/or other connections not shown. Additionally, the present invention may be implemented within any software which utilizes configuration data and needs to support dynamic changes in such data. Systems providing high availability are merely employed for the purposes of illustrating and explaining the invention.
Referring to Figure 2, a queue structure which may be employed by a process for dynamically reconfiguring a highly available clustered multiprocessing system involving multiple software components in accordance with a preferred embodiment of the present invention is illustrated. Coordination in processing events--typically failure (or "failover") events and recovery (or "reintegration") events--related to highly available resources is 5 required. Such coordination is provided by a replicated event queue. The event queue in the exemplary embodiment is a replicated event queue maintained by a coordination component of the high availability cluster software. The coordination component is a distributed entity having a daemon running on each node within the cluster. The coordination component subscribes to other components of the high availability cluster 10 software such as a component for handling node and adapter failures, a component for handling forced failovers by a system administrator, and/or a component for handling application server failures. The coordination component is notified by other components of events which have occurred through an API, collects the events, and determines which of the events should be enqueued for processing. The coordination component may also remove events from the queue under appropriate circumstances.
Events within the queue are processed utilizing information contained within a cluster configuration, and often comprise multiple phases separated by barriers. The phases are generally distributed actions resulting from statements executed in parallel on different nodes within the cluster. Optional barriers between statements allow the one statement to be completed on all nodes within the cluster before a subsequent statement is begun on any node within the cluster. For example, if an application server is to be changed to a different node, every node in the cluster must stop utilizing the application server on the current node before the application server is restarted on the new node.
Failure to coordinate dynamic configuration changes with event processing may result in different configuration information being utilized in various phases of processing a given event, resulting in inconsistent or incorrect behavior.
The expandable queue structure 202 depicted includes a plurality of queue entries 204 together with a pointer 206 to a first queue entry and a pointer 208 to a last queue entry. Queue structure 202 also includes flags 210, which may be employed in dynamically reconfiguring a highly available data processing system involving multiple software components. Each queue entry 204 may include an event name (such as "node_up") and a priority. Priority classes may be employed, such that all events relating to nodes are 5 assigned a first priority while all events relating to adapters are assigned a second priority and all events relating to application servers are assigned a third priority. Each queue entry 204 may also include a node identification, a time stamp, pointers to the next queue entry and the previous queue entry, an event type (i.e., internally generated or externally generated), and parameters for processing the event.
With reference now to Figures 3A and 3B, a high level flowchart for a process ofdynamically reconfiguring a highly available clustered multiprocessing system involving multiple software components in accordance with a preferred embodiment of the present invention is depicted. The process is employed by a configuration component of highly available cluster software.
The process depicted begins at step 302, which depicts initiation of a dynamic configuration change by the user. For example, the user may alter the primary node for a specific application server or temporarily change the primary and standby nodes for all application servers for a given node in order to bring that node down. The process then passes to step 304, which illustrates notifying all nodes within the system that a 20 configuration change event has been initiated. The notification may be performed by setting a flag associated with the event queue.
The process then passes to step 306, which depicts placing a configuration change event in the replicated event queue. In the exemplary embodiment, the replicated event queue is the same queue utilized for failure and recovery events. A separate event queue 25 may be utilized for configuration change events, but would still require coordination with the existing event queue.
The queue may already contain other events already being processed and/or other events having a higher associated priority than the configuration change event. For example, a previous configuration change event may be in progress, or a failure or recovery event may be assigned a higher priority and processed prior to configuration change events.
The process next passes to step 308, which illustrates a determination of whether 5 the configuration change event may be processed next. At a minimum, this step requires a determination of whether events for which processing had already been begun at the time the configuration change event was initiated are complete. Depending on theparticular implementation, this step may also require a determination of whether the queue contains other events having a higher priority that the configuration change event, such as 10 failure or recovery events. Thus, the process may proceed, for example, to step 309, which illustrates processing the next highest priority event, then return to step 308 to determine whether the configuration change event may be processed next. As long as the configuration change event is not the next event which may be processed, the event continues to be queued. Processing of other events which was in progress at the time the configuration change event was queued are completed before processing of the configuration change event is begun, avoiding the possibility of beginning processing of an event under one configuration and completing processing under a different configuration.
Once the configuration change event becomes the next event which may be 20 processed, the process proceeds to step 310, which depicts backing up the current replicated configuration information. The process then passes to step 312, which depicts initiating a transaction changing the system configuration. In a preferred embodiment of the invention, the cluster software comprises a number of different components handling different aspects of providing a highly available system. The cluster software may include, 25 for example, a component for storing configuration information, a component for detection of failures, and a component for handling failures, and/or a component for providing a user interface. Thus, processing of the transaction may require the involvement of a number of different components within the cluster software.
CA 0224l840 l998-06-29 AT9-97-248 1 o Because the system has been cleared from processing other events, configuration changes relevant for each of the components may be sequentially handled in a coordinated fashion. The components which will be affected by a configuration change will be determined by the nature of the desired configuration change. Each component may 5 be modified in an ordered manner. If multiple software components are concerned with different parts of the configuration change, changes among the components may besynchronized. Such synchronization of the portions of the configuration change applied by different software components may be achieved through the use of flags associated with the replicated event queue. For example, if a new node is added to the system, changes to a topology services component of the cluster software allowing other nodes within the cluster to recognize the new node may be required first. Once this portion of the configuration change is complete on all nodes within the cluster, changes to a recovery services component of the cluster software may be required to failover certain application servers to the new node because it is now the primary processor for those applications.
Following step 310, the process passes to step 312, which illustrates beginning a transaction implementing the configuration change. The transaction may be required to change replicated configuration information, change the resources monitored, change the ownership of resources, etc. of a plurality of software components. Each software component may apply the relevant portion of the configuration change either by 20 reinitialization or by a transition operation from the old to the new configuration. Different components may utilize different methods for applying the configuration change.
Where a component utilizes a transition operation from an old configuration to a new configuration to apply the configuration change, the changes should be logged by the cluster software coordination component. This allows the component to undo the 25 configuration changes in the event that the configuration change transaction fails in either the component utilizing the transition operation or a different component applying a portion of the configuration change.
Referring to Figure 3B, from step 312 the process passes to step 314, which depicts a determination of whether the transaction has failed. Failure of the transaction may occur with respect to any component. If the configuration change transaction has failed, the process proceeds to step 318, which illustrates restoring the configuration. The configuration is restored by an ordered undoing of the changes applied by any software components which have applied their portion of the configuration change, as determined from the log of the transition operation. Each component involved in the configuration change up to the point the transaction failed may, in reverse order of the configuration change transaction, restore the prior configuration applied by that component.
The synchronization requirements associated with the configuration change transaction will apply to undoing the transaction and may be similarly achieved. Depending on the method of applying a configuration change, a software component may reinitialize under the old configuration or backtrack through a logged transition operation.
Once the configuration is restored, the process proceeds to step 320, which depicts notifying the user of the failed configuration change transaction. The indication used to provide such notice may include information regarding the reason the configuration change transaction failed, including an identification of the software component in which the transaction failed. From this information, a system administrator may correct the problem and reinitiate the configuration change.
From step 320, the process proceeds to step 322, which illustrates resuming processing of events. Within this path of the process depicted, the processing of events resumes under the old configuration.
Referring again to step 314, once the transaction successfully completes, the process proceeds to step 322, described above. In this path of the process depicted, however, processing of events resumes under the new configuration.
The present invention permits configuration changes to be dynamically applied when multiple software components are required to complete the configuration change.
Interference from other configuration changes is prevented, and the actions among various software components may be synchronized to apply the configuration change in an CA 0224l840 l998-06-29 ordered manner. A copy of the old configuration is retained, and transition operations within particular components are logged. Transactions utilized to apply the configuration change are thus fail-safe, with components restoring the prior configuration in reverse order upon transaction failure either by reinitialization under the prior configuration or by 5 reverse execution of the transition operation.
It is important to note that while the present invention has been described in the context of a fully functional data processing system, those skilled in the art will appreciate that the mechanism of the present invention is capable of being distributed in the form of a computer readable medium of instructions in a variety of forms, and that the present invention applies equally regardless of the particular type of signal bearing media used to actually carry out the distribution. Examples of computer readable media include:
recordable type media such as floppy disks and CD-ROMs and transmission type media such as digital and analog communication links.
While the invention has been particularly shown and described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the inventlon.
High availability (HA) is gaining widespread commercial acceptance as an alternative to fault tolerance for mission-critical computing platforms. Fault tolerant data processing systems rely on specialized hardware to detect hardware faults and switch to a redundant hardware component, regardless of whether the component is a processor, memory board, hard disk drive, adapter, power supply, etc. While providing seamless cutover and uninterrupted performance, fault tolerant systems are expensive due to the redundant hardware requirement. Additionally, fault tolerant systems do not address software errors, a more common source of data processing system failure.
High availability utilizes standard hardware, but provides software allowing resources to be shared system wide. When a node, component, or application fails, an 20 alternative path to the desired resource is quickly established. The brief interruption required to reestablish availability of the resource is acceptable in many situations. The hardware costs are significantly less than fault tolerant systems, and backup facilities may be utilized during normal operation.
Highly available systems are often implemented as clustered multiprocessor (CMP)25 systems. A cluster includes a plurality of nodes or processors connected to shared resources, such as shared external hard disks. Typically, each node runs a server or "back end" application permitting access to the shared resources. A node may "own" a set of resources--disks, volume groups, file systems, networks, networks addresses and/or applications--as long as that node is available. When that node goes down, access to the resources is provided through a different node.
An active configuration comprises a set of hardware and software entities together with a set of relationships among these entities, the combination of entities and relationships delivering services to users. Hardware entities specify nodes, adapters, shared disks, etc. while software entities specify failover and reintegration policies. For example, a particular software entity may specify that an application server should failover to node B when node A fails. It may also specify whether the application server should fail back to node A when node A reintegrates.
Within clustered multiprocessing systems, it would be advantageous to be able todynamically reconfigure an active cluster, changing the cluster configuration without having to stop and then restart cluster services. Dynamic change of an active configuration preferably changes the entity and relationship sets while the system is running, with as little disruption of service as possible. Such dynamic configuration changes are required when the cluster is serving mission-critical applications that cannot be brought down for long periods of time (and preferably are not brought down at all).
An example of a situation requiring persistent support for dynamic configurationchanges is performing a hardware upgrade within a four node cluster (nodes A, B, C and D). A user may need to bring down the node to be upgraded, such as node D, upgrade the hardware, rejoin node D to the cluster, and possibly make configuration changes. If node D were equipped with a faster processor and/or additional memory, for instance, the user may wish node D to become the primary system for an application server previously run on a different node. The user will desire to make these changes and will want the changes to be preserved across power outages and cluster reboots.
Another example of a situation requiring dynamic configuration changes involves transient dynamic configuration changes. If the workload of a node temporarily increases, the user may wish to move an application server previously run on that system to another node. Since the increased workload is not normal, the change need not be preserved across cluster reboots.
At least one prior art cluster software package--HACMP for AIX~, available from 5 International Business Machines Corporation of Armonk, New York--provides somedynamic reconfiguration capabilities. Each node includes a default configuration which is copied into the active configuration for the respective node at cluster start-up. The default configuration may be modified while the cluster is active and copied into the default configurations of other nodes. This modified default configuration is then copied into a 10 staging configuration in each active node. The new configuration is verified and, when the daemons for each cluster node are refreshed, copied into the active configuration for active nodes. Cluster services for an inactive nodes added by the reconfiguration may then be started.
The prior art system for dynamic reconfiguration has several limitations. First,multiple reconfigurations cannot be synchronized. When a second reconfiguration is initiated while a dynamic reconfiguration is in progress, the presence of a staging configuration on any cluster node acts as a lock preventing initiation of a new dynamic reconfiguration event.
Second, the prior art system cannot be utilized to effect dynamic changes when 20 multiple software components are involved in applying different parts of the changes to the configuration. Where a dynamic configuration change involving multiple software components fails, the changes already performed up to the point of failure must be rolled back. This is much more complex than dynamically changing only a single component, and reverting to an old configuration if the attempted configuration change fails. Thus, the 25 changes which may be made dynamically are limited.
It would be desirable, therefore, to provide an cluster multiprocessing system with support for dynamic changes involving multiple software components, and for synchronizing multiple dynamic reconfigurations. It would further be desirable to coordinate dynamic configuration changes with other events in a system and to make the dynamic changes in a fail safe manner.
SUMMARY OF THE INVENTION
it is therefore one object of the present invention to provide an improved cluster multiprocessing system.
It is another object of the present invention to provide an improved method of dynamic reconfiguration of cluster multiprocessing systems.
It is yet another object of the present invention to provide dynamic reconfiguration of highly available cluster multiprocessing systems synchronized across multiple software components.
The foregoing objects are achieved as is now described. Configuration changes are dynamically applied to a cluster multiprocessing system by enqueuing a configuration change event. When the configuration change event is processed, the prior configuration is backed up and each software component applies a relevant portion of a configuration change transaction in an ordered, synchronized manner. Each software component applies its portion of the transaction either by reinitialization or a logged transition operation. If the configuration change transaction fails, the software components roll back the portions of the configuration change already applied in an ordered, synchronized manner to restore the prior configuration. Multiple events for different configuration changes may be enqueued.
The above as well as additional objects, features, and advantages of the presentinvention will become apparent in the following detailed written description.
BRIEF DESCRIPTION OF THE DRAWINGS
The novel features believed characteristic of the invention are set forth in theappended claims. The invention itself however, as well as a preferred mode of use, further objects and advantages thereof, will best be understood by reference to the following CA 0224l840 l998-06-29 detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:
Figure 1 depicts a diagram of a cluster multiprocessing system in which a preferred embodiment of the present invention may be implemented;
Figure 2 is a queue structure which may be employed by a process for dynamicallyreconfiguring a highly available clustered multiprocessing system involving multiple software components in accordance with a preferred embodiment of the present invention;
and Figures 3A-3B depict a high level flowchart for a process of dynamically reconfiguring a highly available clustered multiprocessing system involving multiple software components in accordance with a preferred embodiment of the present inventions.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
With reference now to the figures, and in particular with reference to Figure 1, a diagram of a cluster multiprocessing system in which a preferred embodiment of the present invention may be implemented is depicted. System 102 includes a plurality of server nodes 104-110, each typically identified by a unique name. Each node 104-110 may be a symmetric multiprocessor (SMP) data processing system such as a RISC
System/6000~ system available from International Business Machines Corporation of Armonk, New York or a data processing system functioning as a Windows NTTM server.
Each node 104-110 within system 102 includes an operating system, such as the Advanced Interactive Executive (AIX~) operating system available from International Business Machines Corporation of Armonk, New York or the Windows NTTM operating system available from Microsoft Corporation of Redmond, Washington. Nodes 104-110 within system 102 also include high availability cluster software capable of running on top of or in conjunction with the operating system. This high availability cluster software will include the features described below.
Nodes 104-110 are connected to public local area networks 112-114, which may be an Ethernet, Token-Ring, fiber distributed data interface (FDDI), or other network. Public networks 112-114 provide clients 116-120 with access to servers 104-110. Clients 116-120 are data processing systems which may access nodes 104-110, each running a "front end" or client application which queries server applications running on nodes 104-110.
Typically, each node 104-110 runs server or "back end" applications which accessdata on shared external disks 122-126 via disk buses 128-130. Nodes 104-110 may also be connected by an additional network 132 or networks. For example, a private network may provide point-to-point connection between nodes 104-110 within system 102, with no access provided to clients 116-120. The private network, if available, may be utilized for lock traffic, and may be an Ethernet, Token-Ring, FDDI, or serial optical channel connector (SOCC) network. A serial network may also provide point-to-point communication between nodes 104-110, used for control messages and heartbeat traffic in the event that an alternative subsystem fails.
As depicted in the exemplary embodiment, system 102 may include some level of redundancy to eliminate single points of failure. For example, each node 104-110 may be connected to each public network 112-114 by two network adapters: a service adapter providing the primary active connection between a node and network and a standbyadapter which substitutes for the service adapter in the event that the service adapter fails.
Thus, when a resource within system 102 becomes unavailable, alternative resources may be quickly substituted for the failed resource.
Those of ordinary skill in the art will appreciate that the hardware depicted in the exemplary embodiment of Figure 1 may vary. For example, a system may include more or fewer nodes, additional clients, and/or other connections not shown. Additionally, the present invention may be implemented within any software which utilizes configuration data and needs to support dynamic changes in such data. Systems providing high availability are merely employed for the purposes of illustrating and explaining the invention.
Referring to Figure 2, a queue structure which may be employed by a process for dynamically reconfiguring a highly available clustered multiprocessing system involving multiple software components in accordance with a preferred embodiment of the present invention is illustrated. Coordination in processing events--typically failure (or "failover") events and recovery (or "reintegration") events--related to highly available resources is 5 required. Such coordination is provided by a replicated event queue. The event queue in the exemplary embodiment is a replicated event queue maintained by a coordination component of the high availability cluster software. The coordination component is a distributed entity having a daemon running on each node within the cluster. The coordination component subscribes to other components of the high availability cluster 10 software such as a component for handling node and adapter failures, a component for handling forced failovers by a system administrator, and/or a component for handling application server failures. The coordination component is notified by other components of events which have occurred through an API, collects the events, and determines which of the events should be enqueued for processing. The coordination component may also remove events from the queue under appropriate circumstances.
Events within the queue are processed utilizing information contained within a cluster configuration, and often comprise multiple phases separated by barriers. The phases are generally distributed actions resulting from statements executed in parallel on different nodes within the cluster. Optional barriers between statements allow the one statement to be completed on all nodes within the cluster before a subsequent statement is begun on any node within the cluster. For example, if an application server is to be changed to a different node, every node in the cluster must stop utilizing the application server on the current node before the application server is restarted on the new node.
Failure to coordinate dynamic configuration changes with event processing may result in different configuration information being utilized in various phases of processing a given event, resulting in inconsistent or incorrect behavior.
The expandable queue structure 202 depicted includes a plurality of queue entries 204 together with a pointer 206 to a first queue entry and a pointer 208 to a last queue entry. Queue structure 202 also includes flags 210, which may be employed in dynamically reconfiguring a highly available data processing system involving multiple software components. Each queue entry 204 may include an event name (such as "node_up") and a priority. Priority classes may be employed, such that all events relating to nodes are 5 assigned a first priority while all events relating to adapters are assigned a second priority and all events relating to application servers are assigned a third priority. Each queue entry 204 may also include a node identification, a time stamp, pointers to the next queue entry and the previous queue entry, an event type (i.e., internally generated or externally generated), and parameters for processing the event.
With reference now to Figures 3A and 3B, a high level flowchart for a process ofdynamically reconfiguring a highly available clustered multiprocessing system involving multiple software components in accordance with a preferred embodiment of the present invention is depicted. The process is employed by a configuration component of highly available cluster software.
The process depicted begins at step 302, which depicts initiation of a dynamic configuration change by the user. For example, the user may alter the primary node for a specific application server or temporarily change the primary and standby nodes for all application servers for a given node in order to bring that node down. The process then passes to step 304, which illustrates notifying all nodes within the system that a 20 configuration change event has been initiated. The notification may be performed by setting a flag associated with the event queue.
The process then passes to step 306, which depicts placing a configuration change event in the replicated event queue. In the exemplary embodiment, the replicated event queue is the same queue utilized for failure and recovery events. A separate event queue 25 may be utilized for configuration change events, but would still require coordination with the existing event queue.
The queue may already contain other events already being processed and/or other events having a higher associated priority than the configuration change event. For example, a previous configuration change event may be in progress, or a failure or recovery event may be assigned a higher priority and processed prior to configuration change events.
The process next passes to step 308, which illustrates a determination of whether 5 the configuration change event may be processed next. At a minimum, this step requires a determination of whether events for which processing had already been begun at the time the configuration change event was initiated are complete. Depending on theparticular implementation, this step may also require a determination of whether the queue contains other events having a higher priority that the configuration change event, such as 10 failure or recovery events. Thus, the process may proceed, for example, to step 309, which illustrates processing the next highest priority event, then return to step 308 to determine whether the configuration change event may be processed next. As long as the configuration change event is not the next event which may be processed, the event continues to be queued. Processing of other events which was in progress at the time the configuration change event was queued are completed before processing of the configuration change event is begun, avoiding the possibility of beginning processing of an event under one configuration and completing processing under a different configuration.
Once the configuration change event becomes the next event which may be 20 processed, the process proceeds to step 310, which depicts backing up the current replicated configuration information. The process then passes to step 312, which depicts initiating a transaction changing the system configuration. In a preferred embodiment of the invention, the cluster software comprises a number of different components handling different aspects of providing a highly available system. The cluster software may include, 25 for example, a component for storing configuration information, a component for detection of failures, and a component for handling failures, and/or a component for providing a user interface. Thus, processing of the transaction may require the involvement of a number of different components within the cluster software.
CA 0224l840 l998-06-29 AT9-97-248 1 o Because the system has been cleared from processing other events, configuration changes relevant for each of the components may be sequentially handled in a coordinated fashion. The components which will be affected by a configuration change will be determined by the nature of the desired configuration change. Each component may 5 be modified in an ordered manner. If multiple software components are concerned with different parts of the configuration change, changes among the components may besynchronized. Such synchronization of the portions of the configuration change applied by different software components may be achieved through the use of flags associated with the replicated event queue. For example, if a new node is added to the system, changes to a topology services component of the cluster software allowing other nodes within the cluster to recognize the new node may be required first. Once this portion of the configuration change is complete on all nodes within the cluster, changes to a recovery services component of the cluster software may be required to failover certain application servers to the new node because it is now the primary processor for those applications.
Following step 310, the process passes to step 312, which illustrates beginning a transaction implementing the configuration change. The transaction may be required to change replicated configuration information, change the resources monitored, change the ownership of resources, etc. of a plurality of software components. Each software component may apply the relevant portion of the configuration change either by 20 reinitialization or by a transition operation from the old to the new configuration. Different components may utilize different methods for applying the configuration change.
Where a component utilizes a transition operation from an old configuration to a new configuration to apply the configuration change, the changes should be logged by the cluster software coordination component. This allows the component to undo the 25 configuration changes in the event that the configuration change transaction fails in either the component utilizing the transition operation or a different component applying a portion of the configuration change.
Referring to Figure 3B, from step 312 the process passes to step 314, which depicts a determination of whether the transaction has failed. Failure of the transaction may occur with respect to any component. If the configuration change transaction has failed, the process proceeds to step 318, which illustrates restoring the configuration. The configuration is restored by an ordered undoing of the changes applied by any software components which have applied their portion of the configuration change, as determined from the log of the transition operation. Each component involved in the configuration change up to the point the transaction failed may, in reverse order of the configuration change transaction, restore the prior configuration applied by that component.
The synchronization requirements associated with the configuration change transaction will apply to undoing the transaction and may be similarly achieved. Depending on the method of applying a configuration change, a software component may reinitialize under the old configuration or backtrack through a logged transition operation.
Once the configuration is restored, the process proceeds to step 320, which depicts notifying the user of the failed configuration change transaction. The indication used to provide such notice may include information regarding the reason the configuration change transaction failed, including an identification of the software component in which the transaction failed. From this information, a system administrator may correct the problem and reinitiate the configuration change.
From step 320, the process proceeds to step 322, which illustrates resuming processing of events. Within this path of the process depicted, the processing of events resumes under the old configuration.
Referring again to step 314, once the transaction successfully completes, the process proceeds to step 322, described above. In this path of the process depicted, however, processing of events resumes under the new configuration.
The present invention permits configuration changes to be dynamically applied when multiple software components are required to complete the configuration change.
Interference from other configuration changes is prevented, and the actions among various software components may be synchronized to apply the configuration change in an CA 0224l840 l998-06-29 ordered manner. A copy of the old configuration is retained, and transition operations within particular components are logged. Transactions utilized to apply the configuration change are thus fail-safe, with components restoring the prior configuration in reverse order upon transaction failure either by reinitialization under the prior configuration or by 5 reverse execution of the transition operation.
It is important to note that while the present invention has been described in the context of a fully functional data processing system, those skilled in the art will appreciate that the mechanism of the present invention is capable of being distributed in the form of a computer readable medium of instructions in a variety of forms, and that the present invention applies equally regardless of the particular type of signal bearing media used to actually carry out the distribution. Examples of computer readable media include:
recordable type media such as floppy disks and CD-ROMs and transmission type media such as digital and analog communication links.
While the invention has been particularly shown and described with reference to a preferred embodiment, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the inventlon.
Claims (20)
1. A method of supporting a dynamic configuration change in a cluster multiprocessing system, comprising:
initiating a configuration change transaction involving a plurality of software components while the cluster multiprocessing system is running;
performing said configuration change transaction in a sequence of ordered portions, each portion applied by a software component within said plurality of software components;
and responsive to detecting that said configuration change transaction failed, restoring a prior configuration.
initiating a configuration change transaction involving a plurality of software components while the cluster multiprocessing system is running;
performing said configuration change transaction in a sequence of ordered portions, each portion applied by a software component within said plurality of software components;
and responsive to detecting that said configuration change transaction failed, restoring a prior configuration.
2. The method of claim 1, wherein said step of restoring a prior configuration further comprises:
performing said sequence of ordered portions in reverse order.
performing said sequence of ordered portions in reverse order.
3. The method of claim 1, wherein the step of performing said configuration change transaction in a sequence of ordered portions further comprises:
synchronizing each portion within the sequence of ordered portions utilizing flags.
synchronizing each portion within the sequence of ordered portions utilizing flags.
4. The method of claim 1, wherein the step of performing said configuration change transaction in a sequence of ordered portions further comprises:
reinitializing at least one software component within said plurality of softwarecomponents with a new configuration.
reinitializing at least one software component within said plurality of softwarecomponents with a new configuration.
5. The method of claim 1, wherein the step of performing said configuration change transaction in a sequence of ordered portions further comprises:
executing a transition operation from said prior configuration to a new configuration in at least one software component within said plurality of software components; and logging said transition operation.
executing a transition operation from said prior configuration to a new configuration in at least one software component within said plurality of software components; and logging said transition operation.
6. The method of claim 1, wherein said step of initiating a configuration changetransaction involving a plurality of software components further comprises:
creating a copy of said prior configuration;
notifying each node within said cluster multiprocessing system of said configuration change transaction;
enqueuing a configuration change transaction; and responsive to determining that said configuration change transaction may be performed, initiating a first portion of said configuration change transaction in a software component within said plurality of software components.
creating a copy of said prior configuration;
notifying each node within said cluster multiprocessing system of said configuration change transaction;
enqueuing a configuration change transaction; and responsive to determining that said configuration change transaction may be performed, initiating a first portion of said configuration change transaction in a software component within said plurality of software components.
7. The method of claim 1, wherein said step of restoring a prior configuration further comprises:
reinitializing at least one software component within said plurality of softwarecomponents with a new configuration.
reinitializing at least one software component within said plurality of softwarecomponents with a new configuration.
8. The method of claim 1, wherein said step of restoring a prior configuration further comprises:
rolling back a transition operation from said prior configuration to a new configuration in at least one software component within said plurality of software components.
rolling back a transition operation from said prior configuration to a new configuration in at least one software component within said plurality of software components.
9. An apparatus for supporting dynamic configuration changes in a cluster multiprocessing system, comprising:
transaction initiation means for initiating a configuration change transaction involving a plurality of software components while the cluster multiprocessing system is running;
transaction performance means for performing said configuration change transaction in a sequence of ordered portions, each portion applied by a software component within said plurality of software components; and restoration means, responsive to detecting that said configuration change transaction failed, for restoring a prior configuration.
transaction initiation means for initiating a configuration change transaction involving a plurality of software components while the cluster multiprocessing system is running;
transaction performance means for performing said configuration change transaction in a sequence of ordered portions, each portion applied by a software component within said plurality of software components; and restoration means, responsive to detecting that said configuration change transaction failed, for restoring a prior configuration.
10. The apparatus of claim 9, wherein said restoration means further comprises:
means for performing said sequence of ordered portions in reverse order.
means for performing said sequence of ordered portions in reverse order.
11. The apparatus of claim 9, wherein said transaction performance means furthercomprises:
synchronization means for synchronizing each portion within the sequence of ordered portions utilizing flags.
synchronization means for synchronizing each portion within the sequence of ordered portions utilizing flags.
12. The apparatus of claim 9, wherein said transaction performance means furthercomprises:
means for reinitializing at least one software component within said plurality of software components with a new configuration.
means for reinitializing at least one software component within said plurality of software components with a new configuration.
13. The apparatus of claim 9, wherein said transaction performance means furthercomprises:
means for executing a transition operation from said prior configuration to a new configuration in at least one software component within said plurality of software components; and means for logging said transition operation.
means for executing a transition operation from said prior configuration to a new configuration in at least one software component within said plurality of software components; and means for logging said transition operation.
14. The apparatus of claim 9, wherein said transaction initiation means further comprises:
copying means for creating a copy of said prior configuration;
notification means for notifying each node within said cluster multiprocessing system of said configuration change transaction;
means for enqueuing a configuration change transaction; and initiations means, responsive to determining that said configuration change transaction may be performed, for initiating a first portion of said configuration change transaction in a software component within said plurality of software components.
copying means for creating a copy of said prior configuration;
notification means for notifying each node within said cluster multiprocessing system of said configuration change transaction;
means for enqueuing a configuration change transaction; and initiations means, responsive to determining that said configuration change transaction may be performed, for initiating a first portion of said configuration change transaction in a software component within said plurality of software components.
15. The apparatus of claim 9, wherein said restoration means further comprises:
means for reinitializing at least one software component within said plurality of software components with a new configuration.
means for reinitializing at least one software component within said plurality of software components with a new configuration.
16. The apparatus of claim 9, wherein said restoration means further comprises:
means for rolling back a transition operation from said prior configuration to a new configuration in at least one software component within said plurality of software components.
means for rolling back a transition operation from said prior configuration to a new configuration in at least one software component within said plurality of software components.
17. A computer program product for use with a data processing system, comprising:
a computer usable medium;
first instructions on said computer usable medium for initiating a configurationchange transaction involving a plurality of software components;
second instructions on said computer usable medium for performing said configuration change transaction in a sequence of ordered portions, each portion applied by a software component with said plurality of software components; and third instructions on said computer usable medium, responsive to detecting that said configuration change transaction failed, for restoring a prior configuration.
a computer usable medium;
first instructions on said computer usable medium for initiating a configurationchange transaction involving a plurality of software components;
second instructions on said computer usable medium for performing said configuration change transaction in a sequence of ordered portions, each portion applied by a software component with said plurality of software components; and third instructions on said computer usable medium, responsive to detecting that said configuration change transaction failed, for restoring a prior configuration.
18. The computer program product of claim 17, wherein said third instructions further comprise:
instructions for performing said sequence of ordered portions in reverse order.
instructions for performing said sequence of ordered portions in reverse order.
19. A cluster multiprocessing system, comprising:
a plurality of nodes connected by at least one network, each node within said plurality of nodes including a memory containing configuration information for the cluster multiprocessing system;
cluster multiprocessing system software executing on each node, said software:
initiating a configuration change transaction involving a plurality of software components while the cluster multiprocessing system is running; and responsive to detecting that said configuration change transaction failed, restoring a prior configuration.
a plurality of nodes connected by at least one network, each node within said plurality of nodes including a memory containing configuration information for the cluster multiprocessing system;
cluster multiprocessing system software executing on each node, said software:
initiating a configuration change transaction involving a plurality of software components while the cluster multiprocessing system is running; and responsive to detecting that said configuration change transaction failed, restoring a prior configuration.
20. The cluster multiprocessing system of claim 19, said cluster multiprocessingsoftware performing said configuration change transaction in a sequence of ordered portions, each portion applied by a software component with said plurality of software components.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US08/888,550 | 1997-07-07 | ||
| US08/888,550 US6003075A (en) | 1997-07-07 | 1997-07-07 | Enqueuing a configuration change in a network cluster and restore a prior configuration in a back up storage in reverse sequence ordered |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2241840A1 true CA2241840A1 (en) | 1999-01-07 |
Family
ID=25393380
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002241840A Abandoned CA2241840A1 (en) | 1997-07-07 | 1998-06-29 | Dynamic changes in configuration |
Country Status (5)
| Country | Link |
|---|---|
| US (1) | US6003075A (en) |
| KR (1) | KR100297906B1 (en) |
| BR (1) | BR9802326A (en) |
| CA (1) | CA2241840A1 (en) |
| TW (1) | TW406240B (en) |
Families Citing this family (131)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6178529B1 (en) | 1997-11-03 | 2001-01-23 | Microsoft Corporation | Method and system for resource monitoring of disparate resources in a server cluster |
| US6321258B1 (en) * | 1997-12-11 | 2001-11-20 | Hewlett-Packard Company | Administration of networked peripherals using particular file system |
| US6243825B1 (en) | 1998-04-17 | 2001-06-05 | Microsoft Corporation | Method and system for transparently failing over a computer name in a server cluster |
| US6449734B1 (en) | 1998-04-17 | 2002-09-10 | Microsoft Corporation | Method and system for discarding locally committed transactions to ensure consistency in a server cluster |
| US6360331B2 (en) | 1998-04-17 | 2002-03-19 | Microsoft Corporation | Method and system for transparently failing over application configuration information in a server cluster |
| US6163855A (en) * | 1998-04-17 | 2000-12-19 | Microsoft Corporation | Method and system for replicated and consistent modifications in a server cluster |
| US6542928B1 (en) * | 1998-06-02 | 2003-04-01 | Micron Technology, Inc. | Automatic configuration of testers and hosts on a computer network |
| US6363420B1 (en) * | 1998-06-04 | 2002-03-26 | Mortel Networks Limited | Method and system for heuristically designing and managing a network |
| US6427163B1 (en) * | 1998-07-10 | 2002-07-30 | International Business Machines Corporation | Highly scalable and highly available cluster system management scheme |
| US6212559B1 (en) * | 1998-10-28 | 2001-04-03 | Trw Inc. | Automated configuration of internet-like computer networks |
| US6438705B1 (en) * | 1999-01-29 | 2002-08-20 | International Business Machines Corporation | Method and apparatus for building and managing multi-clustered computer systems |
| US6408343B1 (en) * | 1999-03-29 | 2002-06-18 | Hewlett-Packard Company | Apparatus and method for failover detection |
| US6442713B1 (en) * | 1999-03-30 | 2002-08-27 | International Business Machines Corporation | Cluster node distress signal |
| US7076783B1 (en) | 1999-05-28 | 2006-07-11 | Oracle International Corporation | Providing figure of merit vote from application executing on a partitioned cluster |
| US6871222B1 (en) | 1999-05-28 | 2005-03-22 | Oracle International Corporation | Quorumless cluster using disk-based messaging |
| US7020695B1 (en) * | 1999-05-28 | 2006-03-28 | Oracle International Corporation | Using a cluster-wide shared repository to provide the latest consistent definition of the cluster (avoiding the partition-in time problem) |
| JP4201447B2 (en) * | 1999-12-27 | 2008-12-24 | 富士通株式会社 | Distributed processing system |
| US6757836B1 (en) | 2000-01-10 | 2004-06-29 | Sun Microsystems, Inc. | Method and apparatus for resolving partial connectivity in a clustered computing system |
| US6748429B1 (en) * | 2000-01-10 | 2004-06-08 | Sun Microsystems, Inc. | Method to dynamically change cluster or distributed system configuration |
| US6862613B1 (en) | 2000-01-10 | 2005-03-01 | Sun Microsystems, Inc. | Method and apparatus for managing operations of clustered computer systems |
| US6769008B1 (en) | 2000-01-10 | 2004-07-27 | Sun Microsystems, Inc. | Method and apparatus for dynamically altering configurations of clustered computer systems |
| US6789213B2 (en) | 2000-01-10 | 2004-09-07 | Sun Microsystems, Inc. | Controlled take over of services by remaining nodes of clustered computing system |
| US6871346B1 (en) * | 2000-02-11 | 2005-03-22 | Microsoft Corp. | Back-end decoupled management model and management system utilizing same |
| US6725261B1 (en) | 2000-05-31 | 2004-04-20 | International Business Machines Corporation | Method, system and program products for automatically configuring clusters of a computing environment |
| US6876995B1 (en) * | 2000-10-04 | 2005-04-05 | Microsoft Corporation | Web store events |
| US20040139125A1 (en) | 2001-06-05 | 2004-07-15 | Roger Strassburg | Snapshot copy of data volume during data access |
| US7640582B2 (en) | 2003-04-16 | 2009-12-29 | Silicon Graphics International | Clustered filesystem for mix of trusted and untrusted nodes |
| AU2002310411A1 (en) * | 2001-06-14 | 2003-01-02 | Cariden Technologies Incorporated | Methods and systems to generate and implement a changeover sequence to reconfigure a connection-oriented network |
| US8234156B2 (en) | 2001-06-28 | 2012-07-31 | Jpmorgan Chase Bank, N.A. | System and method for characterizing and selecting technology transition options |
| US7295522B2 (en) * | 2001-06-29 | 2007-11-13 | Microsoft Corporation | System and method for continuously provisioning a mobile device |
| US7921188B2 (en) * | 2001-08-16 | 2011-04-05 | Newisys, Inc. | Computer system partitioning using data transfer routing mechanism |
| US6990602B1 (en) * | 2001-08-23 | 2006-01-24 | Unisys Corporation | Method for diagnosing hardware configuration in a clustered system |
| US7130897B2 (en) * | 2001-10-11 | 2006-10-31 | International Business Machines Corporation | Dynamic cluster versioning for a group |
| US6938031B1 (en) | 2001-10-19 | 2005-08-30 | Data Return Llc | System and method for accessing information in a replicated database |
| US7000016B1 (en) | 2001-10-19 | 2006-02-14 | Data Return Llc | System and method for multi-site clustering in a network |
| US7293105B2 (en) * | 2001-12-21 | 2007-11-06 | Cisco Technology, Inc. | Methods and apparatus for implementing a high availability fibre channel switch |
| US7421471B2 (en) * | 2002-05-17 | 2008-09-02 | Sony Computer Entertainment America Inc. | Configuration switching: dynamically changing between network communication architectures |
| US7606920B2 (en) | 2002-05-17 | 2009-10-20 | Sony Computer Entertainment America Inc. | Method and apparatus for controlling communication ports for an online session of a multi-user application by associating each of the ports with a protocol and designating an active port |
| US7281055B2 (en) | 2002-05-28 | 2007-10-09 | Newisys, Inc. | Routing mechanisms in systems having multiple multi-processor clusters |
| US7155525B2 (en) * | 2002-05-28 | 2006-12-26 | Newisys, Inc. | Transaction management in systems having multiple multi-processor clusters |
| US7249174B2 (en) | 2002-06-12 | 2007-07-24 | Bladelogic, Inc. | Method and system for executing and undoing distributed server change operations |
| US6990656B2 (en) * | 2002-06-27 | 2006-01-24 | Microsoft Corporation | Dynamic metabase store |
| US20040024992A1 (en) * | 2002-08-02 | 2004-02-05 | Shan-Chyun Ku | Decoding method for a multi-length-mode instruction set |
| US7558835B1 (en) | 2002-08-19 | 2009-07-07 | Juniper Networks, Inc. | Application of a configuration patch to a network device |
| US7865578B1 (en) | 2002-08-19 | 2011-01-04 | Juniper Networks, Inc. | Generation of a configuration patch for network devices |
| US7340650B2 (en) | 2002-10-30 | 2008-03-04 | Jp Morgan Chase & Co. | Method to measure stored procedure execution statistics |
| US7945669B2 (en) * | 2002-10-30 | 2011-05-17 | Emc Corporation | Method and apparatus for provisioning storage resources |
| US7577755B2 (en) * | 2002-11-19 | 2009-08-18 | Newisys, Inc. | Methods and apparatus for distributing system management signals |
| US7149752B2 (en) | 2002-12-03 | 2006-12-12 | Jp Morgan Chase Bank | Method for simplifying databinding in application programs |
| US7085759B2 (en) | 2002-12-06 | 2006-08-01 | Jpmorgan Chase Bank | System and method for communicating data to a process |
| US8032439B2 (en) | 2003-01-07 | 2011-10-04 | Jpmorgan Chase Bank, N.A. | System and method for process scheduling |
| US7401156B2 (en) | 2003-02-03 | 2008-07-15 | Jp Morgan Chase Bank | Method using control interface to suspend software network environment running on network devices for loading and executing another software network environment |
| US7484087B2 (en) | 2003-02-24 | 2009-01-27 | Jp Morgan Chase Bank | Systems, methods, and software for preventing redundant processing of transmissions sent to a remote host computer |
| US7379998B2 (en) | 2003-03-31 | 2008-05-27 | Jp Morgan Chase Bank | System and method for multi-platform queue queries |
| US7120823B2 (en) * | 2003-04-17 | 2006-10-10 | International Business Machines Corporation | Method and apparatus for recovering logical partition configuration data |
| US7366722B2 (en) | 2003-05-15 | 2008-04-29 | Jp Morgan Chase Bank | System and method for specifying application services and distributing them across multiple processors using XML |
| US7509641B2 (en) | 2003-05-16 | 2009-03-24 | Jp Morgan Chase Bank | Job processing framework |
| US7386626B2 (en) | 2003-06-23 | 2008-06-10 | Newisys, Inc. | Bandwidth, framing and error detection in communications between multi-processor clusters of multi-cluster computer systems |
| US7577727B2 (en) * | 2003-06-27 | 2009-08-18 | Newisys, Inc. | Dynamic multiple cluster system reconfiguration |
| US7222262B2 (en) * | 2003-08-05 | 2007-05-22 | Newisys, Inc. | Methods and devices for injecting commands in systems having multiple multi-processor clusters |
| US7395347B2 (en) | 2003-08-05 | 2008-07-01 | Newisys, Inc, | Communication between and within multi-processor clusters of multi-cluster computer systems |
| US7533163B1 (en) | 2003-12-30 | 2009-05-12 | Sap Ag | Startup framework and method for enterprise computing systems |
| US7526479B2 (en) * | 2003-12-30 | 2009-04-28 | Sap Ag | Configuration manager in enterprise computing system |
| US8601099B1 (en) | 2003-12-30 | 2013-12-03 | Sap Ag | System and method for managing multiple sever node clusters using a hierarchical configuration data structure |
| US8190780B2 (en) | 2003-12-30 | 2012-05-29 | Sap Ag | Cluster architecture having a star topology with centralized services |
| US8312045B2 (en) * | 2003-12-30 | 2012-11-13 | Sap Ag | Configuration data content for a clustered system having multiple instances |
| US7519600B1 (en) | 2003-12-30 | 2009-04-14 | Sap Aktiengesellschaft | System and method for managing multiple application server clusters using a hierarchical data object and a multi-parameter representation for each configuration property |
| US7523097B1 (en) | 2004-01-13 | 2009-04-21 | Juniper Networks, Inc. | Restoration of archived configurations for a network device |
| US7406691B2 (en) * | 2004-01-13 | 2008-07-29 | International Business Machines Corporation | Minimizing complex decisions to allocate additional resources to a job submitted to a grid environment |
| US7562143B2 (en) * | 2004-01-13 | 2009-07-14 | International Business Machines Corporation | Managing escalating resource needs within a grid environment |
| US7552437B2 (en) * | 2004-01-14 | 2009-06-23 | International Business Machines Corporation | Maintaining application operations within a suboptimal grid environment |
| US7464159B2 (en) * | 2004-01-14 | 2008-12-09 | International Business Machines Corporation | Managing analysis of a degraded service in a grid environment |
| JP2005242981A (en) * | 2004-01-28 | 2005-09-08 | Seiko Epson Corp | Service providing system, apparatus, program, and method, and application management system, application management program and method, and storage medium |
| US7702767B2 (en) | 2004-03-09 | 2010-04-20 | Jp Morgan Chase Bank | User connectivity process management system |
| US9734222B1 (en) | 2004-04-06 | 2017-08-15 | Jpmorgan Chase Bank, N.A. | Methods and systems for using script files to obtain, format and transport data |
| WO2005102016A2 (en) | 2004-04-26 | 2005-11-03 | Jp Morgan Chase Bank | System and method for routing messages |
| US7774485B2 (en) * | 2004-05-21 | 2010-08-10 | Bea Systems, Inc. | Dynamic service composition and orchestration |
| US20060031431A1 (en) * | 2004-05-21 | 2006-02-09 | Bea Systems, Inc. | Reliable updating for a service oriented architecture |
| US7266547B2 (en) * | 2004-06-10 | 2007-09-04 | International Business Machines Corporation | Query meaning determination through a grid service |
| US20050289228A1 (en) * | 2004-06-25 | 2005-12-29 | Nokia Inc. | System and method for managing a change to a cluster configuration |
| US7665127B1 (en) | 2004-06-30 | 2010-02-16 | Jp Morgan Chase Bank | System and method for providing access to protected services |
| US7392471B1 (en) | 2004-07-28 | 2008-06-24 | Jp Morgan Chase Bank | System and method for comparing extensible markup language (XML) documents |
| US7712100B2 (en) * | 2004-09-14 | 2010-05-04 | International Business Machines Corporation | Determining a capacity of a grid environment to handle a required workload for a virtual grid job request |
| US7707288B2 (en) * | 2005-01-06 | 2010-04-27 | International Business Machines Corporation | Automatically building a locally managed virtual node grouping to handle a grid job requiring a degree of resource parallelism within a grid environment |
| US7533170B2 (en) * | 2005-01-06 | 2009-05-12 | International Business Machines Corporation | Coordinating the monitoring, management, and prediction of unintended changes within a grid environment |
| US7793308B2 (en) * | 2005-01-06 | 2010-09-07 | International Business Machines Corporation | Setting operation based resource utilization thresholds for resource use by a process |
| US7502850B2 (en) * | 2005-01-06 | 2009-03-10 | International Business Machines Corporation | Verifying resource functionality before use by a grid job submitted to a grid environment |
| US7761557B2 (en) * | 2005-01-06 | 2010-07-20 | International Business Machines Corporation | Facilitating overall grid environment management by monitoring and distributing grid activity |
| US7590623B2 (en) * | 2005-01-06 | 2009-09-15 | International Business Machines Corporation | Automated management of software images for efficient resource node building within a grid environment |
| US7571120B2 (en) * | 2005-01-12 | 2009-08-04 | International Business Machines Corporation | Computer implemented method for estimating future grid job costs by classifying grid jobs and storing results of processing grid job microcosms |
| US7472079B2 (en) * | 2005-01-12 | 2008-12-30 | International Business Machines Corporation | Computer implemented method for automatically controlling selection of a grid provider for a grid job |
| US7562035B2 (en) * | 2005-01-12 | 2009-07-14 | International Business Machines Corporation | Automating responses by grid providers to bid requests indicating criteria for a grid job |
| US7546582B2 (en) | 2005-03-30 | 2009-06-09 | International Business Machines Corporation | Managing dynamic configuration data for producer components in a computer infrastructure |
| US8572516B1 (en) | 2005-08-24 | 2013-10-29 | Jpmorgan Chase Bank, N.A. | System and method for controlling a screen saver |
| US7499933B1 (en) | 2005-11-12 | 2009-03-03 | Jpmorgan Chase Bank, N.A. | System and method for managing enterprise application configuration |
| US8181016B1 (en) | 2005-12-01 | 2012-05-15 | Jpmorgan Chase Bank, N.A. | Applications access re-certification system |
| US7913249B1 (en) | 2006-03-07 | 2011-03-22 | Jpmorgan Chase Bank, N.A. | Software installation checker |
| US7895565B1 (en) | 2006-03-15 | 2011-02-22 | Jp Morgan Chase Bank, N.A. | Integrated system and method for validating the functionality and performance of software applications |
| KR100768126B1 (en) * | 2006-03-16 | 2007-10-17 | 주식회사 지오네트 | Sequence of event system for plant |
| US7945907B2 (en) * | 2006-06-14 | 2011-05-17 | Sap Ag | System and method for configuring application programs |
| US7610172B2 (en) | 2006-06-16 | 2009-10-27 | Jpmorgan Chase Bank, N.A. | Method and system for monitoring non-occurring events |
| US9122715B2 (en) | 2006-06-29 | 2015-09-01 | International Business Machines Corporation | Detecting changes in end-user transaction performance and availability caused by changes in transaction server configuration |
| US9086917B1 (en) | 2006-10-17 | 2015-07-21 | Manageiq, Inc. | Registering and accessing virtual systems for use in a managed system |
| US8752045B2 (en) | 2006-10-17 | 2014-06-10 | Manageiq, Inc. | Methods and apparatus for using tags to control and manage assets |
| US8458695B2 (en) | 2006-10-17 | 2013-06-04 | Manageiq, Inc. | Automatic optimization for virtual systems |
| US9015703B2 (en) | 2006-10-17 | 2015-04-21 | Manageiq, Inc. | Enforcement of compliance policies in managed virtual systems |
| US8234640B1 (en) | 2006-10-17 | 2012-07-31 | Manageiq, Inc. | Compliance-based adaptations in managed virtual systems |
| US8949826B2 (en) | 2006-10-17 | 2015-02-03 | Managelq, Inc. | Control and management of virtual systems |
| US9038062B2 (en) | 2006-10-17 | 2015-05-19 | Manageiq, Inc. | Registering and accessing virtual systems for use in a managed system |
| US9697019B1 (en) | 2006-10-17 | 2017-07-04 | Manageiq, Inc. | Adapt a virtual machine to comply with system enforced policies and derive an optimized variant of the adapted virtual machine |
| US8234641B2 (en) | 2006-10-17 | 2012-07-31 | Managelq, Inc. | Compliance-based adaptations in managed virtual systems |
| US8949825B1 (en) | 2006-10-17 | 2015-02-03 | Manageiq, Inc. | Enforcement of compliance policies in managed virtual systems |
| US8612971B1 (en) | 2006-10-17 | 2013-12-17 | Manageiq, Inc. | Automatic optimization for virtual systems |
| US8209417B2 (en) * | 2007-03-08 | 2012-06-26 | Oracle International Corporation | Dynamic resource profiles for clusterware-managed resources |
| US7870417B2 (en) * | 2007-04-20 | 2011-01-11 | International Business Machines Corporation | Apparatus, system, and method for adapter card failover |
| US20080263391A1 (en) * | 2007-04-20 | 2008-10-23 | International Business Machines Corporation | Apparatus, System, and Method For Adapter Card Failover |
| US8856360B2 (en) * | 2007-06-22 | 2014-10-07 | Microsoft Corporation | Automatically identifying dynamic internet protocol addresses |
| US20090113408A1 (en) * | 2007-10-30 | 2009-04-30 | Telefonaktiebolaget Lm Ericsson (Publ) | System synchronization in cluster |
| US8407688B2 (en) * | 2007-11-27 | 2013-03-26 | Managelq, Inc. | Methods and apparatus for storing and transmitting historical configuration data associated with information technology assets |
| US8418173B2 (en) | 2007-11-27 | 2013-04-09 | Manageiq, Inc. | Locating an unauthorized virtual machine and bypassing locator code by adjusting a boot pointer of a managed virtual machine in authorized environment |
| US8910128B2 (en) * | 2011-07-19 | 2014-12-09 | Salesforce.Com, Inc. | Methods and apparatus for application performance and capacity analysis |
| US10002041B1 (en) | 2013-02-01 | 2018-06-19 | Jpmorgan Chase Bank, N.A. | System and method for maintaining the health of a machine |
| US9720655B1 (en) | 2013-02-01 | 2017-08-01 | Jpmorgan Chase Bank, N.A. | User interface event orchestration |
| US9088459B1 (en) | 2013-02-22 | 2015-07-21 | Jpmorgan Chase Bank, N.A. | Breadth-first resource allocation system and methods |
| US9619410B1 (en) | 2013-10-03 | 2017-04-11 | Jpmorgan Chase Bank, N.A. | Systems and methods for packet switching |
| GB2518894A (en) | 2013-10-07 | 2015-04-08 | Ibm | A method and a system for operating programs on a computer cluster |
| US9542259B1 (en) | 2013-12-23 | 2017-01-10 | Jpmorgan Chase Bank, N.A. | Automated incident resolution system and method |
| US10248703B2 (en) | 2014-01-08 | 2019-04-02 | Oracle International Corporation | System and method for cluster-wide replication of embedded component configuration |
| US9868054B1 (en) | 2014-02-10 | 2018-01-16 | Jpmorgan Chase Bank, N.A. | Dynamic game deployment |
| EP3613235A4 (en) * | 2017-04-18 | 2020-10-21 | Nokia Solutions and Networks Oy | Priority and locking mechanism for network modules |
| CN112256443B (en) * | 2020-10-14 | 2024-02-06 | 杭州当虹科技股份有限公司 | Redis-based dynamic cluster lock system |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US4958273A (en) * | 1987-08-26 | 1990-09-18 | International Business Machines Corporation | Multiprocessor system architecture with high availability |
| US5598549A (en) * | 1993-06-11 | 1997-01-28 | At&T Global Information Solutions Company | Array storage system for returning an I/O complete signal to a virtual I/O daemon that is separated from software array driver and physical device driver |
| US5612865A (en) * | 1995-06-01 | 1997-03-18 | Ncr Corporation | Dynamic hashing method for optimal distribution of locks within a clustered system |
| US5666486A (en) * | 1995-06-23 | 1997-09-09 | Data General Corporation | Multiprocessor cluster membership manager framework |
-
1997
- 1997-07-07 US US08/888,550 patent/US6003075A/en not_active Expired - Lifetime
-
1998
- 1998-06-10 KR KR1019980021460A patent/KR100297906B1/en not_active IP Right Cessation
- 1998-06-29 CA CA002241840A patent/CA2241840A1/en not_active Abandoned
- 1998-06-30 TW TW087110499A patent/TW406240B/en not_active IP Right Cessation
- 1998-07-01 BR BR9802326-8A patent/BR9802326A/en not_active Application Discontinuation
Also Published As
| Publication number | Publication date |
|---|---|
| US6003075A (en) | 1999-12-14 |
| KR19990013396A (en) | 1999-02-25 |
| KR100297906B1 (en) | 2001-08-07 |
| BR9802326A (en) | 1999-10-19 |
| TW406240B (en) | 2000-09-21 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6003075A (en) | Enqueuing a configuration change in a network cluster and restore a prior configuration in a back up storage in reverse sequence ordered | |
| US20080052327A1 (en) | Secondary Backup Replication Technique for Clusters | |
| JP4307673B2 (en) | Method and apparatus for configuring and managing a multi-cluster computer system | |
| US8230256B1 (en) | Method and apparatus for achieving high availability for an application in a computer cluster | |
| US5822531A (en) | Method and system for dynamically reconfiguring a cluster of computer systems | |
| KR100326982B1 (en) | A highly scalable and highly available cluster system management scheme | |
| US20170031790A1 (en) | Flexible failover policies in high availability computing systems | |
| US8464092B1 (en) | System and method for monitoring an application or service group within a cluster as a resource of another cluster | |
| US7657580B2 (en) | System and method providing virtual applications architecture | |
| US6363497B1 (en) | System for clustering software applications | |
| CA2053344C (en) | Method and system increasing the operational availability of a system of computer programs operating in a distributed system of computers | |
| CA2284376C (en) | Method and apparatus for managing clustered computer systems | |
| US7987394B2 (en) | Method and apparatus for expressing high availability cluster demand based on probability of breach | |
| CN111327467A (en) | Server system, disaster recovery backup method thereof and related equipment | |
| JP2008052407A (en) | Cluster system | |
| US8015432B1 (en) | Method and apparatus for providing computer failover to a virtualized environment | |
| CA2241861C (en) | A scheme to perform event rollup | |
| CN115878361A (en) | Node management method and device for database cluster and electronic equipment | |
| CN114706714A (en) | Method for synchronizing computer memory division snapshots | |
| Corsava et al. | Self-healing intelligent infrastructure for computational clusters | |
| MXPA98005490A (en) | Dynamic changes in configurac | |
| KR20010010293A (en) | Fault management system and Method for recovering fault of the Configuration Management System in the fault tolerant switching control system | |
| PowerHA | IBM Rational ClearCase® support for | |
| Fischer | Implementation of a Disaster Resilient Linux Cluster with Storage Subsystem Based Data Replication | |
| Sakai | Integration of PRIMECLUSTER and Mission- Critical IA Server PRIMEQUEST |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| FZDE | Discontinued |