[Fwd: Re: Reliable supermaster setup - howto?]

View: New views
5 Messages — Rating Filter:   Alert me  

[Fwd: Re: Reliable supermaster setup - howto?]

by Ton van Rosmalen :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Fwd to list.

-------- Originele bericht --------

Hi,

Przemyslaw Wegrzyn schreef:

> Kenneth Marshall wrote:
>>> This leaves my initial question unanswered - how does such setup
>>> recover from lost notifications from supermaster to slave?
>>>
>>> As of PostgreSQL - my idea was to use PostgreSQL on master, and
>>> SQLite on slave, for simplicity, but that would render your patch
>>> useless, unfortunately. Where can I find the patch?
>>
>> The slave will check after the cache period times out. You could
>> also run a tickle script to check that you do not have any stale
>> zones.
> I'm not sure if I understand things right - I'm talking about a
> situation when I add a whole new zone to the master server, and I'd
> like the slave server to add it automatically as well. The zone is not
> yet configured on the slave, so it will not ask for that. It only asks
> when notified by master. So the only way to make it reliable, I
> suppose, is to repeat the notifications form master, until a
> successful AXFR to slave occurs.

In short, it doesn't. If the packet should get lost before the slave has
the zone in its database it won't get retried until a 'pdns_control
notify <domain>' is issued on the master.

Regards,

Ton


_______________________________________________
Pdns-users mailing list
Pdns-users@...
http://mailman.powerdns.com/mailman/listinfo/pdns-users

Parent Message unknown Re: [Fwd: Re: Reliable supermaster setup - howto?]

by Jesse Angell :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I am using MySQL for both my master and my slave.  I played with MySQL replication some but it just seemed over-kill for what I needed (I have a huge MySQL replicated environment for my web stuff).  I ended up just writing a simple script on the master that would do a mysqldump.  It would keep track of the checksum of the last dump and if it changed it would scp that mysqldump to the slave and restore it.

Runs every minute from cron...works great.  Ghetto -- but simple and trouble-free :)

----- Original Message -----
From: "Ton van Rosmalen" <ton@...>
To: "PDNS user-list" <pdns-users@...>
Sent: Friday, October 23, 2009 10:42:48 AM GMT -06:00 US/Canada Central
Subject: [Pdns-users] [Fwd: Re:  Reliable supermaster setup - howto?]

Fwd to list.

-------- Originele bericht --------

Hi,

Przemyslaw Wegrzyn schreef:

> Kenneth Marshall wrote:
>>> This leaves my initial question unanswered - how does such setup
>>> recover from lost notifications from supermaster to slave?
>>>
>>> As of PostgreSQL - my idea was to use PostgreSQL on master, and
>>> SQLite on slave, for simplicity, but that would render your patch
>>> useless, unfortunately. Where can I find the patch?
>>
>> The slave will check after the cache period times out. You could
>> also run a tickle script to check that you do not have any stale
>> zones.
> I'm not sure if I understand things right - I'm talking about a
> situation when I add a whole new zone to the master server, and I'd
> like the slave server to add it automatically as well. The zone is not
> yet configured on the slave, so it will not ask for that. It only asks
> when notified by master. So the only way to make it reliable, I
> suppose, is to repeat the notifications form master, until a
> successful AXFR to slave occurs.

In short, it doesn't. If the packet should get lost before the slave has
the zone in its database it won't get retried until a 'pdns_control
notify <domain>' is issued on the master.

Regards,

Ton


_______________________________________________
Pdns-users mailing list
Pdns-users@...
http://mailman.powerdns.com/mailman/listinfo/pdns-users
_______________________________________________
Pdns-users mailing list
Pdns-users@...
http://mailman.powerdns.com/mailman/listinfo/pdns-users

Re: [Fwd: Re: Reliable supermaster setup - howto?]

by Przemyslaw Wegrzyn-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Ton van Rosmalen wrote:

>> I'm not sure if I understand things right - I'm talking about a
>> situation when I add a whole new zone to the master server, and I'd
>> like the slave server to add it automatically as well. The zone is not
>> yet configured on the slave, so it will not ask for that. It only asks
>> when notified by master. So the only way to make it reliable, I
>> suppose, is to repeat the notifications form master, until a
>> successful AXFR to slave occurs.
>>    
>
> In short, it doesn't. If the packet should get lost before the slave has
> the zone in its database it won't get retried until a 'pdns_control
> notify <domain>' is issued on the master.
>  
It seems I'm convinced now, that database-level replication is way better :)
Thanks for the comment.

Cheers,
Przemek
_______________________________________________
Pdns-users mailing list
Pdns-users@...
http://mailman.powerdns.com/mailman/listinfo/pdns-users

Re: [Fwd: Re: Reliable supermaster setup - howto?]

by Przemyslaw Wegrzyn-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Jesse Angell wrote:
> I am using MySQL for both my master and my slave.  I played with MySQL replication some but it just seemed over-kill for what I needed (I have a huge MySQL replicated environment for my web stuff).  I ended up just writing a simple script on the master that would do a mysqldump.  It would keep track of the checksum of the last dump and if it changed it would scp that mysqldump to the slave and restore it.
>
> Runs every minute from cron...works great.  Ghetto -- but simple and trouble-free :)
>  
Isn't it amazing, that there is no out-of-the-box solution for such a
common task? Everybody seem to use some homebrewed solution.
I had some idea as well - make a python or perl script listening on a
socket (or spawned from inetd). Client side would connect and send last
update time (or counter, whatever), server would answer with set of
changed data, which the client would import into its local database. All
cron'ed.

Basically, there are many solutions, and none of theme is rocket
science, but I just don't want to reinvent the wheel. I'm probably going
to try PostgreSQL + Slony, simply because it is just ready and needs
configuring only. And because I've never used Slony before :)

Cheers,
Przemek
_______________________________________________
Pdns-users mailing list
Pdns-users@...
http://mailman.powerdns.com/mailman/listinfo/pdns-users

Re: [Fwd: Re: Reliable supermaster setup - howto?]

by Przemyslaw Wegrzyn-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Przemyslaw Wegrzyn wrote:
> Basically, there are many solutions, and none of theme is rocket
> science, but I just don't want to reinvent the wheel. I'm probably going
> to try PostgreSQL + Slony, simply because it is just ready and needs
> configuring only. And because I've never used Slony before :)
>  
Replying to my  own post - I looked at Slony, and it's way to heavy for
what I need. It requires very high database privilege level on both
sides, and I don't want to compromise database security for reason as
silly as sec DNS updates ;) Time to do something custom.

Cheers,
Przemek

_______________________________________________
Pdns-users mailing list
Pdns-users@...
http://mailman.powerdns.com/mailman/listinfo/pdns-users