 |
 |
We had this email exchange with @bbockelm some time ago (1 year ago) [EMAILCOPY]. We have been hit now several times with an excessive xrootd usage and a single user filled our uplink with transfers to WAN (other sites). So it would be nice to have throttling control based on the user. [EMAILCOPY] ``` Do we have a way to limit specific users and max connections they can open over xrootd? I like this feature in GridFTP [1] and would be nice to have the same in xrootd. I see some users are abusing the system (dataset is only at Caltech and they run via xrootd opening 20k-30k connections from all around the world) - which overall affects storage and many other things make it inefficient... Maybe it is not the right place to ask, but is there plans to put some logic in CRAB that can ignore whitelist and what can not? [1] export GRIDFTP_TRANSFER_LIMIT="80" export GRIDFTP_DEFAULT_USER_TRANSFER_LIMIT="50" export GRIDFTP_<UNIX USERNAME>_USER_TRANSFER_LIMIT="40" From Brian: I wrote the GridFTP throttling code originally (as well as the Xrootd throttling code) ... I don't think the per-user features have been ported from the GridFTP code base to the XRootD one. There's only a process-wide concurrency limit. Good idea though! Sounds like we're saving up a number of items for an "Xrootd Creature Comforts Hackathon"! ``` -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1446 ######################################################################## 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