Stephen, by the way, if you're not already aware of it:  You probably
want to set innodb_flush_log_at_trx_commit = 0.

The default value of this setting is 1, which causes the log buffer to
be written out to the lgo file and the logfile flushed to disk at every
transaction commit.  (Which obviously has a performance impact.)  With a
setting of 0, nothing is done at transaction commit, but the log buffer
is written to the log file and the log file flushed to disk once per
second.  There is a potential with this setting that up to the last full
second of transactions can be list in the event of a mysqld crash, but
... if mysqld crashes in the middle of Bacula inserting attributes, that
job is blown *anyway*, so there's really no loss.

I also suggest innodb_autoinc_lock_mode = 2, which allows InnoDB to
interleave auto_increment inserts.  This may possibly help with your
locking problem.  Keep in mind though that if you use this setting and
you have replication running, your binlog_format must be set to MIXED or
ROW.


-- 
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  alaric AT caerllewys DOT net   alaric AT metrocast DOT net   phil AT 
co.ordinate DOT org
  Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater
                 It's not the years, it's the mileage.

------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second 
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users