1. 20 Dec, 2018 1 commit
  2. 19 Dec, 2018 1 commit
  3. 17 Dec, 2018 1 commit
  4. 13 Dec, 2018 2 commits
  5. 12 Dec, 2018 2 commits
  6. 11 Dec, 2018 1 commit
  7. 09 Nov, 2018 1 commit
    • Steven Murray's avatar
      DataTransferSessionTapeFullMigration and... · 7d1ce91e
      Steven Murray authored
      DataTransferSessionTapeFullMigration and DataTransferSessionTapeFullOnFlushMigration now count the first files archived to tape as opposed to relying on the values of the archive file IDs
      7d1ce91e
  8. 08 Nov, 2018 1 commit
  9. 29 Oct, 2018 1 commit
  10. 01 Oct, 2018 1 commit
  11. 27 Sep, 2018 1 commit
  12. 20 Sep, 2018 1 commit
  13. 14 Sep, 2018 1 commit
  14. 30 Aug, 2018 5 commits
    • Eric Cano's avatar
      Added disk reporter to the new maintenance process. · 97ec27f4
      Eric Cano authored
      The maintenance process replaces the garbage collector process. It now
      runs both garbage collection and disk reports.
      97ec27f4
    • Eric Cano's avatar
      Unified function names for transfers to tapes. · 5c3d1d92
      Eric Cano authored
      5c3d1d92
    • Eric Cano's avatar
      Updated unit test criteria. · c24a1d8f
      Eric Cano authored
      c24a1d8f
    • Eric Cano's avatar
      Reworked ArchiveRequest jobs lifecycles. · 391ca9a8
      Eric Cano authored
      Changed the lifecycle of the ArchiveRequest to handle the various
      combinations of several jobs and their respective success/failures.
      Most notably, the request now holds a reportdecided boolan, which
      is set when decing to report. This happens when failing to archive
      one copy (first failure), or when all copies are transferred (success
      for all copies).
      
      Added support for in-mount retries. On falure, the job will be
      requeued (with a chance to pick it up again) in the same session
      if sane session retries are not exceeded. Otherwise, the job is
      left owned by the session, to be picked up by the garbage collector
      at tape unmount.
      
      Made disk reporter generic, dealing with both success and failure.
      Improved mount policy support fir queueing.
      
      Expanded information avaible in popped element from archive queues.
      
      Added optional parameters to ArchiveRequest::asyncUpdateJobOwner() to
      cover various cases.
      
      Updated the archive job statuses.
      
      Clarified naming of functions (transfer/report failure instead of bare
      \"failure\").
      
      Updated garbage collector for new archive job statuses.
      
      Added support for report retries and batch reporting in the scheduler
      database.
      
      Updated obsolete wording in MigrationReportPacker log messages and error
      counts.
      391ca9a8
    • Eric Cano's avatar
      Created DiskReportRunner class. · 0654c5cd
      Eric Cano authored
      This class will handle reporting like the GarbageCollector class
      does for garbage collection.
      
      Adapted the interface of scheduler and ArchiveRequests to allow delegating
      reporting to the disk report runner.
      
      This commit is not functionnal. We still need to:
      - Implement the ToReport/Failed queues interface.
      - Adapt the queueing in the scheduler/ArchiveMount
      - Implement the popping of jobs to report.
      - Implement the async reporter for the files.
      - Develop the user interface for failed requests.
      0654c5cd
  15. 14 Aug, 2018 4 commits
  16. 13 Aug, 2018 1 commit
  17. 01 Aug, 2018 1 commit
  18. 31 Jul, 2018 1 commit
  19. 30 Jul, 2018 1 commit
  20. 05 Jul, 2018 2 commits
  21. 04 Jul, 2018 3 commits
  22. 29 Jun, 2018 1 commit
  23. 28 Jun, 2018 1 commit
  24. 06 Jun, 2018 1 commit
  25. 29 May, 2018 1 commit
  26. 15 May, 2018 1 commit
  27. 14 May, 2018 1 commit
  28. 11 May, 2018 1 commit
    • Eric Cano's avatar
      Split queuing archive requests in top and bottom half. · fdb435a5
      Eric Cano authored
      The top half goes as far as when the request is safe in the object store.
      At that point, the bottom half is launched in a new thread, and success is returned
      the called. This will enable lower latency for the users while retaining
      the same data safety.
      
      This version is experimental aas it spans an undetermined number of threads. A more controlled
      version with a work queue should be implenented on the long run.
      fdb435a5