[Pdns-users] 4.2 to 4.3 Authoritative Upgrade path
Giovanni Vecchi
g.vecchi at certego.net
Tue Mar 17 11:15:53 UTC 2020
Hi Peter,
thanks for your quick reply.
If 4.2 queries do not ask for that field, I can't figure out what could go
wrong, isn't it?
Otherwise, what's the best upgrade path for this scenario? May I need to
stop every powerdns instance -> upgrade database schema -> upgrade every
powerdns instances -> start powerdns instances?
Thanks a lot
Thanks
On Tue, 17 Mar 2020 at 09:39, Pieter Lexis via Pdns-users <
pdns-users at mailman.powerdns.com> wrote:
> Hi Giovanni,
>
> On 3/16/20 6:11 PM, Giovanni Vecchi via Pdns-users wrote:
> > my scenario is the following:
> > - several 4.2 Authoritative servers
> > - multi-master database configuration (Percona XtraDB Cluster for
> instance)
> >
> > In order to upgrade to 4.3 and avoid downtime, is it safe to upgrade the
> > database schema first and every server then?
>
> The schema upgrade adds a field to the cryptokeys table and all queries
> from PowerDNS ask for specific field, not all fields. So it _should_ be
> safe. We do recommend testing it just to be sure :).
>
> Best regards,
>
> Pieter
>
> --
> Pieter Lexis
> PowerDNS.COM BV -- https://www.powerdns.com
> _______________________________________________
> Pdns-users mailing list
> Pdns-users at mailman.powerdns.com
> https://mailman.powerdns.com/mailman/listinfo/pdns-users
>
--
<http://www.certego.net/>
Giovanni Vecchi
Infrastructure Lead Engineer, Certego
+39-059-7353333
<http://www.linkedin.com/company/certego>
<http://twitter.com/Certego_IRT> <http://github.com/certego>
<http://www.youtube.com/CERTEGOsrl>
<http://plus.google.com/117641917176532015312>
Use of the information within this document constitutes acceptance for
use in an "as is" condition. There are no warranties with regard to
this information; Certego has verified the data as thoroughly as
possible. Any use of this information lies within the user's
responsibility. In no event shall Certego be liable for any
consequences or damages, including direct, indirect, incidental,
consequential, loss of business profits or special damages, arising
out of or in connection with the use or spread of this information.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20200317/7afcfa7e/attachment.htm>
More information about the Pdns-users
mailing list