Hi, we have been having a lot of trouble lately here at the NCC. Apart from some HW problems, that are now fixed, we are still receiving updates at a rate and in a combination that the DB can't presently handle in a fast way. All messages sent are queued and processed in turn. We are working on optimizing the software to handle these updates faster. Also we are going to deploy a queue control system to ensure a prompt response to updates more directly related to the RIPE DB intended purpose while still ensuring that others not so directly related will get processed. Currently we are processing the mails that were causing the problems with a lower priority to ensure an adequate service to the community. I will be presenting an in depth report on the situation next week at the RIPE meeting (DB wg). Shall the TLD wg also be interested in the some sort of presentation or overview I will be glad to present it. We have been reporting on the situation to this and other RIPE wgs and shall continue to do so. At this moment the situation is such that messages are being processed as in the good old days :-) Best regards, Joao Damas RIPE DB Group Manager RIPE NCC On Tue, 14 Sep 1999, Alfredo E. Cotroneo wrote:
Hi,
For the last ten days or so we have noticed that replies for a new contact handle to auto-dbm@ripe.net is taking much more than the usual 2-5 minutes as it used to be in the good old times ;-) Although we request only a few handles per month, a relly from RIPE takes now 10-20 hrs or more in some cases, regardless of the time (day or night, week or week-end) when the request is sent out.
I have heard of some kind of explanation related to SW/HW upgrades at RIPE and huge requests of handles being queued by some provider a few days ago, however, can someone at RIPE tell if the situation is going to be solved soon and when ?
Unfortunately this is causing at least an additional 1+ day delay in the registration of new domains at the Italian NIC, as IT-NIC requests that a handle exists for each contact before the domain registration form is submitted. Of course any comment from IT-NIC on how they can modify their internal procedures to minimize such delays (i.e. by IT-NIC requesting a new handle to RIPE directly) is also welcome.
Thanks.
-- Alfredo E. Cotroneo PO Box 11028, 20110, Milano, Italy Phone: +39-335-214-614 (try first) / +39-02-266-6971 email: alfredo@nexus.org fax: +39-02-706-38151
From: Joao Luis Silva Damas <joao@ripe.net>
Apart from some HW problems, that are now fixed, we are still receiving updates at a rate and in a combination that the DB can't presently handle ... All messages sent are queued and processed in turn.
This together with recent comments about domain objects in RIPE DB has started to worry me too. Our operation depends on RIPE's ability to register IP address assignments. Based on recent statistics it seems like we are suffering from reasons NOT related to addresses at all. http://www.ripe.net/meetings/ripe/ripe-33/pres/db-update/sld008.html
Also we are going to deploy a queue control system to ensure a prompt response to updates more directly related to the RIPE DB intended purpose while still ensuring that others not so directly related will get processed.
This tactful comment probably means a turn to the right direction. But I wish it was said loudly and clearly, maybe even as a complete change in DB usage policy. We pay for address registration services, please take the domain (non-rev-dns-related) objects elsewhere.
We have been reporting on the situation to this and other RIPE wgs and
Would it be possible to separate reverse DNS related domain objects from the big total of domain objects in RIPE DB report?
handles per month, a relly from RIPE takes now 10-20 hrs or more in some cases, regardless of the time (day or night, week or week-end) when the ... Unfortunately this is causing at least an additional 1+ day delay in the registration of new domains at the Italian NIC, as IT-NIC requests that a handle exists for each contact before the domain registration form is
-- Vesa Ruokonen - Internet Services, Telia Finland
participants (2)
-
Joao Luis Silva Damas
-
Vesa Ruokonen