Page History
...
An update from 20080410-0747 to 20080513-1222 was needed as a critical bug was found (https://jira.slac.stanford.edu/browse/GXR-33
) that affect the automatic update of the authorization file used by xrootd. Otherwise there are only small bug fixes between 20080410-0747 and 20080513-1222 that don't affect GLAST.
The test setup on the glast xrootd cluster used the configuration that would be used in production, in particular
authorization has been turned on. Only glast users are allowed to read data and certain production accounts are
allowed to write to xrootd.
The basic functionality of the new xrootd version has been examined in a test cluster. The testing included
reading/writing with xrdcp, stating files and checksumming of files.
...
- running the crawler
- MC-simulation
- skimmer jobs
- reading and writing with xrdcp
- reading from xrootd with root version 5.18.00(b)
and they run successfully.
The test that required the xrootd client tools (xrdcp to transfer files, xrd.pl to stat,checksum and remove
files) were done with using client tools from the new version.
...
It is possible to re-activate the old xrootd version now , no data will be lost.
CCB Jira
...
- Install new client admin tools:
mv /afs/slac/g/glast/applications/xrootd/TEST to /afs/slac/g/glast/applications/xrootd/PROD
The new version works with the old xrootd servers and this move doesn't cause any disruption to clients. - Stop xrootd on all data servers
- Stop xrootd on the redirectors (glastlnx04/05)
- activate new version on redirectors and restart them.
- restart xrootd on the data server servers with the new version
The whole procedure should take less then five minutes and clients will retry to access xrootd during that time
and not fail. User will be informed when the restart will happen in order to reduce the load on xrootd, just as a precaution.