increase daily db dump frequency?
Hi RIPE NCC, WG, I have a use-case in which secondaire NRTM mirrors can't easily reseed from the data stored at ftp.ripe.net:/ripe/dbase/ because the intermediate NRTM mirror retains less history than the actual delta between when the dump was made and the current serial. In other words, if I want to reseed an IRR instance I have to do so before lunch (UTC), because after lunch the delta usually is too large. This can be mitigated if the dump files in ftp.ripe.net:/ripe/dbase/split are refreshed more often then once a day. Would it be possible to dump every 6 hours instead of every 24 hours? Kind regards, Job
I agree with Job and would also like to see the frequency change. Thanks, Billy
On Feb 19, 2016, at 4:36 AM, Job Snijders <job@ntt.net> wrote:
Hi RIPE NCC, WG,
I have a use-case in which secondaire NRTM mirrors can't easily reseed from the data stored at ftp.ripe.net:/ripe/dbase/ because the intermediate NRTM mirror retains less history than the actual delta between when the dump was made and the current serial.
In other words, if I want to reseed an IRR instance I have to do so before lunch (UTC), because after lunch the delta usually is too large.
This can be mitigated if the dump files in ftp.ripe.net:/ripe/dbase/split are refreshed more often then once a day.
Would it be possible to dump every 6 hours instead of every 24 hours?
Kind regards,
Job
On Fri, Feb 19, 2016 at 02:36:19PM +0000, William Sylvester wrote:
I agree with Job and would also like to see the frequency change.
+1 Piotr -- gucio -> Piotr Strzyżewski E-mail: Piotr.Strzyzewski@polsl.pl
Dear WG, We’re investigating the possibility of increasing the frequency of refreshing the split files on the FTP site and the impact it would have for other users. As an alternative solution, can you use our primary mirror since it’s up-to-date? Kind regards, Thiago da Cruz Software Engineer - RIPE NCC Database Team
On 19 Feb 2016, at 10:36, Job Snijders <job@ntt.net> wrote:
Hi RIPE NCC, WG,
I have a use-case in which secondaire NRTM mirrors can't easily reseed from the data stored at ftp.ripe.net:/ripe/dbase/ because the intermediate NRTM mirror retains less history than the actual delta between when the dump was made and the current serial.
In other words, if I want to reseed an IRR instance I have to do so before lunch (UTC), because after lunch the delta usually is too large.
This can be mitigated if the dump files in ftp.ripe.net:/ripe/dbase/split are refreshed more often then once a day.
Would it be possible to dump every 6 hours instead of every 24 hours?
Kind regards,
Job
On Mon, Feb 22, 2016 at 03:55:04PM +0100, Thiago da Cruz Pereira wrote:
We’re investigating the possibility of increasing the frequency of refreshing the split files on the FTP site and the impact it would have for other users.
Thank you.
As an alternative solution, can you use our primary mirror since it’s up-to-date?
No. My requirement in this case is to use our own mirrors. Kind regards, Job
Hi Job, WG, We investigated this. The split files take around 4,5 hours to generate, due to the size of the database. We could raise the frequency to every six hours, i.e. four times per day. It would require significant resources from one of the slave nodes, but under normal circumstances this should not be an issue. Please let us know if you think this would be valuable. Also, others, please let us know if you would expect any practical problems on your side if split files are produced more frequently. Kind regards, Tim Bruijnzeels
On 22 Feb 2016, at 16:02, Job Snijders <job@instituut.net> wrote:
On Mon, Feb 22, 2016 at 03:55:04PM +0100, Thiago da Cruz Pereira wrote:
We’re investigating the possibility of increasing the frequency of refreshing the split files on the FTP site and the impact it would have for other users.
Thank you.
As an alternative solution, can you use our primary mirror since it’s up-to-date?
No. My requirement in this case is to use our own mirrors.
Kind regards,
Job
On Tue, Mar 15, 2016 at 12:02:27PM +0100, Tim Bruijnzeels wrote:
We investigated this. The split files take around 4,5 hours to generate, due to the size of the database.
We could raise the frequency to every six hours, i.e. four times per day. It would require significant resources from one of the slave nodes, but under normal circumstances this should not be an issue. Please let us know if you think this would be valuable. Also, others, please let us know if you would expect any practical problems on your side if split files are produced more frequently.
4,5 hours borders close to filling up the 6 hour window. Therefor I propose, that if we increase the frequency, we change it to once every 12 hours. I look forward to more feedback. Kind regards, Job
participants (6)
-
Job Snijders -
Job Snijders -
Piotr Strzyzewski -
Thiago da Cruz Pereira -
Tim Bruijnzeels -
William Sylvester