Re: [Bacula-users] Fixing InnoDB lock wait timeouts

2010-03-08 Thread Jesper Krogh
Phil Stracchino wrote: > On 03/08/10 13:32, Jesper Krogh wrote: >> Phil Stracchino wrote: >>> If the problem still occurs, something else is going on. But this >>> should fix the problem in probably >99% of cases in which the 50-second >>> timeout is only infrequently being exceeded. >> It hugely

Re: [Bacula-users] Fixing InnoDB lock wait timeouts

2010-03-08 Thread Phil Stracchino
On 03/08/10 13:32, Jesper Krogh wrote: > Phil Stracchino wrote: >> If the problem still occurs, something else is going on. But this >> should fix the problem in probably >99% of cases in which the 50-second >> timeout is only infrequently being exceeded. > > It hugely depends on your fileset siz

Re: [Bacula-users] Fixing InnoDB lock wait timeouts

2010-03-08 Thread Jesper Krogh
Phil Stracchino wrote: > If the problem still occurs, something else is going on. But this > should fix the problem in probably >99% of cases in which the 50-second > timeout is only infrequently being exceeded. It hugely depends on your fileset sizes.. I have some in the order of 10m records.. a

[Bacula-users] Fixing InnoDB lock wait timeouts

2010-03-08 Thread Phil Stracchino
>From a routine weekly differential of a Windows 2000 client (Director and Catalog on a multicore Solaris 10 x86 server) with Bacula 3.0.3 running against MySQL 5.1: 08-Mar 03:47 babylon4-sd JobId 1398: Job write elapsed time = 00:08:54, Transfer rate = 2.641 M +bytes/second 08-Mar 03:49 babylon4