Re: Operational Notification: Extremely large zone transfers can result in corrupted journal files or server process termination

2018-07-16 Thread Klaus Darilion via bind-users
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

Re: Operational Notification: Extremely large zone transfers can result in corrupted journal files or server process termination

2018-07-13 Thread 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

Re: Operational Notification: Extremely large zone transfers can result in corrupted journal files or server process termination

2018-07-13 Thread Michał Kępień
> > 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

Re: Operational Notification: Extremely large zone transfers can result in corrupted journal files or server process termination

2018-07-12 Thread Matthew Pounsett
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