This project is mirrored from https://:*****@github.com/Ensembl/ensembl-hive.git. Pull mirroring updated .
  1. 24 Nov, 2017 1 commit
  2. 12 Jan, 2017 1 commit
  3. 27 Sep, 2016 1 commit
  4. 06 Jul, 2016 4 commits
  5. 03 Jun, 2016 1 commit
  6. 18 Mar, 2016 1 commit
  7. 29 Jan, 2016 1 commit
  8. 08 Jan, 2016 1 commit
  9. 23 Nov, 2015 1 commit
  10. 18 Jun, 2015 1 commit
  11. 17 Jun, 2015 2 commits
  12. 21 May, 2015 1 commit
  13. 19 May, 2015 1 commit
  14. 07 May, 2015 2 commits
  15. 28 Apr, 2015 1 commit
  16. 26 Mar, 2015 1 commit
  17. 19 Mar, 2015 1 commit
  18. 12 Mar, 2015 2 commits
  19. 26 Feb, 2015 1 commit
  20. 02 Feb, 2015 1 commit
  21. 28 Jan, 2015 1 commit
  22. 27 Jan, 2015 1 commit
  23. 26 Jan, 2015 1 commit
  24. 22 Jan, 2015 1 commit
  25. 16 Jan, 2015 1 commit
  26. 15 Jan, 2015 1 commit
    • Matthieu Muffato's avatar
      bugfix: the claimed batch was not released · d9f1b05b
      Matthieu Muffato authored
      The problem was when a worker is contaminated and has to die: remainings jobs
      of the batch were not released.
      We now have an explicit list of all the cause_of_death that could happen through
      a batch, and for which we should free the jobs
      d9f1b05b
  27. 13 Jan, 2015 1 commit
  28. 07 Jan, 2015 1 commit
  29. 04 Dec, 2014 1 commit
    • Matthieu Muffato's avatar
      Clearer flags in register_worker_death() · 321e4b53
      Matthieu Muffato authored
      "self-burial" had two meanings:
       - should we release the undone jobs ?
       - should we update the last_check_in field in the worker table ?
      The former can simply be found by checking whether the worker already has a
      role attached to it.
      The latter is only set when a worker registers its own death, and is not set
      by the GarbageCollector.
      321e4b53
  30. 15 Nov, 2014 1 commit
    • Matthieu Muffato's avatar
      Clearer flags in register_worker_death() · f69e4e27
      Matthieu Muffato authored
      "self-burial" had two meanings:
       - should we release the undone jobs ?
       - should we update the last_check_in field in the worker table ?
      The former can simply be found by checking whether the worker already has a
      role attached to it.
      The latter is only set when a worker registers its own death, and is not set
      by the GarbageCollector.
      f69e4e27
  31. 25 Oct, 2014 1 commit
    • Matthieu Muffato's avatar
      bugfix: jobs could not trigger MEMLIMIT events · 91de34e4
      Matthieu Muffato authored
      (and probably RUNLIMIT as well)
      The problem was in Queen::register_worker_death(). The code fetches the
      current role, finalizes it, and then updates the worker table. The role
      that is fetched from the database with fetch_last_unfinished_by_worker_id()
      is not connected to any workers and later, when
      AnalysisJobAdaptor::release_undone_jobs_from_role() needs to know the cause
      of death and the number of work done by the worker, the role would load
      another instance of the worker using the information currently stored in
      the database, that is: before it has been updated.
      Hence, the code was complaining that cause_of_death was not populated.
      By associating the role to the worker, we allow the method to read the
      existing information
      91de34e4
  32. 06 Oct, 2014 2 commits
  33. 01 Oct, 2014 1 commit