Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
Frankly, my take is that you are over estimating what the file system can do
Possibly. But before we switched to xrootd-only, we ran DMLite+HDFS on the same hardware. No checksum issues or general timeouts.
Deletions would occasionally stress the server if done via GridFTP, but worked fine via HTTP - the limitation has always been on the server side, not the file system.
Both redirector nor server are at low load (< 50% of cores) and are otherwise not very busy - nor is the file system.
That's the main reason I cannot understand the current issues.
I hope it is just a misconfiguration on our side or something with a workaround.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.
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