Been consistently getting this error message over the past week trying to sync a city (Arvada, CO) from OSM and Iām starting to believe there is an issue. Doesnāt matter what time of day I run it; I havenāt been able to get it to sync even once. Thanks.
I think you might be right. I managed to get a job in the queue, but it have been running/stuck for hours.
Yeah ā¦ while Iāve seen the queue size drop at times, it has been overloaded in general lately.
I did some spot-checking, and it looks like the last couple days could have been caused by Greater London updates. Iām going to adjust city sync limits from daily to weekly (each person can request 5 city syncs per day, and each city can be synced once per 7 days) to see if that helps.
I also see some user-specific jobs, which usually correspond to people deleting activities or un-marking streets as manually completed. While debugging this issue, I added some logging that tells me when people delete activities & it doesnāt seem to correspond to these spikes.
3 Likes
lol I feel bad if I request more than 2 city syncs in a month
2 Likes
Same here. Those do seem to be quite generous limits. I generally only request a sync if I have just made significant updates in OSM or if I realized that a ācityā that I am attempting to complete hasnāt been updated in a few months.
Also, doing a manual sync of Greater London just seems odd, but perhaps I have misunderstood how nested cities work. I had assumed that an update in, say, Islington would filter through to GL automatically, but perhaps not.
yeah me too. It seems silly to do a sync every time I come across a āstreetā that is actually someoneās driveway, so I update OSM as I see them and order a sync about once a month.
I have to say, Iām still trying to sync Arvada. At this point it must have been dozens of attempts over the last week, and every single time it has failed this error.
Yeah, itās rough right now.
All the reprocessing that has to occur after activity deletions and city updates was taking too long ā¦ the worst about 1 minute per node, an average of 28 seconds ā¦ it effectively blocked city sync requests and activity deletions
Iāve got some updated code that drops the worst of them down to ~10s per node, with an average of ~30ms ā¦ Iām hopefully going to be able to re-enable everything later today (activity deletions & automatic city updates are currently disabled).
ok thank you!
FYI, about an hour ago, I was able to kick off an update for Arvada. It at least appears to be processing.
Yup, I managed to get one update done, which together with my OSM edits over the last month and the addition now of trunk roads has made a massive difference. I will do no more than one update a day (where that is possible) till all eight of mine are caught up. Thanks for the update.