[pybsddb] Problem scanning large hashed database

[Will Weisser]

I get the same error in my original process when starting another process
which calls lock_detect on the same database.  I suspect a problem with the
python binding as the db_deadlock utility does not show the same behavior.

On Wed, Dec 3, 2008 at 8:58 PM, andrew <andrew at reurbanise.co.nz> wrote:

> Hi All,
>
> I have a large-ish production database (1.6M objects) that usually gets
> accessed only for reads on writes on specific keys, for which it is nice
> and fast. However, I need to be able to do some adhoc queries on this
> data occasionally and I seem to be running into some problems doing
> that.
>
> My approach is simply to fetch all keys and then iterate through the
> keys, fetching the data for each key and then writing some of it to an
> output file. I want to do this while the database is still "up", i.e.,
> while a server process that allows access to the database via Pyro is
> still running. Unfortunately, when I run this scanning script (which
> takes minutes just to fetch all the keys) it seems to kill the Pyro
> process with:
>
> bsddb.db.DBRunRecoveryError: (-30978, 'DB_RUNRECOVERY: Fatal error, run
> database recovery -- PANIC: fatal region error detected; run recovery',
> 'This error occured remotely (Pyro). Remote traceback is available.')
>
> My questions are:
>
> 1. Is there a better way to do this ?
> 2. Could it be some sort of locking problem ?
> 3. Has anyone else done anything like this successfully ?
>
> Thanks for your help.
>
> Cheers, Andrew.
>
> _______________________________________________
> pybsddb mailing list
> pybsddb at argo.es
> http://mailman.argo.es/listinfo/pybsddb
> http://www.argo.es/~jcea/programacion/pybsddb.htm<http://www.argo.es/%7Ejcea/programacion/pybsddb.htm>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jcea.es/pipermail/pybsddb/attachments/20081204/05915c0b/attachment.htm>