...
- It would be nice if xrootd kept the original date when a file is copied in, and maintained this even if added to/restored from HPSS.
- The command syntax, error messages, and returncode for commonly used xrootd commands could be
improved to be easier to use within (python) scripts. - lack of a reasonable way to list files in xrootd (e.g., "ls" command)
- A possible alternative solution would be a nightly job which lists files on all servers, combines them together, and flags inconsistencies (e.g. same file with different size/date).
- Ability to migrate (or duplicate) data between disks without going via HPSS.
Recommendations/Action Items
- Do not run NFS on the same machine as xrootd.
- Increase priority of some xrootd processes.
- Checksum only (a few) files at a time (we already do).
- Could append some kind of UID to files to ensure names are unique.
- Could perhaps use process instance ID?
- Need to think about how we access files from different job steps
- Should not use ID in public data catalog name
- Ideally this could be automated as part of GPL tools
- How to handle incomplete (real) data ?
- Maybe we can move data if we find out that it is as complete as it ever will be.
- Access control
- We need to restrict access to members of glast-user (or subset)
- NFS group is recommended way to handle it
- We need to figure out how to create an NFS group and keep it updated automatically
- When machines on which xrootd daemons are running crashes system does not recover
- Not clear whether there is a timeout issue
- Set timeout lower?
- Try out on Wilko's laptop
- Bug in rm — bug in client (bug #?)
- Fabrizio has promised to fix this (moving to CERN, Atlas)
- xrdcp -f bug is fixed
- xrdcp is in /usr/local/bin
- When Tom does a lot of rm's together with short timeout caused problems
- Wilko dummied out mss call
- How easy to bring xrootd down?
- Many clients reading at once can cause client timeouts
- Thumpers have 15TB per machine.
- Ganglia runs on our servers
- Wilko will ask Yemi to rename the servers which are running xrootd
- Talk to Tifigh about how appropriate the Babar Monitoring System is for Glast
- We will send Tom a pointer to babar monitoring system
- We will attempt to be more organized and formal about which releases Glast is using
- We will use our own glast location for client tools
- Wilko should use version management in Jira
- Should use AFS directories area to make version # clear
- Will make sure tools can print out their version #
- Hard to maintain dates on files in xrootd
- Tom should provide list of desired return codes for xrootd tools
- Wilko has a xrdcpls command
- We could add the checksum into the file
To Do List
- Complete implementation of tar/archive/retrieval system
{"serverDuration": 58, "requestCorrelationId": "569aa962505b5d48"}