On 08/04/18 00:21, John Nemeth wrote: > On Aug 3, 9:05am, Phil Stracchino wrote: > } Getting Bacula to work with a Galera cluster on the other hand is pretty > } straightforward. At the moment the principal thing you need to do for > } that is turn off attribute spooling, because the writeset limit in the > } attribute spooling code doesn't work. > > Ah, this would be the problem I ran across. I made the changes > to the schema and tried some test runs. That was okay, but when > I tried it with production backups it would fail when despooling > attributes. My C++ is pretty much non-existant (I spend my time > digging around inside kernels) so I ended up giving up and installing > yet another instant of mysqld on the box running the director.
Yup. Attribute despool on any job with more than 128K files will exceed Galera's hard writeset size limit. (128K rows/4GB, whichever comes first.) -- 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
