GLAST Infrastructure How-to-Fix : HTF Xrootd
This page last changed on May 28, 2008 by chuckp.
How to Fix XrootdOwned by: Wilko Kroeger Note: xrootd is the daemon for the Xrootd data server. The xrootd cluster consists of redirectors and data server. A redirector is the central entrance point for a client. It does not provide any files but it directs a client to an appropriate data server.
Relevant directories on each Xrootd server are:
Monitoring ToolsFree disk space glast xrootd server: http://www.slac.stanford.edu/~wilko/glastmon/xrddisk.html Nagios01 xrootd Service Status: http://nagios01.slac.stanford.edu/nagios/cgi-bin/status.cgi?hostgroup=GLAST+xrootd+Servers&style=detail Ganglia glast-xrootd: http://ganglia01.slac.stanford.edu:8080/ganglia/glast/?c=glast-xrootd&m=&r=hour&s=descending&hc=4 Start/Stop daemonsThe glast xrootd servers (data servers and redirectors) are configured so that ranger will automatically restart a non running xrootd or olbd daemon. Ranger runs every 15 min. Notes:
Background Notes:Xrootd (also referred to as SCALLA for "Scalable Cluster Architecture for Low Latency Access") handles both disk and tape, thereby providing the option to write data for which demand has been low, to tape and retrieve it upon request. In addition to scalability and rapid response times, Xrootd is able to handle concurrent requests for data located in the same directory. In contrast, AFS also handles concurrent requests, but replicates requested files on additional servers as needed in order to keep pace with requests for data, making it much less efficient in its use of disk space. NFS is not as good as AFS at handling concurrent requests for data from the same directory, and its use is therefore being minimized. |
![]() |
Document generated by Confluence on Jan 21, 2010 11:37 |