[Pdns-users] SQLite3 problem during stress

[Christian Svensson]

Yes, updating only one zone at the time is very much acceptable - that the
initial transfer takes quite long time does not matter.

We do not want to use an "active" database due to memory / CPU footprint. If
PowerDNS locks the table and let the other threads just wait for the lock
like any other mutex it would probably be just fine with distributor-threads
= 1.

I want to note that indeed PowerDNS _crashes_ / _exits_ in the end due to
the "Database is locked" error. Since I'm currently testing with OpenDBX I
don't know íf this is something that is regarded as an OpenDBX or PowerDNS
bug - but gsqlite3 did also crash during heavy load which (as stated before)
makes me believe that it's backend agnostic.

Greetings

Christian "BC" Svensson
Codelead Systems - http://www.codelead.se


On Sun, Jul 19, 2009 at 10:46 PM, Norbert Sendetzky <
norbert at linuxnetworks.de> wrote:

> On Sun July 19 2009 19:21:56 bert hubert wrote:
> > > SQLite is only useful for small installations and a few domains because
> > > it uses table locks when it writes the changes to the database. As each
> > > zone
> >
> > That may be so, but it should still not crash.
>
> Like I wrote to Bert in a private mail:
> It doesn't crash but the handling of timeouts is suboptimal. I will create
> a
> patch that will improve this.
>
>
> Norbert
> --
> OpenPGP public key
> http://www.linuxnetworks.de/norbert.pubkey.asc
>
>
>
> _______________________________________________
> Pdns-users mailing list
> Pdns-users at mailman.powerdns.com
> http://mailman.powerdns.com/mailman/listinfo/pdns-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20090720/12d9a930/attachment-0001.html>