Rene Wilhelm wrote:
Hi Arife,
I have noticed that it was not inserted for a while. The reason is the data we collect over there getting quite data, and DBinsert can not handle it anymore.
Ah, I see.
I do not know what the quick solution would be.
I will leave this ticket open and we will see how we can improve it.
The raw data on lama suggests the activity on rrc12 has come down again to more "normal" levels, at least disk usage is of the same order, even a bit lower, than that of rrc03 at ams-ix:
rrc00 rrc03 rrc12 Jan 430240 4312288 2009136 Feb 1174536 3503580 1822364 Mar 460220 3702528 2219576 Apr 730940 3544852 5987960 May 1997620 3488828 8392800 Jun 526332 851528 783260
Perhaps it is possible to switch DBinsert back on again while continuing investigation on how to deal with future hurricane size update storms?
It's not that dbinsert is not running, just that it's still processing data from April. To avoid this problem (and have current data inserted at the expense of delaying insertion of old data) dbinsert used to insert from the most recent file first ... but that then caused problems if an application assumed that database entries were in time-order. It might be worth flagging some of these old files as 'AI' or 'RI' in the updtlist table so that dbinsert will skip them and then gradually move them back to 'A'/'R' as processing time permits. James