 |
 |
Thank you for the update Eric. If async is the issue then it would indicate that, perhaps, it is a problem when a particular block of data is written out of order. It would nice if we could catch that somehow. Of course, that would mean bringing back the error which may be too disruptive. Andy On Wed, 4 Nov 2020, Eric Cano wrote: > I was away for 2 weeks, during which we had the transfers set to sync and no issue arose. So the problem happens only with async enabled. We will stick to this setup for the time being. > > To be complete, we also automatically restarted the xrootd daemon every day (to minimize the odds of having accumulations of pending transfers), so this could play a role. This mechanism had been now removed. I will report if new issues pop up. > > -- > You are receiving this because you were mentioned. > Reply to this email directly or view it on GitHub: > https://github.com/xrootd/xrootd/issues/1305#issuecomment-721730821 -- 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/1305#issuecomment-722026964 ######################################################################## 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