Re: Operational Notification: Extremely large zone transfers can result in corrupted journal files or server process termination
Am 14.07.2018 um 00:38 schrieb Matthew Pounsett: > On 13 July 2018 at 06:04, Michał Kępień wrote: > >> Hopefully this will shed some light on the matter: >> >> https://gitlab.isc.org/isc-projects/bind9/issues/339#note_12805 >> >> That is helpful, thanks. That comment says the issue requires a journal > entry of over 4G, however the original bug report indicates it was > triggered by a 1.6GiB IXFR. But then I suppose there's not a 1:1 > relationship between the size of the zone transfer and the size of the > journal entry. The journal increases over time until it reaches "max-journal-size" which will trigger a journal clean-up. I supsect if the journal is eg. 3G and you have an 1.6 IXFR it may crash your bind. regards Klaus ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Operational Notification: Extremely large zone transfers can result in corrupted journal files or server process termination
On 13 July 2018 at 06:04, Michał Kępień wrote: > Hopefully this will shed some light on the matter: > > https://gitlab.isc.org/isc-projects/bind9/issues/339#note_12805 > > That is helpful, thanks. That comment says the issue requires a journal entry of over 4G, however the original bug report indicates it was triggered by a 1.6GiB IXFR. But then I suppose there's not a 1:1 relationship between the size of the zone transfer and the size of the journal entry. Thanks for the info! ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Operational Notification: Extremely large zone transfers can result in corrupted journal files or server process termination
> > What is an "extraordinarily large zone transfer"? We do have regularly > > AXFR and IXFRs around 2GB. Is this "extraordinarily large"? > > > > I've also been curious about this. Are we talking millions of records, > tens or hundreds of millions, or billions? Hopefully this will shed some light on the matter: https://gitlab.isc.org/isc-projects/bind9/issues/339#note_12805 -- Best regards, Michał Kępień ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Operational Notification: Extremely large zone transfers can result in corrupted journal files or server process termination
On 9 July 2018 at 16:22, Klaus Darilion wrote: > What is an "extraordinarily large zone transfer"? We do have regularly > AXFR and IXFRs around 2GB. Is this "extraordinarily large"? > I've also been curious about this. Are we talking millions of records, tens or hundreds of millions, or billions? ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
