Print

Print

One more thing ... even when Andy and I rework the file-close protocol so that it eventually closes out all the fds, the situation from the overload perspective won't change much, that is, the caching proxy will still struggle to write out the last remaining blocks and then close the file.

So, if you are consistently hitting this issue it means you either need a beefier machine (correctly configured for allowing O(1000) simultaneous read/write streams (raid 5/6 or zfs setups are known to choke with this rather badly)) or a caching cluster.

There is another solution for this case, immediate local client redirect to the origin ... and this is almost ready to go. But it won't work if local clients can not connect to WAN.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/975?email_source=notifications\u0026email_token=AA7NRDUSYRPIMO2PMJS5WUTP4HSQVA5CNFSM4HLGWH72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYPVUSQ#issuecomment-505371210", "url": "https://github.com/xrootd/xrootd/issues/975?email_source=notifications\u0026email_token=AA7NRDUSYRPIMO2PMJS5WUTP4HSQVA5CNFSM4HLGWH72YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYPVUSQ#issuecomment-505371210", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

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