Print

Print


Hi Sebastien,

The default transaction timeout is set to 60 seconds. When reached, the
client will reconnect the server and try again. The only solution is to up
the timeout.

Andy

P.S. ut of curiosity,what do you have to tune in Ceph to get a round this.

On Fri, 4 Dec 2015, Sebastien Ponce wrote:

> I'm playing with an xrootd server having a ceph backend. I wrote some relatively big file (5GB) and wanted to drop it using xrdfs. One thing is that the ceph plugin to xroot is not at all optimized for deletion of big files and thus this deletion takes long (70s).
>
> What I see on the client side is the following (note that the deletion is successful) :
>
> # xrdfs lxbrl59a04.cern.ch:1095 rm /testbigfilenewws
> [ERROR] Server responded with an error: [3011] Unable to remove /testbigfilenewws; no such file or directory
>
> Now here is what happened on the server :
>
> 151204 16:30:20 30792 XrdInet: Accepted connection from [log in to unmask]
> 151204 16:30:20 30792 XrootdXeq: root.12416:33@lxc2cert5-a pub IPv4 login
> ceph_posix_unlink : /testbigfilenewws
> 151204 16:31:20 30793 XrdInet: Accepted connection from [log in to unmask]
> 151204 16:31:20 30793 XrootdXeq: root.12416:7@lxc2cert5-a pub IPv4 login
> 151204 16:31:20 30793 root.12416:7@lxc2cert5-a XrootdProtocol: endsess 30598:33.16
> 151204 16:31:20 30793 root.12416:7@lxc2cert5-a XrootdProtocol: endsess 30598:33.16 rc=4 (Resource temporarily unavailable)
> ceph_posix_unlink : /testbigfilenewws
> ceph_posix_unlink : /testbigfilenewws
> 151204 16:31:25 30792 XrootdXeq: root.12416:33@lxc2cert5-a disc 0:01:05
> ceph_posix_unlink : /testbigfilenewws
> 151204 16:31:30 30787 ofs_remove: root.12416:7@lxc2cert5-a Unable to remove /testbigfilenewws; no such file or directory
> 151204 16:31:30 30787 root.12416:7@lxc2cert5-a XrootdResponse: sending err 3011: Unable to remove /testbigfilenewws; no such file or directory
>
> As you can see, the client was getting impatient and has retried the rm several times. Sadly, the last one cam just when the deletion was finally over, hence the final "File not found".
>
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/315


Reply to this email directly or view it on GitHub.



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