Silicon Graphics, Incorporated

Sony Computer Entertainment America LLC

Sony Interactive Entertainment America LLC

Ajit Dandapani

Raghu Mallena

Ira Pramanick

Manish Verma

Luca Castellano

Padmanabhan Sreenivasan

Michael Nishimoto

Robert David Bradshaw

Sharad Srivastava

Robert David Bradshaw, Jr

Robert D Bradshaw, Jr

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. In addition, 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.

Flexible failover policies in high availability computing systems

A high availability computing system includes a plurality of computer nodes (for example, a server system) connected by a first and a second network, wherein the computer nodes communicate with each other to detect server failure and transfer applications to other computer nodes on detecting server failure. The system incorporates methods of maintaining high availability in a server cluster having a plurality of nodes. A group communications service, a membership service and a system resource manager are instantiated on each node and the group communications service, the membership service and the system resource manager on each node communicate with other nodes to detect node failures and to transfer applications to other nodes on detecting node failure.

Maintaining process group membership for node clusters in high availability computing systems

A method of correlating a group of related processes residing on separate computers of a computer network so that they can be treated as a single entity. A single, large program is split up into separate processes and simultaneously run on several different computers. These related, but separate, processes are assigned a unique identifier. When a new process is created, it is assigned the same identifier as that of the process from which it was created, even though the child process might reside on a different computer. If a process determines that it should not belong to its current group, that process can create its own group by requesting that it be assigned a new identifier. Based on the identifiers, it is possible to implement programs that treat related processes as a single entity.

Operating system having a mechanism for handling a group of related processes residing on separate machines

Growing community of inventors

Los Altos, CA, United States of America

Ajit Dandapani