George, Right at the moment, I don't recommend using MariaDB. They are just now fixing a very serious false deadlock detection bug that causes Bacula to fail. ========= Copy paste from a recent email ============= [ https://jira.mariadb.org/browse/MDEV-13333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Lindström closed MDEV-13333. -------------------------------- Fix Version/s: 10.1.36 10.2.18 10.3.10 (was: 10.2) (was: 10.1) (was: 10.3) Resolution: Fixed Deadlock failure that does not occur elsewhere ---------------------------------------------- Key: MDEV-13333 URL: https://jira.mariadb.org/browse/MDEV-13333 Project: MariaDB Server Issue Type: Bug Components: Locking, Storage Engine - InnoDB Affects Versions: 10.2.7 Environment: MariaDB installed using repo on your site to Ubuntu 16.04. Reporter: Kern Sibbald Assignee: Jan Lindström Fix For: 10.1.36, 10.2.18, 10.3.10 Attachments: mariadb-bug, mdev13333.test, output_b MariaDB gets the following deadlock error: localhost-dir: sql_create.c:837-5 Fill File table Query failed: INSERT INTO File (FileIndex, JobId, PathId, FilenameId, LStat, MD5, DeltaSeq) SELECT batch.FileIndex, batch.JobId, Path.PathId, Filename.FilenameId,batch.LStat, batch.MD5, batch.DeltaSeq FROM batch JOIN Path ON (batch.Path = Path.Path) JOIN Filename ON (batch.Name = Filename.Name): ERR=Deadlock found when trying to get lock; When running the Bacula 9.0.1 regression script named: three-pool-virtual-test This does not occur on any version of MySQL, nor the Ubuntu version 10.0 of MariaDB. The code has been stable for many years. I am running all instances of MariaDB and MySQL out of the box. I have changed no parameters. This appears to be a false deadlock detection. Note, it is 100% reproducible. On 08/07/2018 02:05 AM, George Anchev
via Bacula-users wrote:
Today I installed 9.2.0 FD on one of the network workstations. Trying to run an estimate for an incremental job tells me that "Job 0" cannot find previous Full backup, so it will estimates a full one. My workaround with changing the SQL_MODE didn't work in this case. On Mon, 6 Aug 2018 16:37:02 -0400 Phil Stracchino wrote:ALTER TABLE Media MODIFY FirstWritten datetime DEFAULT NULL, MODIFY LastWritten datetime DEFAULT NULL, MODIFY LabelDate datetime DEFAULT NULL, MODIFY InitialWrite datetime DEFAULT NULL;Can anyone please confirm if that is all that is required to get rid of all these MariaDB related issues? Also - how safe is it? (I really know very little about DBs). The other day I also filed a bug report about the issue: https://bugs.bacula.org/view.php?id=2408 Perhaps if we have a script to update our DBs it would suffice. -- George ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users |
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users