[Tilesathome] "done" down and "active" through the roof

[Alex S.]

Matthias Julius wrote:
>> this was also partly due to the API downtime. I would estimate 10-15k
>> jobs there to be "lost".
> 
> Actually, I just checked the go_nogo script and it says the queue
> length is 3.50.  There simply are not more jobs processed because
> there are no more to process.  This would mean that all of the 16.15k
> jobs in "active" are actually "lost" and should be re_queued.

Undoubtedly, some of those have been manually re-queued already.

Does the server check for and remove entries from the 'active' list even 
if another client uploads the requested tileset?  If it doesn't, it 
should, else there will be some unnecessary re-rendering and processor 
time that could go toward another worthy goal if an automated re-queue 
is implemented.