rspregistrar
—
RSerPool Pool Registrar (PR) Service
rspregistrar |
[-announcettl=TTL ]
[-asap=auto|address:port,address,... ]
[-asapannounce=auto|address:port ]
[-autoclosetimeout=seconds ]
[-endpointkeepalivetransmissioninterval=milliseconds ]
[-endpointkeepalivetimeoutinterval=milliseconds ]
[-maxbadpereports=reports ]
[-maxhresitems=items ]
[-maxincrement=increment ]
[-minaddressscope=loopback|sitelocal|global ]
[-serverannouncecycle=milliseconds ]
[-enrp=auto|address:port,address,... ]
[-enrpannounce=auto|address:port ]
[-maxelementsperhtrequest=items ]
[-mentordiscoverytimeout=milliseconds ]
[-peer=address:port ]
[-peerheartbeatcycle=milliseconds ]
[-peermaxtimelastheard=millisecond ]
[-peermaxtimenoresponse=milliseconds ]
[-takeoverexpiryinterval=milliseconds ]
[-cspinterval=milliseconds ]
[-cspserver=address:port ]
[-logcolor=on|off ]
[-logappend=filename ]
[-logfile=filename ]
[-loglevel=0-9 ] |
rspregistrar
provides a registrar service
for Reliable Server Pooling (RSerPool) pool elements (PEs) and pool users
(PUs). PRs of an operation scope synchronize their view of the handlespace
using the Endpoint haNdlespace Redundancy Protocol (ENRP), transported via
SCTP. An operation scope has a limited range, e.g. an organization or only a
building. In particular, it is restricted to a single administrative domain
- in contrast to GRID computing - in order to keep the management complexity
at a minimum. Nevertheless, PEs may be distributed globally for their
service to survive localized disasters.
PEs choose an arbitrary PR of the operation scope to register into
a pool by using the Aggregate Server Access Protocol (ASAP), again
transported via SCTP. Upon registration at a PR, the chosen PR becomes the
Home-PR (PR-H) of the newly registered PE. A PR-H is responsible for
monitoring its PEs' availability by keep-alive messages (to be acknowledged
by the PE within a given timeout) and propagates the information about its
PEs to the other PRs of the operation scope via ENRP updates.
In order to access the service of a pool given by its PH, a PU
requests a PE selection from an arbitrary PR of the operation scope, using
the Aggregate Server Access Protocol (ASAP), transported via SCTP. The PR
selects the requested list of PE identities by applying a pool-specific
selection rule, called pool policy.
In order to allow for automatic configuration, a PR can send out
regular announces via an ASAP and ENRP multicast address. PEs and PUs can
listen to this address to learn the list of currently available PRs.
rspregistrar
uses the environment
variables CSP_SERVER and CSP_INTERVAL to define a CSP server to send reports
to in the specified interval.
If loglevel>0, log messages will be printed to stdout or into a
specified log file.
For a detailed introduction to RSerPool, see:
https://duepublico.uni-duisburg-essen.de/servlets/DerivateServlet/Derivate-16326/Dre2006_final.pdf
Thomas Dreibholz's RSerPool Page:
https://www.nntb.no/~dreibh/rserpool/