Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add a persistent layer for the state of locks #54

Open
Tracked by #44
CiottiGiorgio opened this issue May 12, 2023 · 1 comment
Open
Tracked by #44

Add a persistent layer for the state of locks #54

CiottiGiorgio opened this issue May 12, 2023 · 1 comment
Labels
backend

Comments

@CiottiGiorgio
Copy link
Contributor

The idea is that the state of the locks should be persisted and linked to the job that acquired it.
This way, if a job fails and restarts, it will request a lock that was never released but it will still get it back by virtue of being the original workflow that acquired it.
The behavior should be that when a job acquires again a wallet that it already owned, it should renew the lease (#48), otherwise just fail.
@CiottiGiorgio CiottiGiorgio mentioned this issue May 12, 2023
Open
@CiottiGiorgio
Copy link
Contributor Author

Currently being addressed in #60

@CiottiGiorgio CiottiGiorgio changed the title Add a persistent SQLite layer for the state of locks Add a persistent layer for the state of locks May 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backend
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@solanoepalacio @CiottiGiorgio