US20170031790A1 - Flexible failover policies in high availability computing systems - Google Patents
Flexible failover policies in high availability computing systems Download PDFInfo
- Publication number
- US20170031790A1 US20170031790A1 US15/226,725 US201615226725A US2017031790A1 US 20170031790 A1 US20170031790 A1 US 20170031790A1 US 201615226725 A US201615226725 A US 201615226725A US 2017031790 A1 US2017031790 A1 US 2017031790A1
- Authority
- US
- United States
- Prior art keywords
- failover
- resource
- node
- cluster
- script
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/40—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection
-
- 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/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2023—Failover techniques
- G06F11/2033—Failover techniques switching over of hardware resources
-
- 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/16—Error detection or correction of the data by redundancy in hardware
- G06F11/20—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements
- G06F11/202—Error detection or correction of the data by redundancy in hardware using active fault-masking, e.g. by switching out faulty elements or by switching in spare elements where processing functionality is redundant
- G06F11/2023—Failover techniques
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2201/00—Indexing scheme relating to error detection, to error correction, and to monitoring
- G06F2201/805—Real-time
Definitions
- the present invention is related to computer processing, and more particularly to providing flexible failover policies on high availability computer processing systems.
- What is needed is a system and method of increasing the availability of mission critical applications by providing greater failover flexibility in determining the targets for moving resources from a machine that has failed.
- the high availability computing system includes a plurality of servers connected by a first and a second network, wherein the servers communicate with each other to detect server failure and transfer applications to other servers on detecting server failure through a process referred to as “failover”.
- a system for implementing a failover policy includes a cluster infrastructure for managing a plurality of nodes, a high availability infrastructure for providing group and cluster membership services, and a high availability script execution component operative to receive a failover script and at least one failover attribute and operative to produce a failover domain.
- a method for determining a target node for a failover comprises executing a failover script that produces a failover domain, the failover domain having an ordered list of nodes, receiving a failover attribute and based on the failover attribute and failover domain, selecting a node upon which to locate a resource.
- FIG. 1A shows a diagram of the hardware and operating environment in conjunction with which embodiments of the invention may be practiced
- FIG. 1B is a diagram illustrating an exemplary node configuration according to embodiments of the invention.
- FIG. 2 is a flowchart illustrating a method for providing failover policies according to an embodiment of the invention.
- a cluster node is a single computer system. Usually, a cluster node is an individual computer. The term node is also used for brevity. When one node fails, other nodes are left intact and able to operate.
- a pool is the entire set of nodes involved with a group of clusters.
- the group of clusters are usually close together and should always serve a common purpose.
- a replicated database is stored on each node in the pool.
- a cluster is a collection of one or more nodes coupled to each other by networks or other similar interconnections.
- a cluster is identified by a simple name; this name must be unique within the pool.
- a particular node may be a member of only one cluster. All nodes in a cluster are also in the pool: however, all nodes in the pool are not necessarily in the cluster.
- a node membership is the list of nodes in a cluster on which High Availability base software can allocate resource groups.
- a process membership is the list of process instances in a cluster that form a process group. There can be multiple process groups per node.
- a client-server environment is one in which a set of users operate on a set of client systems connected through a network to a set of server systems.
- applications within a client-server system are divided into two components: a client component and a server component. Each component can run on the same of different nodes.
- a process running the client component of the application is called a client; a process running the server component is called a server.
- Clients send requests to servers and collect responses from them. Not all servers can satisfy all requests. For instance, a class of Oracle database servers might be able to satisfy requests regarding the employees of a company, while another class might be able to satisfy requests regarding the company's products.
- Servers that are able to satisfy the same type of requests are said to be providing the same service.
- the time interval between the event of posting a request and the event of receiving a response is called latency.
- Service availability can be defined by the following example. Consider a web service implemented by a set of web servers running on a single system. Assume that the system suffers an operating system failure. After the system is rebooted, the web servers are restarted and clients can connect again. A failure of the servers therefore appears to clients like a long latency.
- a service is said to be unavailable to a client when latencies become greater than a certain threshold, called critical latency. Otherwise, it is available.
- a service is down when it is unavailable to all clients; otherwise, it is up.
- avail(S) 1-downtime/(t′-t) where t′-t is a large time interval, generally a year. For instance, a service which is available 99.99% should have an yearly downtime of about an hour. A service that is available 99.99% or higher is generally called highly available.
- Outages due to maintenance are generally considered less severe. They can be scheduled when clients are less active, for instance, during a weekend. Users can get early notification. Downtime due to maintenance is often called scheduled downtime. On the other hand, failures tend to occur when the servers are working under heavy load, i.e. when most clients are connected. Downtime due to failures is often called unscheduled downtime. Some time service availability is measured considering only unscheduled downtime.
- System availability is computed similarly to service availability.
- the downtime is obtained by multiplying the average number of system failures (OS crashes, HW failures, . . . ) by the average repair time.
- a resource is a single physical or logical entity that provides a service to clients or other resources.
- a resource can be a single disk volume, a particular network address, or an application such as a web server.
- a resource is generally available for use over time on two or more nodes in a cluster, although it can be allocated to only one node at any given time.
- Resources are identified by a resource name and a resource type.
- One resource can be dependent on one or more other resources: If so, it will not be able to start (that is, be made available for use) unless the dependent resources are also started.
- Dependent resources must be part of the same resource group and are identified in a resource dependency list.
- a resource name identifies a specific instance of a resource type.
- a resource name must be unique for a given resource type.
- a resource type is a particular class of resource. All of the resources in a particular resource type can be handled in the same way for the purposes of failover. Every resource is an instance of exactly one resource type.
- a resource type is identified by a simple name: this name must be unique within the cluster.
- a resource type can be defined for a specific node, or It. can be defined for an entire cluster.
- a resource type that is defined for a specific node overrides a cluster-wide resource type definition with the same name: this allows an-individual node to override global settings from a cluster-wide resource type definition.
- a resource type can be dependent on one or more other resource types. If such a. dependency exists, at least one instance of each of the dependent resource types must be defined.
- a resource type named Netscape_web might have resource type dependencies on resource types named IP_address and volume. If a resource named web is defined with the Netscape_web resource type, then the resource group containing web must also contain at least one resource of the type IP_address and one resource of the type volume.
- predefined resource types are provided. However, a user can create additional resource types.
- a resource group is a collection of interdependent resources.
- a resource group is identified by a simple name: this name must be unique within a duster.
- Table 1 shows an example of the resources for a resource group named WebGroup.
- a resource group is the unit of failover for the High Availability base software.
- resource groups cannot overlap: that is two resource groups cannot contain the same resource.
- a resource dependency list is a list of resources upon which a resource depends. Each resource instance must have resource dependencies that satisfy its resource type dependencies before it can be added to a resource group.
- a resource type dependency list is a list of resource types upon which a resource type depends.
- the filesystem resource type depends upon the volume resource type
- the Netscape_web resource type depends upon the filesystem and IP_address resource types.
- a failover is the process of allocating a resource group (or application) to another node, according to a failover policy
- a failover may be triggered by the failure of a resource, a change in the node membership (such as when a node fails or starts), or a manual request by the administrator.
- a failover policy is the method used by High Availability base software to determine the destination node of a failover.
- a failover policy consists of the following:
- the administrator can configure a failover policy for each resource group.
- a failover policy name must be unique within the pool.
- a failover domain is the ordered list of nodes on which a given resource group can be allocated.
- the nodes listed in the failover domain must be within the same cluster. However, the failover domain does not have to include every node in the cluster.
- the administrator defines the initial failover domain when creating a failover policy. This list is transformed into a run-time failover domain by the failover script.
- High Availability base software uses the run-time failover domain along with failover attributes and the node membership to determine the node on which a resource group should reside.
- High Availability base software stores the run-time failover domain and uses it as input to the next failover script invocation.
- the initial and run-time failover domains may be identical.
- High Availability base software allocates a given resource group to the first node listed in the run-time failover domain that is also in the node membership: the point at which this allocation takes place is affected by the failover attributes.
- a failover attribute is a string that affects the allocation of a resource group in a cluster.
- the administrator must specify system attributes (such as Auto_Failback or Controlled_Failback) and can optionally supply site-specific attributes.
- a failover script is a shell script that generates a run-time failover domain and returns it to the High Availability base software process.
- the High Availability base software process applies the failover attributes and then selects the first node in the returned failover domain that is also in the current node membership.
- the action scripts are the set of scripts that determine how a resource is started, monitored, and stopped. Typically, there will be a set of action scripts specified for each resource type.
- HA Highly Available services
- a multi-server application using built-in or highly available services can directly provide HA services.
- a single-server application layered on top of multi-server highly available system services can provide equivalent HA services.
- a single-server application may depend on a special application which uses the multi-server application discussed above.
- FIG. 1A illustrates an exemplary environment for providing HA services.
- the environment 10 includes nodes 20 , clients 24 , and database 26 , all communicably coupled by a network 22 .
- Each of nodes 20 . 1 - 20 . 5 are computer systems comprising hardware and software and can provide services to clients 24 .
- nodes 20 can also be referred to as servers.
- processes 26 comprise software that provides services to client 24 .
- each of nodes 20 . 1 can be suitably configured to provide high availability services according to the various embodiments of the invention.
- FIG. 1B provides further detail of software layers according to an embodiment of the invention that can be run on nodes 20 to support HA services.
- software running on a node 20 includes cluster infrastructure 12 , HA infrastructure 14 , HA base software 16 , application plug-ins 28 , and processes 26 .
- Cluster infrastructure 12 includes software components for performing the following:
- the cluster software infrastructure includes clusteruster_admin and cluster_control subsystems.
- HA infrastructure 14 provides software components to define clusters, resources, and resource types.
- the HA infrastructure includes the following:
- HA base software 16 provides end-to-end monitoring of services and client in order to determine whether resource load balancing or failover are required.
- HA base software 16 is the IRIS FailSafe product available from Silicon Graphics, Inc.
- HAbase software includes the software required to make the following high-availability services:
- IP addresses (the IP_address resource type)
- application plug-ins 28 comprise software components that provide an interface to convert applications such as processes 26 into high-availability services.
- application plug-ins 26 can include database agents. Each database agent monitors all instances of one type of database.
- database agents comprise the following:
- Processes 26 include software applications that can be configured to provide services. It is not a requirement that any of processes 26 be intrinsically HA services.
- Application plug-ins 18 along with HA base software 16 can be used to turn processes 26 into HA services.
- HA base software 16 can be used to turn processes 26 into HA services.
- the process 26 have the following characteristics: [0088] The application can be easily restarted and monitored. [0089] It should be able to recover from failures as do most client/server software. The failure could be a hardware failure, an operating system failure, or an application failure. If a node crashed and reboots, client/server software should be able to attach again automatically.
- node 20 can include a database (not shown).
- the database can be used to store information including:
- a cluster administration daemon maintains identical databases on each node in the cluster.
- the previous section described an overview of a system for providing high availability services and failover policies for such services.
- This section will provide a description of a method 200 for providing failover policies for high availability services.
- the methods to be performed by the operating environment constitute computer programs made up of computer-executable instructions. Describing the methods by reference to a flowchart enables one skilled in the art to develop such programs including such instructions to carry out the methods on suitable computers (the processor of the computer executing the instructions from computer-readable media).
- the method illustrated in FIG. 2 is inclusive of the acts required to be taken by an operating environment executing an exemplary embodiment of the invention.
- the method 200 begins when a software component, such as HA base software 16 ( FIG. 1A ) executes a failover script for a resource in response to either a failover event such as a node or process failure, or a load balancing event such as a resource bottleneck or processor load (block 202 ).
- the failover script can be programmed in any of a number of languages, include Java, perl, shell (Bourne, C-Shell, Korn shell etc.) or the C programming language. The invention is not limited to a particular programming language. In one embodiment of the invention, the following scripts can be executed:
- start, stop, and exclusive scripts are required for every resource type.
- a monitor script may also be required, but if need be only a return-success function.
- a restart script may be required if the restart mode is set to 1; however, this script may contain only a return-success function.
- the probe script is optional.
- monitor script there are two types of monitoring that may be accomplished in a monitor script:
- the monitoring script can make a simple request and verify that the proper response is received.
- the monitoring script can request a home page, verify that the connection was made, and ignore the resulting home page.
- a simple request such as querying a table can be made.
- a system executing the method receives a failover domain as output from the failover script (block 204 ).
- the failover script can receive an input domain, apply script logic, and provide an output domain.
- the output domain is an ordered list of nodes on which a given resource can be allocated.
- the system receives failover attributes (block 206 ).
- the failover attributes are used by the scripts and by the HA base software to modifying the run-time failover domain used for a specific resource group.
- the method determines a target node for the resource (block 208 ). Once a target node has been determined, the system can cause the resource to start on the target node.
- computer is defined to include any digital or analog data processing unit. Examples include any personal computer, workstation, set top box, mainframe, server, supercomputer, laptop or personal digital assistant capable of embodying the inventions described herein.
- Examples of articles comprising computer readable media are floppy disks, hard drives, CD-ROM or DVD media or any other read-write or read-only memory device.
Abstract
Description
- The present application is a continuation and claims the priority benefit of U.S. patent application Ser. No. 14/288,079 filed May 27, 2014, issuing as U.S. Pat. No. 9,405,640, which is a continuation and claims the priority benefit of U.S. patent application Ser. No. 12/891,390 filed Sep. 27, 2010, now U.S. Pat. No. 8,769,132, which is a continuation and claims the priority benefit of U.S. patent application Ser. No. 09/997,404 filed Nov. 29, 2001, which is a continuation and claims the priority benefit of U.S. patent application Ser. No. 09/811,357 filed Mar. 16, 2001, which claims the priority benefit of U.S. provisional application 60/189,864 filed Mar. 16, 2000, the disclosures of which are incorporated herein by reference.
- A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. The following notice applies to the software and data as described below and in the drawings hereto: Copyright© 2000, 2001 Silicon Graphics Incorporated, All Rights Reserved.
- Field of the Invention
- The present invention is related to computer processing, and more particularly to providing flexible failover policies on high availability computer processing systems.
- Description of the Related Art
- Companies today rely on computers to drive all aspects of their business. Certain business functions can survive intermittent interruptions in service; others cannot.
- To date, attempts to ensure high availability to mission critical applications have relied on two approaches. Applications have been made more available either through the use of specialized fault tolerant hardware or through cumbersome changes to the applications or to the environment in which the applications run. These approaches increase the costs to the organization of running the applications. In addition, certain approaches to making applications more available increase the risk of introducing errors in the underlying data.
- What is needed is a system and method of increasing the availability of mission critical applications by providing greater failover flexibility in determining the targets for moving resources from a machine that has failed.
- To address the problems stated above, and to solve other problems that will become apparent in reading the specification and claims, a high availability computing system and method are described. The high availability computing system includes a plurality of servers connected by a first and a second network, wherein the servers communicate with each other to detect server failure and transfer applications to other servers on detecting server failure through a process referred to as “failover”.
- According to another aspect of the present invention, a system for implementing a failover policy includes a cluster infrastructure for managing a plurality of nodes, a high availability infrastructure for providing group and cluster membership services, and a high availability script execution component operative to receive a failover script and at least one failover attribute and operative to produce a failover domain.
- According to another aspect of the invention, a method for determining a target node for a failover comprises executing a failover script that produces a failover domain, the failover domain having an ordered list of nodes, receiving a failover attribute and based on the failover attribute and failover domain, selecting a node upon which to locate a resource.
-
FIG. 1A shows a diagram of the hardware and operating environment in conjunction with which embodiments of the invention may be practiced; -
FIG. 1B is a diagram illustrating an exemplary node configuration according to embodiments of the invention; and -
FIG. 2 is a flowchart illustrating a method for providing failover policies according to an embodiment of the invention. - In the following detailed description, reference is made to the accompanying drawings which form a part hereof, and in which is shown by way of illustration specific embodiments in which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural changes may be made without departing from the scope of the present invention.
- Some portions of the detailed descriptions which follow are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the ways used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is here, and generally, conceived to be a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussions, it is appreciated that throughout the present invention, discussions utilizing terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar computing device, that manipulates and transforms data represented as physical (e.g., electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
- A number of computing terms will be used throughout this specification. In this specification, a cluster node is a single computer system. Usually, a cluster node is an individual computer. The term node is also used for brevity. When one node fails, other nodes are left intact and able to operate.
- A pool is the entire set of nodes involved with a group of clusters. The group of clusters are usually close together and should always serve a common purpose. A replicated database is stored on each node in the pool.
- A cluster is a collection of one or more nodes coupled to each other by networks or other similar interconnections. A cluster is identified by a simple name; this name must be unique within the pool. A particular node may be a member of only one cluster. All nodes in a cluster are also in the pool: however, all nodes in the pool are not necessarily in the cluster.
- A node membership is the list of nodes in a cluster on which High Availability base software can allocate resource groups.
- A process membership is the list of process instances in a cluster that form a process group. There can be multiple process groups per node.
- A client-server environment is one in which a set of users operate on a set of client systems connected through a network to a set of server systems. Often, applications within a client-server system are divided into two components: a client component and a server component. Each component can run on the same of different nodes. A process running the client component of the application is called a client; a process running the server component is called a server.
- Clients send requests to servers and collect responses from them. Not all servers can satisfy all requests. For instance, a class of Oracle database servers might be able to satisfy requests regarding the employees of a company, while another class might be able to satisfy requests regarding the company's products.
- Servers that are able to satisfy the same type of requests are said to be providing the same service. The time interval between the event of posting a request and the event of receiving a response is called latency.
- Service availability can be defined by the following example. Consider a web service implemented by a set of web servers running on a single system. Assume that the system suffers an operating system failure. After the system is rebooted, the web servers are restarted and clients can connect again. A failure of the servers therefore appears to clients like a long latency.
- A service is said to be unavailable to a client when latencies become greater than a certain threshold, called critical latency. Otherwise, it is available. A service is down when it is unavailable to all clients; otherwise, it is up. An outage occurs when a service goes down. The outage lasts until the service comes up again. If downtime is the sum of the durations of outages over a certain time interval D=R, a for a certain service S, service availability can be defined as:
- avail(S)=1-downtime/(t′-t) where t′-t is a large time interval, generally a year. For instance, a service which is available 99.99% should have an yearly downtime of about an hour. A service that is available 99.99% or higher is generally called highly available.
- Service outages occur for two reasons: maintenance (e.g. hardware and software upgrades) and failures (e.g. hardware failures, OS crashes).
- Outages due to maintenance are generally considered less severe. They can be scheduled when clients are less active, for instance, during a weekend. Users can get early notification. Downtime due to maintenance is often called scheduled downtime. On the other hand, failures tend to occur when the servers are working under heavy load, i.e. when most clients are connected. Downtime due to failures is often called unscheduled downtime. Some time service availability is measured considering only unscheduled downtime.
- Vendors often provide figures for system availability. System availability is computed similarly to service availability. The downtime is obtained by multiplying the average number of system failures (OS crashes, HW failures, . . . ) by the average repair time.
- Consider a service whose servers are distributed on a set of N (where N>1) nodes in a cluster. For the service to be unavailable, all of the N nodes must fail at the same time. Since most of system failures are statistically independent, the probability of such an event is pN, where p is the probability of a failure of a single system. For example, given a cluster of 2 nodes with availability of 99.7% for each node, at any given time, there is a 0.3% or 0.003 probability that a node is unavailable. The probability of both nodes being unavailable at the same time is 0.003 2=0.000009 or 0.0009%. The cluster as a whole therefore has a system availability of 99.9991% or (1-0.000009). System availability of a cluster is high enough to allow the deployment of highly available services.
- A resource is a single physical or logical entity that provides a service to clients or other resources. For example, a resource can be a single disk volume, a particular network address, or an application such as a web server. A resource is generally available for use over time on two or more nodes in a cluster, although it can be allocated to only one node at any given time.
- Resources are identified by a resource name and a resource type. One resource can be dependent on one or more other resources: If so, it will not be able to start (that is, be made available for use) unless the dependent resources are also started. Dependent resources must be part of the same resource group and are identified in a resource dependency list.
- A resource name identifies a specific instance of a resource type. A resource name must be unique for a given resource type.
- A resource type is a particular class of resource. All of the resources in a particular resource type can be handled in the same way for the purposes of failover. Every resource is an instance of exactly one resource type.
- A resource type is identified by a simple name: this name must be unique within the cluster. A resource type can be defined for a specific node, or It. can be defined for an entire cluster. A resource type that is defined for a specific node overrides a cluster-wide resource type definition with the same name: this allows an-individual node to override global settings from a cluster-wide resource type definition.
- Like resources, a resource type can be dependent on one or more other resource types. If such a. dependency exists, at least one instance of each of the dependent resource types must be defined. For example, a resource type named Netscape_web might have resource type dependencies on resource types named IP_address and volume. If a resource named web is defined with the Netscape_web resource type, then the resource group containing web must also contain at least one resource of the type IP_address and one resource of the type volume.
- In one embodiment, predefined resource types are provided. However, a user can create additional resource types.
- A resource group is a collection of interdependent resources. A resource group is identified by a simple name: this name must be unique within a duster. Table 1 shows an example of the resources for a resource group named WebGroup.
-
TABLE 1 Resource Resource Type Vol1 volume lfs1 files ystem 199.10.48.22 IP_address Oracle_DB Application - In some embodiments, if any individual resource in a resource group becomes unavailable for its intended use, then the entire resource group is considered unavailable. In these embodiments, a resource group is the unit of failover for the High Availability base software.
- In some embodiments of the invention, resource groups cannot overlap: that is two resource groups cannot contain the same resource.
- A resource dependency list is a list of resources upon which a resource depends. Each resource instance must have resource dependencies that satisfy its resource type dependencies before it can be added to a resource group.
- A resource type dependency list is a list of resource types upon which a resource type depends. For example, the filesystem resource type depends upon the volume resource type, and the Netscape_web resource type depends upon the filesystem and IP_address resource types.
- For example, suppose a file system instance/fs1 is mounted on volume/vol1. Before/fs1 can be added to a resource group. /fs1 must be defined to depend on/vol1. the High Availability base software only knows that a file system instance must have one volume instance in its dependency list. This requirement is inferred from the resource type dependency list.
- A failover is the process of allocating a resource group (or application) to another node, according to a failover policy A failover may be triggered by the failure of a resource, a change in the node membership (such as when a node fails or starts), or a manual request by the administrator.
- A failover policy is the method used by High Availability base software to determine the destination node of a failover. A failover policy consists of the following:
- Failover domain
- Failover attributes
- Failover script
- The administrator can configure a failover policy for each resource group. A failover policy name must be unique within the pool.
- A failover domain is the ordered list of nodes on which a given resource group can be allocated. The nodes listed in the failover domain must be within the same cluster. However, the failover domain does not have to include every node in the cluster.
- The administrator defines the initial failover domain when creating a failover policy. This list is transformed into a run-time failover domain by the failover script. High Availability base software uses the run-time failover domain along with failover attributes and the node membership to determine the node on which a resource group should reside. High Availability base software stores the run-time failover domain and uses it as input to the next failover script invocation. Depending on the run-time conditions and contents of the failover script, the initial and run-time failover domains may be identical.
- In general, High Availability base software allocates a given resource group to the first node listed in the run-time failover domain that is also in the node membership: the point at which this allocation takes place is affected by the failover attributes.
- A failover attribute is a string that affects the allocation of a resource group in a cluster. The administrator must specify system attributes (such as Auto_Failback or Controlled_Failback) and can optionally supply site-specific attributes.
- A failover script is a shell script that generates a run-time failover domain and returns it to the High Availability base software process. The High Availability base software process applies the failover attributes and then selects the first node in the returned failover domain that is also in the current node membership.
- The action scripts are the set of scripts that determine how a resource is started, monitored, and stopped. Typically, there will be a set of action scripts specified for each resource type.
- The following is the complete set of action scripts that can be specified for each resource:
-
- probe, which verifies that the resource is configured on a server
- exclusive, which verifies that the resource is not already running
- start, which starts the resource
- stop, which stops the resource
- monitor, which monitors the resource
- restart, which restarts the resource on the same server after a monitoring failure occurs
- Highly Available (HA) services can be provided in two ways. First, a multi-server application using built-in or highly available services, can directly provide HA services. In the alternative, a single-server application layered on top of multi-server highly available system services can provide equivalent HA services. In other words, a single-server application may depend on a special application which uses the multi-server application discussed above.
-
FIG. 1A illustrates an exemplary environment for providing HA services. As shown, theenvironment 10 includesnodes 20, clients 24, anddatabase 26, all communicably coupled by anetwork 22. Each of nodes 20.1-20.5 are computer systems comprising hardware and software and can provide services to clients 24. Thusnodes 20 can also be referred to as servers. Specifically, processes 26 comprise software that provides services to client 24. Moreover, each of nodes 20.1 can be suitably configured to provide high availability services according to the various embodiments of the invention. -
FIG. 1B provides further detail of software layers according to an embodiment of the invention that can be run onnodes 20 to support HA services. As illustrated, software running on anode 20 includescluster infrastructure 12,HA infrastructure 14,HA base software 16, application plug-ins 28, and processes 26. -
Cluster infrastructure 12 includes software components for performing the following: - Node logging
- Cluster administration
- Node definition
- In one embodiment, the cluster software infrastructure includes clusteruster_admin and cluster_control subsystems.
HA infrastructure 14 provides software components to define clusters, resources, and resource types. In one embodiment, the HA infrastructure includes the following: -
- Cluster membership daemon. Provides the list of nodes, called node membership, available to the cluster.
- Group membership daemon. Provides group membership and reliable communication services In the presence of failures to
HA base software 12 processes. - Start daemon. Starts HA base software daemons and restarts them on failures.
- System resource manager daemon. Manages resources, resource groups and resource types. Executes action scripts for resources.
- Interface agent daemon. Monitors the local node's network Interfaces.
- Further details on the
cluster infrastructure 12 andHA infrastructure 14 can be found in the cofiled, copending, U.S. patent application Ser. No. 09/811,158 entitled “MAINTAINING MEMBERSHIP IN HIGH AVAILABILITY COMPUTING SYSTEMS”, previously incorporated by reference. -
HA base software 16 provides end-to-end monitoring of services and client in order to determine whether resource load balancing or failover are required. In one embodiment,HA base software 16 is the IRIS FailSafe product available from Silicon Graphics, Inc. In this embodiment, HAbase software includes the software required to make the following high-availability services: - IP addresses (the IP_address resource type)
- XLV logical volumes (the volume resource type)
- XFS file systems (the filesystem resource type)
- MAC addresses (the MAC_address resource type)
- In one embodiment of the invention, application plug-ins 28 comprise software components that provide an interface to convert applications such as
processes 26 into high-availability services. For example, application plug-ins 26 can include database agents. Each database agent monitors all instances of one type of database. In one embodiment, database agents comprise the following: - IRIS FailSafe Oracle
- IRIS FailSafe INFORMIX
- IRIS FailSafe Netscape Web
- IRIS FailSafe Mediabase
-
Processes 26 include software applications that can be configured to provide services. It is not a requirement that any ofprocesses 26 be intrinsically HA services. Application plug-ins 18, along withHA base software 16 can be used to turnprocesses 26 into HA services. In order for a plug-in to be used to turn aprocess 26 into an HA application, it is desirable that theprocess 26 have the following characteristics: [0088] The application can be easily restarted and monitored. [0089] It should be able to recover from failures as do most client/server software. The failure could be a hardware failure, an operating system failure, or an application failure. If a node crashed and reboots, client/server software should be able to attach again automatically. -
- The application must have a start and stop procedure.
- When the resource group fails over, the resources that constitute the resource group are stopped on one node and started on another node, according to the failover script and action scripts.
- The application can be moved from one node to another after failures.
- If the resource has failed, it must still be possible to run the resource stop procedure. In addition, the resource must recover from the failed state when the resource start procedure is executed in another node.
- The application does not depend on knowing the host name. That is, those resources that can be configured to work with an IP address.
- It should be noted that an
application process 26 itself is not modified to make it into a high-availability service. - In addition,
node 20 can include a database (not shown). The database can be used to store information including: - Resources
- Resource types
- Resource groups
- Failover policies
- Nodes
- Clusters
- In one embodiment, a cluster administration daemon (cad) maintains identical databases on each node in the cluster.
- The previous section described an overview of a system for providing high availability services and failover policies for such services. This section will provide a description of a
method 200 for providing failover policies for high availability services. The methods to be performed by the operating environment constitute computer programs made up of computer-executable instructions. Describing the methods by reference to a flowchart enables one skilled in the art to develop such programs including such instructions to carry out the methods on suitable computers (the processor of the computer executing the instructions from computer-readable media). The method illustrated inFIG. 2 is inclusive of the acts required to be taken by an operating environment executing an exemplary embodiment of the invention. - The
method 200 begins when a software component, such as HA base software 16 (FIG. 1A ) executes a failover script for a resource in response to either a failover event such as a node or process failure, or a load balancing event such as a resource bottleneck or processor load (block 202). The failover script can be programmed in any of a number of languages, include Java, perl, shell (Bourne, C-Shell, Korn shell etc.) or the C programming language. The invention is not limited to a particular programming language. In one embodiment of the invention, the following scripts can be executed: -
- [0106] probe, which verifies that the resource is configured on a node
- exclusive, which verifies that the resource is not already running
- start, which starts the resource
- stop, which stops the resource
- monitor, which monitors the resource
- restart, which restarts the resource on the same node when a monitoring failure occurs
- It should be noted that in some embodiments, the start, stop, and exclusive scripts are required for every resource type. A monitor script may also be required, but if need be only a return-success function. A restart script may be required if the restart mode is set to 1; however, this script may contain only a return-success function. The probe script is optional.
- In some embodiments, there are two types of monitoring that may be accomplished in a monitor script:
-
- Is the resource present?
- Is the resource responding?
- For a client-node resource that follows a protocol, the monitoring script can make a simple request and verify that the proper response is received. For a web node, the monitoring script can request a home page, verify that the connection was made, and ignore the resulting home page. For a database, a simple request such as querying a table can be made.
- Next, a system executing the method receives a failover domain as output from the failover script (block 204). The failover script can receive an input domain, apply script logic, and provide an output domain. The output domain is an ordered list of nodes on which a given resource can be allocated.
- Next, the system receives failover attributes (block 206). The failover attributes are used by the scripts and by the HA base software to modifying the run-time failover domain used for a specific resource group. Based on the failover domain and attributes, the method determines a target node for the resource (block 208). Once a target node has been determined, the system can cause the resource to start on the target node.
- In the above discussion and in the attached appendices, the term “computer” is defined to include any digital or analog data processing unit. Examples include any personal computer, workstation, set top box, mainframe, server, supercomputer, laptop or personal digital assistant capable of embodying the inventions described herein.
- Examples of articles comprising computer readable media are floppy disks, hard drives, CD-ROM or DVD media or any other read-write or read-only memory device.
- Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement which is calculated to achieve the same purpose may be substituted for the specific embodiment shown. This application is intended to cover any adaptations or variations of the present invention. Therefore, it is intended that this invention be limited only by the claims and the equivalents thereof.
Claims (1)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/226,725 US20170031790A1 (en) | 2000-03-16 | 2016-08-02 | Flexible failover policies in high availability computing systems |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US18986400P | 2000-03-16 | 2000-03-16 | |
US81135701A | 2001-03-16 | 2001-03-16 | |
US09/997,404 US20020198996A1 (en) | 2000-03-16 | 2001-11-29 | Flexible failover policies in high availability computing systems |
US12/891,390 US8769132B2 (en) | 2000-03-16 | 2010-09-27 | Flexible failover policies in high availability computing systems |
US14/288,079 US9405640B2 (en) | 2000-03-16 | 2014-05-27 | Flexible failover policies in high availability computing systems |
US15/226,725 US20170031790A1 (en) | 2000-03-16 | 2016-08-02 | Flexible failover policies in high availability computing systems |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/288,079 Continuation US9405640B2 (en) | 2000-03-16 | 2014-05-27 | Flexible failover policies in high availability computing systems |
Publications (1)
Publication Number | Publication Date |
---|---|
US20170031790A1 true US20170031790A1 (en) | 2017-02-02 |
Family
ID=46278520
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/997,404 Abandoned US20020198996A1 (en) | 2000-03-16 | 2001-11-29 | Flexible failover policies in high availability computing systems |
US12/891,390 Expired - Fee Related US8769132B2 (en) | 2000-03-16 | 2010-09-27 | Flexible failover policies in high availability computing systems |
US14/288,079 Expired - Lifetime US9405640B2 (en) | 2000-03-16 | 2014-05-27 | Flexible failover policies in high availability computing systems |
US15/226,725 Abandoned US20170031790A1 (en) | 2000-03-16 | 2016-08-02 | Flexible failover policies in high availability computing systems |
Family Applications Before (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/997,404 Abandoned US20020198996A1 (en) | 2000-03-16 | 2001-11-29 | Flexible failover policies in high availability computing systems |
US12/891,390 Expired - Fee Related US8769132B2 (en) | 2000-03-16 | 2010-09-27 | Flexible failover policies in high availability computing systems |
US14/288,079 Expired - Lifetime US9405640B2 (en) | 2000-03-16 | 2014-05-27 | Flexible failover policies in high availability computing systems |
Country Status (1)
Country | Link |
---|---|
US (4) | US20020198996A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9886508B2 (en) | 2006-02-15 | 2018-02-06 | Sony Interactive Entertainment America Llc | Systems and methods for server management |
Families Citing this family (57)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020198996A1 (en) * | 2000-03-16 | 2002-12-26 | Padmanabhan Sreenivasan | Flexible failover policies in high availability computing systems |
US7137040B2 (en) * | 2003-02-12 | 2006-11-14 | International Business Machines Corporation | Scalable method of continuous monitoring the remotely accessible resources against the node failures for very large clusters |
US20040163007A1 (en) * | 2003-02-19 | 2004-08-19 | Kazem Mirkhani | Determining a quantity of lost units resulting from a downtime of a software application or other computer-implemented system |
US20050036483A1 (en) * | 2003-08-11 | 2005-02-17 | Minoru Tomisaka | Method and system for managing programs for web service system |
US8892702B2 (en) * | 2003-09-30 | 2014-11-18 | International Business Machines Corporation | Policy driven autonomic computing-programmatic policy definitions |
US7451201B2 (en) * | 2003-09-30 | 2008-11-11 | International Business Machines Corporation | Policy driven autonomic computing-specifying relationships |
US7533173B2 (en) * | 2003-09-30 | 2009-05-12 | International Business Machines Corporation | Policy driven automation - specifying equivalent resources |
CN1302412C (en) * | 2003-11-11 | 2007-02-28 | 联想(北京)有限公司 | Computer group system and its operation managing method |
US20050132379A1 (en) * | 2003-12-11 | 2005-06-16 | Dell Products L.P. | Method, system and software for allocating information handling system resources in response to high availability cluster fail-over events |
US7734750B2 (en) | 2003-12-19 | 2010-06-08 | International Business Machines Corporation | Real-time feedback for policies for computing system management |
US20050259572A1 (en) * | 2004-05-19 | 2005-11-24 | Esfahany Kouros H | Distributed high availability system and method |
US20060036894A1 (en) * | 2004-07-29 | 2006-02-16 | International Business Machines Corporation | Cluster resource license |
US7451347B2 (en) * | 2004-10-08 | 2008-11-11 | Microsoft Corporation | Failover scopes for nodes of a computer cluster |
US7757116B2 (en) * | 2007-04-04 | 2010-07-13 | Vision Solutions, Inc. | Method and system for coordinated multiple cluster failover |
US7669080B2 (en) * | 2007-08-16 | 2010-02-23 | International Business Machines Corporation | Reducing likelihood of data loss during failovers in high-availability systems |
US7925917B1 (en) | 2008-04-03 | 2011-04-12 | United Services Automobile Association (Usaa) | Systems and methods for enabling failover support with multiple backup data storage structures |
US9454444B1 (en) * | 2009-03-19 | 2016-09-27 | Veritas Technologies Llc | Using location tracking of cluster nodes to avoid single points of failure |
CN101854373B (en) * | 2009-04-01 | 2013-10-09 | 华为技术有限公司 | Target switching method, server node and colony system |
US8055933B2 (en) * | 2009-07-21 | 2011-11-08 | International Business Machines Corporation | Dynamic updating of failover policies for increased application availability |
KR101585435B1 (en) * | 2009-09-25 | 2016-01-18 | 삼성전자 주식회사 | Intelligent network system and control method the same |
US8438573B2 (en) * | 2010-01-15 | 2013-05-07 | Oracle International Corporation | Dependency on a resource type |
US9069619B2 (en) * | 2010-01-15 | 2015-06-30 | Oracle International Corporation | Self-testable HA framework library infrastructure |
US20110179173A1 (en) * | 2010-01-15 | 2011-07-21 | Carol Colrain | Conditional dependency in a computing cluster |
US9098334B2 (en) * | 2010-01-15 | 2015-08-04 | Oracle International Corporation | Special values in oracle clusterware resource profiles |
US9207987B2 (en) * | 2010-01-15 | 2015-12-08 | Oracle International Corporation | Dispersion dependency in oracle clusterware |
US8583798B2 (en) * | 2010-01-15 | 2013-11-12 | Oracle International Corporation | Unidirectional resource and type dependencies in oracle clusterware |
US8949425B2 (en) | 2010-01-15 | 2015-02-03 | Oracle International Corporation | “Local resource” type as a way to automate management of infrastructure resources in oracle clusterware |
US8448014B2 (en) * | 2010-04-23 | 2013-05-21 | International Business Machines Corporation | Self-healing failover using a repository and dependency management system |
US8738961B2 (en) | 2010-08-17 | 2014-05-27 | International Business Machines Corporation | High-availability computer cluster with failover support based on a resource map |
US9424152B1 (en) * | 2012-10-17 | 2016-08-23 | Veritas Technologies Llc | Techniques for managing a disaster recovery failover policy |
US20140380300A1 (en) * | 2013-06-25 | 2014-12-25 | Bank Of America Corporation | Dynamic configuration framework |
KR20150028077A (en) * | 2013-09-05 | 2015-03-13 | 에스케이하이닉스 주식회사 | System for fail-over of semiconductor equipment sever and method the same |
US20150100826A1 (en) * | 2013-10-03 | 2015-04-09 | Microsoft Corporation | Fault domains on modern hardware |
CN103577235A (en) * | 2013-11-14 | 2014-02-12 | 中安消技术有限公司 | Software deploying method, deploying server, computer to be deployed and system |
US10402460B1 (en) | 2014-09-08 | 2019-09-03 | Amazon Technologies, Inc. | Contextual card generation and delivery |
US9836363B2 (en) * | 2014-09-30 | 2017-12-05 | Microsoft Technology Licensing, Llc | Semi-automatic failover |
US10275326B1 (en) * | 2014-10-31 | 2019-04-30 | Amazon Technologies, Inc. | Distributed computing system failure detection |
US9785480B2 (en) * | 2015-02-12 | 2017-10-10 | Netapp, Inc. | Load balancing and fault tolerant service in a distributed data system |
US9811345B2 (en) * | 2015-04-16 | 2017-11-07 | Lenovo Enterprise Solutions (Singapore) Pte. Ltd. | Utilizing computing resources under a disabled processor node without fully enabling the disabled processor node |
US10069688B2 (en) | 2016-03-07 | 2018-09-04 | International Business Machines Corporation | Dynamically assigning, by functional domain, separate pairs of servers to primary and backup service processor modes within a grouping of servers |
CN106506233A (en) * | 2016-12-01 | 2017-03-15 | 郑州云海信息技术有限公司 | A kind of automatic deployment Hadoop clusters and the method for flexible working node |
US10552272B2 (en) * | 2016-12-14 | 2020-02-04 | Nutanix, Inc. | Maintaining high availability during N-node failover |
US10496153B2 (en) | 2017-10-27 | 2019-12-03 | EMC IP Holding Company LLC | Method and system for binding chassis and components |
US10719417B2 (en) * | 2018-01-30 | 2020-07-21 | EMC IP Holding Company, LLC | Data protection cluster system supporting multiple data tiers |
US11075925B2 (en) | 2018-01-31 | 2021-07-27 | EMC IP Holding Company LLC | System and method to enable component inventory and compliance in the platform |
US10693722B2 (en) * | 2018-03-28 | 2020-06-23 | Dell Products L.P. | Agentless method to bring solution and cluster awareness into infrastructure and support management portals |
US10754708B2 (en) | 2018-03-28 | 2020-08-25 | EMC IP Holding Company LLC | Orchestrator and console agnostic method to deploy infrastructure through self-describing deployment templates |
US10514907B2 (en) | 2018-03-28 | 2019-12-24 | EMC IP Holding Company LLC | System and method for out-of-the-box solution-level management via logical architecture awareness |
US11086738B2 (en) | 2018-04-24 | 2021-08-10 | EMC IP Holding Company LLC | System and method to automate solution level contextual support |
US10795756B2 (en) | 2018-04-24 | 2020-10-06 | EMC IP Holding Company LLC | System and method to predictively service and support the solution |
US11599422B2 (en) | 2018-10-16 | 2023-03-07 | EMC IP Holding Company LLC | System and method for device independent backup in distributed system |
US10949548B2 (en) * | 2018-10-18 | 2021-03-16 | Verizon Patent And Licensing Inc. | Systems and methods for providing multi-node resiliency for blockchain peers |
US10862761B2 (en) | 2019-04-29 | 2020-12-08 | EMC IP Holding Company LLC | System and method for management of distributed systems |
US10574657B1 (en) | 2019-07-18 | 2020-02-25 | Capital One Services, Llc | Automatic transaction processing failover |
US11301557B2 (en) | 2019-07-19 | 2022-04-12 | Dell Products L.P. | System and method for data processing device management |
US11303562B1 (en) | 2021-01-25 | 2022-04-12 | International Business Machines Corporation | Dynamic high-availability architecture |
US11201887B1 (en) * | 2021-03-23 | 2021-12-14 | Lookingglass Cyber Solutions, Inc. | Systems and methods for low latency stateful threat detection and mitigation |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5539883A (en) * | 1991-10-31 | 1996-07-23 | International Business Machines Corporation | Load balancing of network by maintaining in each computer information regarding current load on the computer and load on some other computers in the network |
US5625811A (en) * | 1994-10-31 | 1997-04-29 | International Business Machines Corporation | Method and system for database load balancing |
US6073126A (en) * | 1996-10-04 | 2000-06-06 | Kabushiki Kaisha Toshiba | Multi-computer system capable of abstractly and integrally describing system configuration and control contents |
US20010000801A1 (en) * | 1999-03-22 | 2001-05-03 | Miller Paul J. | Hydrophilic sleeve |
US20010008019A1 (en) * | 1998-04-17 | 2001-07-12 | John D. Vert | Method and system for transparently failing over application configuration information in a server cluster |
US6351747B1 (en) * | 1999-04-12 | 2002-02-26 | Multex.Com, Inc. | Method and system for providing data to a user based on a user's query |
Family Cites Families (62)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4769772A (en) | 1985-02-28 | 1988-09-06 | Honeywell Bull, Inc. | Automated query optimization method using both global and parallel local optimizations for materialization access planning for distributed databases |
US5187787B1 (en) * | 1989-07-27 | 1996-05-07 | Teknekron Software Systems Inc | Apparatus and method for providing decoupling of data exchange details for providing high performance communication between software processes |
US5339392A (en) * | 1989-07-27 | 1994-08-16 | Risberg Jeffrey S | Apparatus and method for creation of a user definable video displayed document showing changes in real time data |
US5396635A (en) * | 1990-06-01 | 1995-03-07 | Vadem Corporation | Power conservation apparatus having multiple power reduction levels dependent upon the activity of the computer system |
JPH04271454A (en) * | 1991-02-27 | 1992-09-28 | Toshiba Corp | Loosely-coupled computer system |
US5504894A (en) * | 1992-04-30 | 1996-04-02 | International Business Machines Corporation | Workload manager for achieving transaction class response time goals in a multiprocessing system |
JP3746785B2 (en) * | 1993-07-28 | 2006-02-15 | 3コム コーポレイション | Network station with multiple network addresses |
US5513314A (en) * | 1995-01-27 | 1996-04-30 | Auspex Systems, Inc. | Fault tolerant NFS server system and mirroring protocol |
US6003030A (en) * | 1995-06-07 | 1999-12-14 | Intervu, Inc. | System and method for optimized storage and retrieval of data on a distributed computer network |
US6047323A (en) * | 1995-10-19 | 2000-04-04 | Hewlett-Packard Company | Creation and migration of distributed streams in clusters of networked computers |
US5864854A (en) * | 1996-01-05 | 1999-01-26 | Lsi Logic Corporation | System and method for maintaining a shared cache look-up table |
US5862348A (en) * | 1996-02-09 | 1999-01-19 | Citrix Systems, Inc. | Method and apparatus for connecting a client node to a server node based on load levels |
US5805785A (en) * | 1996-02-27 | 1998-09-08 | International Business Machines Corporation | Method for monitoring and recovery of subsystems in a distributed/clustered system |
US5778187A (en) * | 1996-05-09 | 1998-07-07 | Netcast Communications Corp. | Multicasting method and apparatus |
US5852724A (en) * | 1996-06-18 | 1998-12-22 | Veritas Software Corp. | System and method for "N" primary servers to fail over to "1" secondary server |
US5867494A (en) * | 1996-11-18 | 1999-02-02 | Mci Communication Corporation | System, method and article of manufacture with integrated video conferencing billing in a communication system architecture |
US6421726B1 (en) * | 1997-03-14 | 2002-07-16 | Akamai Technologies, Inc. | System and method for selection and retrieval of diverse types of video data on a computer network |
US6189111B1 (en) * | 1997-03-28 | 2001-02-13 | Tandem Computers Incorporated | Resource harvesting in scalable, fault tolerant, single system image clusters |
US5941999A (en) * | 1997-03-31 | 1999-08-24 | Sun Microsystems | Method and system for achieving high availability in networked computer systems |
US5987621A (en) * | 1997-04-25 | 1999-11-16 | Emc Corporation | Hardware and software failover services for a file server |
AU7149498A (en) | 1997-04-25 | 1998-11-24 | Symbios, Inc. | Redundant server failover in networked environment |
US6292905B1 (en) * | 1997-05-13 | 2001-09-18 | Micron Technology, Inc. | Method for providing a fault tolerant network using distributed server processes to remap clustered network resources to other servers during server failure |
US6199110B1 (en) * | 1997-05-30 | 2001-03-06 | Oracle Corporation | Planned session termination for clients accessing a resource through a server |
JP3901806B2 (en) * | 1997-09-25 | 2007-04-04 | 富士通株式会社 | Information management system and secondary server |
US5999712A (en) * | 1997-10-21 | 1999-12-07 | Sun Microsystems, Inc. | Determining cluster membership in a distributed computer system |
US6173420B1 (en) * | 1997-10-31 | 2001-01-09 | Oracle Corporation | Method and apparatus for fail safe configuration |
US6279032B1 (en) * | 1997-11-03 | 2001-08-21 | Microsoft Corporation | Method and system for quorum resource arbitration in a server cluster |
US6178529B1 (en) * | 1997-11-03 | 2001-01-23 | Microsoft Corporation | Method and system for resource monitoring of disparate resources in a server cluster |
US6145089A (en) * | 1997-11-10 | 2000-11-07 | Legato Systems, Inc. | Server fail-over system |
US6185695B1 (en) * | 1998-04-09 | 2001-02-06 | Sun Microsystems, Inc. | Method and apparatus for transparent server failover for highly available objects |
US6243825B1 (en) * | 1998-04-17 | 2001-06-05 | Microsoft Corporation | Method and system for transparently failing over a computer name in a server cluster |
US6157955A (en) * | 1998-06-15 | 2000-12-05 | Intel Corporation | Packet processing system including a policy engine having a classification unit |
US6108703A (en) * | 1998-07-14 | 2000-08-22 | Massachusetts Institute Of Technology | Global hosting system |
US6266781B1 (en) * | 1998-07-20 | 2001-07-24 | Academia Sinica | Method and apparatus for providing failure detection and recovery with predetermined replication style for distributed applications in a network |
JP3859369B2 (en) * | 1998-09-18 | 2006-12-20 | 株式会社東芝 | Message relay apparatus and method |
US6263433B1 (en) * | 1998-09-30 | 2001-07-17 | Ncr Corporation | Provision of continuous database service and scalable query performance using active redundant copies |
US6496941B1 (en) * | 1998-12-29 | 2002-12-17 | At&T Corp. | Network disaster recovery and analysis tool |
US6473396B1 (en) * | 1999-01-04 | 2002-10-29 | Cisco Technology, Inc. | Use of logical addresses to implement module redundancy |
US6438705B1 (en) * | 1999-01-29 | 2002-08-20 | International Business Machines Corporation | Method and apparatus for building and managing multi-clustered computer systems |
US6438704B1 (en) * | 1999-03-25 | 2002-08-20 | International Business Machines Corporation | System and method for scheduling use of system resources among a plurality of limited users |
US6745241B1 (en) * | 1999-03-31 | 2004-06-01 | International Business Machines Corporation | Method and system for dynamic addition and removal of multiple network names on a single server |
US6442685B1 (en) * | 1999-03-31 | 2002-08-27 | International Business Machines Corporation | Method and system for multiple network names of a single server |
US6532494B1 (en) * | 1999-05-28 | 2003-03-11 | Oracle International Corporation | Closed-loop node membership monitor for network clusters |
US6539494B1 (en) * | 1999-06-17 | 2003-03-25 | Art Technology Group, Inc. | Internet server session backup apparatus |
US6647430B1 (en) * | 1999-07-30 | 2003-11-11 | Nortel Networks Limited | Geographically separated totem rings |
US6625152B1 (en) | 1999-10-13 | 2003-09-23 | Cisco Technology, Inc. | Methods and apparatus for transferring data using a filter index |
US6487622B1 (en) * | 1999-10-28 | 2002-11-26 | Ncr Corporation | Quorum arbitrator for a high availability system |
US6892317B1 (en) * | 1999-12-16 | 2005-05-10 | Xerox Corporation | Systems and methods for failure prediction, diagnosis and remediation using data acquisition and feedback for a distributed electronic system |
US6564336B1 (en) * | 1999-12-29 | 2003-05-13 | General Electric Company | Fault tolerant database for picture archiving and communication systems |
US6594786B1 (en) * | 2000-01-31 | 2003-07-15 | Hewlett-Packard Development Company, Lp | Fault tolerant high availability meter |
US6636982B1 (en) * | 2000-03-03 | 2003-10-21 | International Business Machines Corporation | Apparatus and method for detecting the reset of a node in a cluster computer system |
US7627694B2 (en) * | 2000-03-16 | 2009-12-01 | Silicon Graphics, Inc. | Maintaining process group membership for node clusters in high availability computing systems |
US20020198996A1 (en) * | 2000-03-16 | 2002-12-26 | Padmanabhan Sreenivasan | Flexible failover policies in high availability computing systems |
WO2002010944A1 (en) * | 2000-08-01 | 2002-02-07 | Qwest Communications International Inc. | Performance modeling, fault management and repair in a xdsl network |
US6857082B1 (en) * | 2000-11-21 | 2005-02-15 | Unisys Corporation | Method for providing a transition from one server to another server clustered together |
US6785678B2 (en) * | 2000-12-21 | 2004-08-31 | Emc Corporation | Method of improving the availability of a computer clustering system through the use of a network medium link state function |
US6952766B2 (en) * | 2001-03-15 | 2005-10-04 | International Business Machines Corporation | Automated node restart in clustered computer system |
JP4271454B2 (en) | 2002-02-04 | 2009-06-03 | 北興化学工業株式会社 | Method for producing tertiary phosphine bonded with bulky hydrocarbon group |
JP2004062603A (en) | 2002-07-30 | 2004-02-26 | Dainippon Printing Co Ltd | Parallel processing system, server, parallel processing method, program and recording medium |
US7716238B2 (en) * | 2006-02-15 | 2010-05-11 | Sony Computer Entertainment America Inc. | Systems and methods for server management |
US7979460B2 (en) * | 2006-02-15 | 2011-07-12 | Sony Computer Entainment America Inc. | Systems and methods for server management |
US7831620B2 (en) * | 2006-08-31 | 2010-11-09 | International Business Machines Corporation | Managing execution of a query against a partitioned database |
-
2001
- 2001-11-29 US US09/997,404 patent/US20020198996A1/en not_active Abandoned
-
2010
- 2010-09-27 US US12/891,390 patent/US8769132B2/en not_active Expired - Fee Related
-
2014
- 2014-05-27 US US14/288,079 patent/US9405640B2/en not_active Expired - Lifetime
-
2016
- 2016-08-02 US US15/226,725 patent/US20170031790A1/en not_active Abandoned
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5539883A (en) * | 1991-10-31 | 1996-07-23 | International Business Machines Corporation | Load balancing of network by maintaining in each computer information regarding current load on the computer and load on some other computers in the network |
US5625811A (en) * | 1994-10-31 | 1997-04-29 | International Business Machines Corporation | Method and system for database load balancing |
US6073126A (en) * | 1996-10-04 | 2000-06-06 | Kabushiki Kaisha Toshiba | Multi-computer system capable of abstractly and integrally describing system configuration and control contents |
US20010008019A1 (en) * | 1998-04-17 | 2001-07-12 | John D. Vert | Method and system for transparently failing over application configuration information in a server cluster |
US20010000801A1 (en) * | 1999-03-22 | 2001-05-03 | Miller Paul J. | Hydrophilic sleeve |
US6351747B1 (en) * | 1999-04-12 | 2002-02-26 | Multex.Com, Inc. | Method and system for providing data to a user based on a user's query |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9886508B2 (en) | 2006-02-15 | 2018-02-06 | Sony Interactive Entertainment America Llc | Systems and methods for server management |
Also Published As
Publication number | Publication date |
---|---|
US9405640B2 (en) | 2016-08-02 |
US8769132B2 (en) | 2014-07-01 |
US20110214007A1 (en) | 2011-09-01 |
US20020198996A1 (en) | 2002-12-26 |
US20140281675A1 (en) | 2014-09-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20170031790A1 (en) | Flexible failover policies in high availability computing systems | |
US5822531A (en) | Method and system for dynamically reconfiguring a cluster of computer systems | |
US6314526B1 (en) | Resource group quorum scheme for highly scalable and highly available cluster system management | |
US7657536B2 (en) | Application of resource-dependent policies to managed resources in a distributed computing system | |
US6363497B1 (en) | System for clustering software applications | |
US6134673A (en) | Method for clustering software applications | |
US8769478B2 (en) | Aggregation of multiple headless computer entities into a single computer entity group | |
US20020091814A1 (en) | Highly scalable and highly available cluster system management scheme | |
US20020129128A1 (en) | Aggregation of multiple headless computer entities into a single computer entity group | |
US20080172679A1 (en) | Managing Client-Server Requests/Responses for Failover Memory Managment in High-Availability Systems | |
US7987394B2 (en) | Method and apparatus for expressing high availability cluster demand based on probability of breach | |
US7246261B2 (en) | Join protocol for a primary-backup group with backup resources in clustered computer system | |
CN110825704B (en) | Data reading method, data writing method and server | |
US8015432B1 (en) | Method and apparatus for providing computer failover to a virtualized environment | |
US20090044186A1 (en) | System and method for implementation of java ais api | |
CN113765697B (en) | Method and system for managing logs of a data processing system and computer readable medium | |
CA2241861C (en) | A scheme to perform event rollup | |
Smart | The big picture | |
US10367711B2 (en) | Protecting virtual computing instances from network failures | |
Stack et al. | Self-healing in a decentralised cloud management system | |
US8595349B1 (en) | Method and apparatus for passive process monitoring | |
US11663096B1 (en) | Managing storage domains, service tiers and failed storage domain | |
US20230305876A1 (en) | Managing storage domains, service tiers, and failed servers | |
Youn et al. | The approaches for high available and fault-tolerant cluster systems | |
Read | Oracle solaris cluster essentials |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: SONY COMPUTER ENTERTAINMENT AMERICA LLC, CALIFORNI Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SILICON GRAPHICS INTERNATIONAL CORP.;REEL/FRAME:041157/0765 Effective date: 20131015 Owner name: SILICON GRAPHICS INTERNATIONAL CORP., CALIFORNIA Free format text: MERGER;ASSIGNOR:SGI INTERNATIONAL, INC.;REEL/FRAME:041157/0684 Effective date: 20120808 Owner name: SILICON GRAPHICS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SREENIVASAN, PADMANABHAN;DANDAPANI, AJIT;NISHIMOTO, MICHAEL;AND OTHERS;SIGNING DATES FROM 20020127 TO 20020710;REEL/FRAME:041593/0001 Owner name: SGI INTERNATIONAL, INC., CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:SILICON GRAPHICS INTERNATIONAL, INC.;REEL/FRAME:041593/0407 Effective date: 20090513 Owner name: SONY INTERACTIVE ENTERTAINMENT AMERICA LLC, CALIFO Free format text: CHANGE OF NAME;ASSIGNOR:SONY COMPUTER ENTERTAINMENT AMERICA LLC;REEL/FRAME:041593/0763 Effective date: 20160331 Owner name: SILICON GRAPHICS INTERNATIONAL, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SILICON GRAPHICS, INC.;REEL/FRAME:041595/0118 Effective date: 20090508 |
|
STCV | Information on status: appeal procedure |
Free format text: NOTICE OF APPEAL FILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |