-
Notifications
You must be signed in to change notification settings - Fork 10
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
Feature request: Add (configurable?) number of retries on fail or timeout #17
Comments
Hi, How are you handle the backup of your database ? If using MariaDB and mysqldump, you should consider mariabackup. nysqldump freezes the database during backup as mariabackup shouldn't: https://mariadb.com/kb/en/full-backup-and-restore-with-mariabackup/ Cheers, |
Another approach should be to configure a master-slave and perform the backup on the salve instance. |
we are using mariadb but the backup is done using the
that has been added to my wish list now .. :-) |
The You should consider mariabackup
Backup / restore operations: https://mariadb.com/kb/en/full-backup-and-restore-with-mariabackup/ |
Meanwhile I have added a slave database and now backups are performed on the slave side, no longer causing locks/interruptions of the passbolt instance every hour. |
I randomly encounter the same behavior when querying our self-hosted Passbolt. Some requests fail, result in a timeout, and cause the playbook to crash, even when a "retry" option is added to the Ansible tasks. It would be fantastic if the plugin could allow configuring the timeout and/or a retry mechanism. |
Once every hour we take an automated backup of the passbolt DB and keys. However this makes passbolt unresponsive or at least very slow during about 1 to 2 minutes.. But since we also run a lot of Ansible plays, with many lookups, it happens quite a lot that we get a timeout error from the lookup plugin at the times such a backup occurs.
So I would like to see the plugin to retry a few times before actually bailing out.
The text was updated successfully, but these errors were encountered: