Setup another transfer, passing the option -g '-p 10' to FTS. For the moment, I have disabled it and all traffic now going through the pool node. Also having problem with gridftp door on the admin node not starting up.

FTS log files reported problem with pool dcache_24. Even if I now just submit a single file for transfer, I get an error these error messages. Initially transfers were successful, then started seeing error messages in the dCache pool node gridftp door logs:ġ2/13 16:14:48 CellAdapter: cought SocketTimeoutException: Do nothing, just allow looping to continue Also gave chance to study the FTS logs and ganglia monitoring pages. Initially just using Matt Hodges test script to start some transfers in order to observe the performance before any tuning took place. Problem was eventually resolved when a new myproxy -d was issued.įTS tests were started properly. FTS was accepting the jobs, but querying the transfer status produced a strange error message. It is hoped that there will be sufficient time to study these effects on the transfer rate. In addition to modifying the dCache setup, it is also possible to use FTS to modify the configuration of the RAL-ED channel (in terms of number of concurrent file transfers and parallel streams). This data will be used to modify our dCache setup in the future towards a more optimal configuration. It is expected that there will be a decrease in the transfer rate when only the NFS mounted pools are available to the dCache, but I would like to get a quantitative results. As a warm up for this test, I will transfer smaller amount of data from the Tier-1 and at the same time modify our dCache setup to observe the effect that the following have on the data transfer rate: SC4 requirement is for a sustained transfer of 1TB of data from the RAL Tier-1.

Gftp file size limit