Hello Graham, Le jeudi 22 avril 2010 17:47:35, Graham Keeling a écrit : > Hello, > > I am not sure whether this is a bug or a feature request. I will happily > fill in the form for either, once somebody advises... > > The command that I run most often on bconsole is 'status director'. > > Unfortunately, bconsole often pauses for long periods of time during a > 'status director' request. For example, whilst the query that bug 1472 > talks about is running (generating accurate data). In that case, 'status > director' is blocked regularly for more than five minutes. The situation > is worse if there are multiple backups, each queuing up to make their > query. > This is particularly bad from the perspective of people who want to use > bconsole as the engine behind a graphical interface. > The user cannot get any idea of what is going on, and it seems as if bacula > is 'stuck' indefinitely. > > It would be very good if 'status director' could be tweaked so that it does > not get blocked. > It seems to be the 'list_scheduled_jobs()' function that waits for a lock > (LockRes()). > In the worse case, it could at least quickly return a message that states > that the resource is busy. But I think that it should be possible to do > better than that. >
The actual master code uses a dedicated sql connection for the VirtualFull query, it should no longer block. For normal Accurate backup, it uses dedicated connection since the beginning, so it's shouldn't block commands too. We planed to use a dedicated connection for command like "status dir", some users are also using the multidb catalog option that permits to use dedicated connection for each threads. (we don't test it through regression tests, so I cannot guarantee that it works all the time, but it's a workaround). Bye ------------------------------------------------------------------------------ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
