[OSM-dev] Data corruption :) II

[Stefan de Konink]

Tom Hughes wrote:
> That would be a backward step - we have perfect synchronisation at the 
> moment so why move to a situation where you may get old data, even if 
> only a few minutes old?

Because your perfect synchronisation is in one place: London. Your users 
are all over the world.

>>> + loss of control unless all proxy targets are maintained by
>>>   the OSM admin team
>>
>> The OSM admin team maintains the proxy. And targets get checked if 
>> they have the latest minutely's every hour -> if not, remove from pool.
> 
> Absolutely not. That way leads to chaos. We know this from the t at h proxy 
> experience where there was always at least one server that didn't seem 
> to be working.

If not working; not in the pool? That is pretty trivial. Just an 
automatic script.

>>>> What is the down time you expect for 0.6 migration?
>>>
>>> We are still attempting to quantify that.
>>
>> New server an option?
> 
> Moving to a new database server is part of the migration plan.

Then why would there be any serious downtime then? (Longer than 5 
minutes to synchronise with the latest diff)


Stefan