We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
The text was updated successfully, but these errors were encountered:
Mutex prevents parallel change notifications generatons
9e394b6
#963 A timed mutex was introduced and a lock on that, which prevents multiple processes to generate the changes notifications simultaneously.
teusbenschop
No branches or pull requests
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.
The text was updated successfully, but these errors were encountered: