 |
 |
Frankly, varioous options introduce their own peculiar side effects that may make the system annoying enough that people simply consider it broken and move on. In this particular case the simplest solution is to limit the number of TPC requests that can happen at the same time. We did that right off the bat for xroot TPC and that worked really well. I am suprised that no such limit was envisioned for the http side. Saying they share the same storage is, in my opinion, architecturally misguided and very much complicates the whole storage backend when a simple solution exists. Andy On Tue, 1 Feb 2022, Alessandra Forti wrote: > Hi Brian, > >> 4: This was recently added to the throttling plugin. I think the filesystem level is an appropriate place to put limits given that the storage resources are shared between HTTP and XRootD. > > A transfer protocol should have the option to limit the number of connections to the server that it serves the data from. I think limiting the file system assumes the file system isn't supporting other applications. > > -- > Reply to this email directly or view it on GitHub: > https://github.com/xrootd/xrootd/issues/1601#issuecomment-1026921244 > You are receiving this because you are subscribed to this thread. > > Message ID: ***@***.***> -- Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/1601#issuecomment-1027118152 You are receiving this because you are subscribed to this thread. Message ID: <[log in to unmask]> ######################################################################## 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