1 / 9

Reliable Server Pooling Architecture

Reliable Server Pooling Architecture. Michael Tüxen tuexen@fh-muenster.de. The Motivation. Build systems without a single point of failure by using servers not being highly reliable. SCTP addresses network failures. RSerPool addresses host failures (as much as possible). Server Pools.

sydnee-barron
Download Presentation

Reliable Server Pooling Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Reliable Server PoolingArchitecture Michael Tüxen tuexen@fh-muenster.de

  2. The Motivation • Build systems without a single point of failure by using servers not being highly reliable. • SCTP addresses network failures. • RSerPool addresses host failures (as much as possible).

  3. Server Pools • Use a set of servers instead of one. • Identify them by a Pool Handle (PH). • Provide a mechanism to resolve PH to transport addresses. • State sharing between the servers is out of scope of RSerPool

  4. Entities in the Architecture • Pool Elements (PEs) • the servers in a server pool. • Pool Users (PUs) • the clients. • Name Servers (NSs) • the entities performing the name resolution.

  5. PE PE PE PE PE NS NS Communication relations PU PU

  6. Protocols • Aggregate Server Access Protocol (ASAP) • PE <-> NS • PU <-> NS • PU <-> PE (Enhanced Mode) • Endpoint Name Resolution Protocol (ENRP) • NS <-> NS

  7. What are the protocols used for? • ASAP • Registration of PEs. • Re-registration of PEs. • Supervision of PEs. • Name resolution. • Failover support. • ENRP • Complete state sharing between the NSs.

  8. General Considerations • Lightweight Client have to be supported. • Two entities are in the transport address selection involved. • There are other applications for RSerPool: distributed computing, support for transport layer mobility, ...

  9. Failover Support • Business Cards for PUs being PEs. • Last Will for preferred PEs to fail over. • State Cookie for state synchronization. • Only available in Advanced Mode.

More Related