Tags

Release made to test a "faster" version of OracleCatalogue::deleteArchiveFile().

Please note that this is NOT the final version of OracleCatalogue::deleteArchiveFile().  In the future we will NOT delete rows from catalogue database when "eos rm" is executed.  Instead we will simply update a status column to a "deleted" status.

Added timing measurements and lockfree operations.

YAR

YAR (timing + fixes)

Bulk archive/retrieve.

YAR

Fixed retrieve mount scheduling.

Re-taging back in time and before commits requiring xrootd version change.

Locking improvement in BackendRados (bigger lock timeout, backoff mechanism).

Fixed bug in locking logic of Helpers::getLockedAndFetchedQueue<ArchiveQueue>() in case of retry.

Added stack trace to scheduling failures.

YAR (Yet Another Release)

Fixed empty queues and empty objects.

Fixed crash in garbage collector.

Added missing error handling in serialization.

Fixed couple of fix (such as garbage collectors crashing, faster queing of requests, etc.)

The CTA front-end now calls the Scheduler when EOS requests the deletion of an archive file.

The CTA front-end no longer tries to delete an archive request from the object store when it handles an ```eos rm``` command.

Please note that this there is now a leak in archive files.  If a file is "in-flight" and therefore has not yet been written to tape and recorded in the CTA catalogue then a call to "eos rm" will do nothing and the file will eventually appear in the CTA catalogue when it is written to tape.  The file will therefore NOT be in the EOS namespace but it WILL be in the CTA catalogue.