[Pdns-users] Provisions for DB failures?

[Gabriel Ambuehl]

-----BEGIN PGP SIGNED MESSAGE-----

Hello bert,

Sunday, March 16, 2003, 8:44:54 PM, you wrote:

>         3) Simplicity is good

> In this case, if any of the slaves has a database problem, it goes
down. The
> other slaves continue to work and the internet does not notice that
there is
> a problem.

More or less. Except for the people that need to make two queries, of
course.

>         * somebody creates a *simple* algorithm for determining if a
> database is not working right

I suggest this: no algorithm at all. From what I've gathered,
everything needed is in place already as you can have multiple
backends. So what's needed is a mechanism that you can supply
additional DBs which are queried in case the first query would result
in a servfailed reply (I believe that's already happening if you have
different backends right?).

> Then we'd be willing to implement it. Let me know.


Now personally, what I'd love to see more than anything else (and more
than the above, of coure) is a dumb flat file based module that can be
used as second backend in case the DB fails. Say the flatfile gets
produced every X hours from the DB. This is relatively cheap
to generate (it could be done with a one line crontab entry,
actually) with any but very big installations where there are
usually other provisions taken that RDBMS don't go down.

Thoughts?



Best regards,
 Gabriel

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2i

iQEVAwUBPnTMTMZa2WpymlDxAQGctwf/YNxIGPviP7NOz6kszQJ5TNuB7Wyx2cJ1
Z+DR2T8Kf0yyg2WlVBxmvC1nBTdOcspR6IvkMFzJ2cGvC4ymj/F/dqMxldBdmxyW
ESh869AIOur0hudHer41WiF7Uj6A9Id35LrRDdLStGx5rGPr8jJV7R3Pn3YAWZk2
UXK06xKZiPQO21ACJttUz6wIfodxkgRLa39YfwjHrb7yqmmcrMI56NFsia/bOx/0
rW93gwenUJIo5nlkk9jZ4Rghu1grnRVNoUlAAWeum3oNW7Bhhu5NnQVQfqKGs3Df
SasUqIXOEZyeA5IgWjHE7dRggIFtY55/jlCQtZqJwF5pf0o24obMFA==
=5kij
-----END PGP SIGNATURE-----