...
Item | Presenter | Notes | |||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Operational Issues | |||||||||||
Further observations from Data Challenge Future testing plans (RAL initiated / VO initiated) ? | All | To improve still: LB, Checksums (inflight + metadata), RR with failsafe hotspotting | |||||||||
Rocky 8 migration planning | |||||||||||
Deletion studies through RDR | Previous deletion times reported were from the client side, end-to-end. Now analysing times for individual ceph_posix_unlink calls, and will look at deletion request times with XRootD itself. That is, looking at the amounts of time that a deletion request takes travelling though layers of XRootD code. I’ve noted some strange outliers from an initial sample (y-axis times in ms, last tick should read 80000 ms.) Outlier for ceph_posix_unlink at 90s? stddev of 4476 for the plot below. 6808 samples taken for a single gateway from 22nd Feb: | ||||||||||
Deletions |
Next steps: Identify potential solutions. | ||||||||||
Planning for ALICE CMSD redirection | INC-163994 - DNS ip additions | ||||||||||
Checksums fixes | |||||||||||
Prefetch studies and WN changes | |||||||||||
Tokens Status | |||||||||||
CMSD Load balancing | PR: It replaces the current algorithm in xrootd. testing for simulated behaviour in progress. | ||||||||||
SKA Gateway box | |||||||||||
5.6.x root TPC issue | https://github.com/xrootd/xrootd/issues/2202 issue open, under investigation |
...