On 07/24/17 11:26, Kern Sibbald wrote: > Hello Phil, > > Well, Bacula does not send millions of rows at a time. It does already > batch data together and submits up to a maximum of 500,000 records at > one time. It has never been necessary to change that number because any > respectable database should be able to handle a batch of 500,000 records > at a time (about 50-100MB of data)-- even a cluster, in my opinion. I > suspect that the Galera guys are very sadly mistaken to suggest an > optimum of only 1,000 at a time for the size of the datasets we see some > Bacula customers using, and I will be *extremely* surprised if this > problem shows up in Oracle MySQL.
It doesn't show up in MySQL using native asynchronous single-threaded replication. There are very sound technical reasons for it when using Galera synchronous parallel replication, and I would not be in the least surprised to find a similar limitation in Oracle's MySQL Group Replication feature since Group Replication is basically Oracle's reverse-engineered Galera replication with the serial numbers filed off. > That said, you can experiment if you wish and try changing the maximum > number of rows (changes). It is in <bacula>/src/cats/sql_create.c at > line 870. If this is something that comes up frequently, we certainly > could put the maximum on a directive in the Catalog resource or perhaps > even elsewhere. Oh good! If it's a single change in one place, that should be very simple to test a fix for. I'll get right on it first chance I get. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
