Mon Nov 12 12:51:16 PST 2012
- Previous message: [Slony1-general] replication fails to due bad DNS at startup, requires slony restart to fix
- Next message: [Slony1-general] replication fails to due bad DNS at startup, requires slony restart to fix
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I don't think most programs do any sort of TTL expiry of DNS lookups. It seems reasonable to me to restart a program upon DNS configuration changes. On Mon, Nov 12, 2012 at 2:33 PM, Mark Stosberg <mark at summersault.com> wrote: > Perhaps Slony aggressively caches DNS? Or perhaps it could recover from > this "FATAL" condition? Is this expected behavior, or should slony > behave better in the face of temporary DNS problems? > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.slony.info/pipermail/slony1-general/attachments/20121112/0e59329a/attachment.htm
- Previous message: [Slony1-general] replication fails to due bad DNS at startup, requires slony restart to fix
- Next message: [Slony1-general] replication fails to due bad DNS at startup, requires slony restart to fix
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list