Skip to content

Conversation

sni
Copy link
Contributor

@sni sni commented Jun 14, 2023

if --store-queue-on-shutdown is used, database should only be accessed during shutdown and on initial startup. Skipping the done() saves the unnecessary query preparation, database locks, etc...

@sni sni force-pushed the improve-store-queue-on-shutdown branch from e898a86 to ced0d3a Compare June 14, 2023 21:13
@sni sni force-pushed the improve-store-queue-on-shutdown branch from ced0d3a to d3304a8 Compare June 16, 2023 14:10
if `--store-queue-on-shutdown` is used, database should only be accessed during
shutdown and on initial startup. Skipping the done() saves the unnecessary query
preparation, database locks, etc...

instead truncate queue database after successfully importing the retention database.

 - fixes gearman#369
@sni sni force-pushed the improve-store-queue-on-shutdown branch from d3304a8 to 120fb35 Compare June 18, 2023 17:28
@esabol
Copy link
Member

esabol commented Jun 18, 2023

CI tests pass, so I think we're good to merge here. The changes look good to me, but I haven't personally tested them. @sni , have you tested these changes on your system? And they work as desired?

@sni
Copy link
Contributor Author

sni commented Jun 19, 2023

yes, works as expected.

@esabol esabol merged commit 15bd982 into gearman:master Jun 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

sqlite db is constantly accessed even though --store-queue-on-shutdown is set
2 participants