- Compact style
- Indico style
- Indico style - inline minutes
- Indico style - numbered
- Indico style - numbered + minutes
- Indico Weeks View
Topic: WLCG DOMA TPC Meeting
Join Zoom Meeting
https://cern.zoom.us/j/99836057922?pwd=ZFhWN3NpYi9oZmwvM3pIRE9zdzFnZz09
Meeting ID: 998 3605 7922
Passcode: 733660
One tap mobile
+41315280988,,99836057922# Switzerland
+41432107042,,99836057922# Switzerland
Dial by your location
+41 31 528 09 88 Switzerland
+41 43 210 70 42 Switzerland
+41 43 210 71 08 Switzerland
+33 1 7037 2246 France
+33 1 7037 9729 France
+33 1 8699 5831 France
Meeting ID: 998 3605 7922
Find your local number: https://cern.zoom.us/u/aeB4ArMgmT
Total sites (T1_Disk + T2s) | 56 |
Notified Sites | 56 (100%) |
Reporting a davs endpoint | 47 (83%) |
Passed manual tests | 41 (73%) |
Passed loadTests (davs) | 13 (23%) |
Passed loadTests (srm) | 12 (21%) |
Enabled to fetch changes in TFC: | 0 (0%) |
1. Corner cases in the TFC parser
The TFC parser uses regular expressions to parse all the possible formats of the URLs used within the LFN to PFN rules. We have found cases not taken into account by the set of regexps or pieces in the code whit missing regexps. I'm currently refactoring these pieces of code.
2. WebDAV in the TFC
Either the site admins do not define their WebDAV endpoint at their TFC or they define it wrongly
3. Missing permission
We have found many sites missing permissions for Rucio to write the LoadTest file
4. The ASO problem.
We found out that ASO relies on the Rucio configuration of the RSEs to schedule its TPC transfers. It always fetches the preferred protocols for read and write from the sites involved but doesn't check whether they're compatible or not. We had to change our TFC parser to keep read/write preferred protocols fixed to srm.
Luca M:
Sorry, unfortunately I would not be able to join this meeting, here a short update from my side.
On the 12th April we organised a dedicated meeting to follow up between experts (EOS, XRootD, DM clients) the current libcurl memory leak issue in XRootD on CentOS7.
During the meeting we agreed that a patch will be provided to XrootD5, targeting release 5.2 (thanks a lot to Brian B. for his rapid development of the patch). This patch will enable XRootD to automatically build and load a bundle certificate leading to an expected leak of only 350 bytes per transfer.
On the EOS operational side we are currently targeting for the roll out of EOS version 5 with the latest XRootD 5 release. This will allow to roll-out in our production cluster the patch with the next EOS release.
We are also currently evaluating if it will be necessary to port the patch back to XRootD version 4.
Steps towards a minimal unified monitoring solution (Rizart):
Towards Networking DC 2021 (Riccardo):