Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • autosubmit autosubmit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 338
    • Issues 338
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 21
    • Merge requests 21
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Earth SciencesEarth Sciences
  • autosubmitautosubmit
  • Issues
  • #945
Closed
Open
Issue created Feb 07, 2023 by dbeltran@dbeltranMaintainer

Change lock mechanism

Our current lock mechanism relies on a library that doesn't work properly if three or more instances of the experiment are running. ( mainly due to the shared filesystem )

  • The lock is done properly on the first run,
  • The lock is released if another run or create on the same experiment is triggered, although the attempt is blocked if the first instance didn't finish.
  • The lock is done again, but the instance is never blocked.

The idea is to change this library to a custom file-based lock.

Edited Feb 14, 2023 by dbeltran
Assignee
Assign to
Time tracking