What is the impact on the client in the event of a failover?
The failover event, if it happens, should be transparent to the client. The client may experience a slight delay since server objects on the Slave Naming Server may be activated on demand to service the requests that are coming in. And of the corba object references that the client is holding, transient references like iterator references are no longer valid. This shouldn’t be too much of a problem since clients using transient iterator references should be prepared cases where the references become invalid. The reason being the Naming Server should not leave too many iterator lying around taking resources so it is given the right to invalidate the iterator references any time. Other than the transient references, any request using the persistent references will be re-routed to the Slave Naming Server. ; Load Balancing NS800-What are the differences between the load balancing of a Cluster and that of Osagent? Both Cluster and Osagent provide Round Robin load balancing facility. But the
The failover event, if it happens, should be transparent to the client. The client may experience a slight delay since server objects on the Slave Naming Server may be activated on demand to service the requests that are coming in. And of the corba object references that the client is holding, transient references like iterator references are no longer valid. This shouldn’t be too much of a problem since clients using transient iterator references should be prepared cases where the references become invalid. The reason being the Naming Server should not leave too many iterator lying around taking resources so it is given the right to invalidate the iterator references any time. Other than the transient references, any request using the persistent references will be re-routed to the Slave Naming Server.
