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.

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

Mutex on automatic versus manual change notifications generation #963

Closed
teusbenschop opened this issue Aug 17, 2024 · 0 comments
Closed
Assignees

Comments

@teusbenschop
Copy link
Member

The change notifications get generated every night.
These can also be generated manually.

If one process generates them, and another does that too, there's database clashes and errors in the journal.

Better would it be to use a unique mutex that processes can lock, preferably with a timeout on it, and if it falls in timeout, then to log that error.

@teusbenschop teusbenschop self-assigned this Sep 28, 2024
teusbenschop added a commit that referenced this issue Sep 28, 2024
#963

A timed mutex was introduced and a lock on that, which prevents multiple processes to generate the changes notifications simultaneously.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant