 |
 |
Hello, XRootD Developers,
I am operating a CMS Tier-2 center. I am contacting you because there is an issue related to throttle syntax.
Since our site subscribes to the global federation redirection of CMS experiments, we are supposed to respond to data requests from other CMS sites. This is called CMS AAA.
The problem is that when a particular user creates an enormous amount of grid jobs requesting data that is only on our site.
We used dCache as a backend and ran an xrootd daemon in the front for the federation subscription.
We set "throttle.throttle concurrency 30" in this xroot daemon setting, but we found that all of these transfer requests were delivered to dCache.
In some cases, the number rises momentarily and is blocked, but xrootd delivered the request to dCache, rather than the data transfer itself. So, it shows the concurrent jobs decrease after requesting delivery. Therefore, not only will there be tens of thousands of job requests waiting on the dCache side, but xrootd itself has tens of thousands of TCP sessions, which is a huge burden on the server.
I think the xrootd server is responsible for the actual transmission burden because I set the pss instead of redirecting. But I think it's a fatal bug to leave out of the throttle number.
Please review it.
Also, I would like to ask if it is possible to develop a queue system to pass site stability checks such as the SAM test in the throttle setting.
Regards,
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1