GitLab

Corrected scheduling to wait for more files to be queued before creating ArchiveForRepack mount + Unit test

The disk read task hangs in this case. The tape write taks is still created, will leave a placeholder on the
tape (to be implemented) and count an error for the request.

Also added extra logs in ArchiveMount::getNextJobBatch().

Replaced castor file header with CTA file header

Moved castor::server::
  BlockingQueue
  Semaphores
  AtomicCounter
  AtomicFlag
into cta::threading::

Completed changes so that archive and retrieves can be queued, mounts created and jobs reported done.

Removed deprecated structures from archiveNS and nameserver namespaces. Removed RetrieveToFileRequest.

This implied removing tpconfig, tplabel and tpstat.

Fixed confusion between archive and retieve in logging "path" and creation of file object by file factory.

Implemented cta::ArchiveJob::complete(), and added the members that should be set to have the necessary
information available at complete() time.
Updated the calls in the archive_and_retrieve_new_file unit test.

Please note that you will have to install the following CASTOR rpms
in order to compile:

  castor
  castor-devel
  castor-lib
  castor-lib-server
  castor-lib-tape

Renamed CTA/tapeserver/castor to CTA/tapeserver/castor_checkout in preparation for the moving the sub-directory CTA/tapeserver/castor/castor up the directory tree

Added a the new criteria (less that half the work asked for) for ending the session for migrations.
The symetric for recalls is not possible currently as we do not know the file size beforehand in recalls (it is found out from data on tape).

wait for the end of execution pipeline draining in all cases in MigrationTaskInjector::WorkerThread::run.
The asynchronous deleteAllTasks deleted the end-of-session signaling to the task injector, which led this
end of MigrationTaskInjector::WorkerThread::run into infinte waiting for this dropped end of session signal.

Reviewed and fixed the error handling for migrations.
A deadlock was created by the competing usage of a stop variable an normal information flow
through the threads. The global variable's usage has been reduced and clarified:
it is set by the tape thread to indicated an error reached it. From that point
on, the remaining disk threads can stop what they are doing (and not before as failing
to read a file should not block the completion of previous ones).
The file errors are now transmitted to the client before end of session, and in case of flush.
The unit tests have been updated accordingly.
Report messages have been improved.