IIOP Failover in Dynamic Clusters

Abstract-Requirement: Clients should experience high-availability when accessing network services. Availability should be transparent and not require altering programs. Problem: Availability needs to work on multiple platforms and must not require additional hardware/software, other than the remoting system. Solution: Replicate the service in a cluster. Advertise all replica addresses. On client invocation, if a replica address fails, have the remoting infrastructure try another address. Requirement: The number of replicas in the cluster can change dynamically (e.g., more/less instances to handle heavier/lighter loads, instances failing, online upgrades). Problem: Clients need to know the current cluster membership but are not able to participate in group membership communication. Solution: Give the initial cluster membership a label. Whenever membership changes generate a new label. Advertise the label. When a client invokes a service, send the label (as "out-of-band" data) ...

• Type: Conference
• Year: 2006
• Where: CIC
• Authors: Harold Carr, Ken Cavanaugh
• Keywords: CIC 2006, CIC 2008, Cluster Membership, Label, Replica Address Fails