Maybe not a warm topic today but it will become hotter for the next reprocessing campaign in december:

• Pin leak found in FTS: For the Staging + transfer case, FTS creates two pins. One for bringonline and another for srmpreparetoget.  On transfer completion, only the pin generated by srmpreparetoget is released. The one from bringonline is kept. Tickets: https://its.cern.ch/jira/browse/FTS-1491  
• This impacts https://github.com/rucio/rucio/issues/3035: The pin lifetime from Rucio to FTS cannot be set to the rule lifetime as it will keep files for too long on the buffer.
• Now, the current default pin lifetime is too short and doesn't protect the files long enough: Files are staged several times, garbaged collected, etc before the final transfer. This also impact site performance in general  https://its.cern.ch/jira/browse/FTS-1492
• This affects all T1 dCache sites requiring garbage collection.