[mythtv-users] Slow MySQL query after delete
Michael Rice
mikerice1969 at gmail.com
Wed Dec 5 07:07:24 UTC 2007
hOn Dec 4, 2007 10:42 PM, Chris Pinkham <cpinkham at bc2va.org> wrote:
> * On Wed Dec 05, 2007 at 12:16:45AM -0500, Michael T. Dean wrote:
> > 2007-12-04 22:00:08.327 scheduler: Scheduled items: Scheduled 265 items
> > in 2.8 = 0.00 match + 2.79 place
>
> It probably doesn't affect you much, but tonight I found an issue
> in the interaction between the delete code on the frontend and the
> scheduler on the backend. In current SVN, with the new Watch List,
> we update the 'last_delete' field in the record table whenever we
> delete a recording. This is done on the frontend before it tells
> the backend to delete the recording. This update hangs if the
> scheduler is currently running because the scheduler has an implicit
> read-only lock on the record table. So, for people who have long
> scheduler runs, if they try to delete a recording while the
> scheduler is running, they will experience a hang on the frontend
> until the scheduler's BUQ is finished.
That's exactly the problem I've been seeing (also the hanging in the
delete dialog mentioned in the ticket).
Thanks for looking into these!
More information about the mythtv-users
mailing list