Automatic flushing of the jnl files

[Howard, Christopher]

Oh, well that's good to know. :)

-Christopher



On 1/21/15, 12:18 PM, "Chris Thompson" <cet1 at cam.ac.uk> wrote:

>On Jan 21 2015, Howard, Christopher wrote:
>
>>The journal files get flushed to the zone file periodically, but old
>>transactions don't get removed so the journal file will continue to grow
>>forever.  If you're like me and on virtual machines with limited hard
>>disk
>>capacity, you can limit the journal file size with the max-journal-size
>>configuration statement. Just make sure that the size is large enough to
>>hold all of the transactions between flushes (I believe that's around
>>every 15 minutes).  Otherwise, after a crash you would be missing
>>records.
>
>I am fairly sure you are wrong on that last point. BIND will not flush
>journal file entries that have not yet been committed to the master file,
>even if they make the journal bigger than max-journal-size. If you specify
>"max-journal-size 512;" you will find the journal gets emptied completely,
>but only after the master file has been updated. (Of course, as Phil
>Mayers
>points out, this would cause downstream IXFRs to become AXFRs,)
>
>-- 
>Chris Thompson
>Email: cet1 at cam.ac.uk
>
>_______________________________________________
>Please visit https://lists.isc.org/mailman/listinfo/bind-users to
>unsubscribe from this list
>
>bind-users mailing list
>bind-users at lists.isc.org
>https://lists.isc.org/mailman/listinfo/bind-users