Reason for change
We would like to deploy a new xrootd version switching from 20080513-1222 to 20080531-0714p1.
The new version contains a few fixes:
- Allow removing files via the redirector from data servers that are filled (GXR-37@JIRA)
- Allow collection of xrootd statistics by Ganglia (GXR-38@JIRA)
- Fixes a bug that could cause the redirector cmsd to crash if a suspended data server connects
to quickly again.
Besides that the new version contains only minor changes.
Testing
The standard tests for a new xrootd release have been done:
reading and writing files with xrdcp,
client admin tools like stat, rm files and create and remove directories.
The new version has been installed as a test version on the glast xrootd cluster which allows
access to the glast data. Tests were done to access the data using the test xrootd.
Rollback
The old xrootd version can be re-activated and restarted. The xrootd configuration file has to be rolled back. It will take about 5 minutes to do the roll back
CCB Jira
Details
Only the xrootd version running on the xrootd cluster will be changed. The version that clients are using out of the application area (/afs/slac.stanford.edu/g/glast/applications/xrootd/PROD) will not be changed.
No outage is required for installing the new version the procedure will be:
- Update xrootd configuration file (for ganglia monitoring)
- activate the new version on all xrootd servers (just updates a link that points to
the new version) - restart the redirectors
- restart the data servers
The restart it self will take a couple of minutes and should not affect any client.
Details
Only the xrootd version running on the xrootd cluster will be changed. The version that clients are using out of the application area (/afs/slac.stanford.edu/g/glast/applications/xrootd/PROD) will not be changed.
No outage is required for installing the new version the procedure will be:
- Update xrootd configuration file (for ganglia monitoring)
- activate the new version on all xrootd servers (just updates a link that points to
the new version) - restart the redirectors
- restart the data servers
The restart it self will take a couple of minutes and should not affect any client.