[development] problems with shutdown function in search module

[Gerhard Killesreiter]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi there,

our search module uses a shutdown function in its cron hook. While
re-indexing scratch.d.o to test Doug's patch, I encountered the
following situation:

1) There are runnign several update routines from search_update_totals
in parallel.

2) The final select query in that function run for hours.

I believe that 1) is caused by the fact that the shutdown function isn't
governed by our cron semaphore. That is, it runs until it is done and it
won't stop other cron jobs from running. So if there are enough dirty
workds to update, it is possible that there are several of them running
in parallel. I've seen as many as 5. Does anybody consider this a problem?

I have no idea what causes 2 but would be grateful for suggestions on
how to fix the problem.

Cheers,
	Gerhard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGtwc4fg6TFvELooQRAnfvAKCsAuBwTKd1cXBwO4QZ0LzEnLrbkgCgzEMm
7ZYafVkZRStDqb3tILCycqk=
=dyMQ
-----END PGP SIGNATURE-----