Premeture Queue Processing

Question

Premeture Queue Processing

cbaines opened this issue 11 years ago · 4 comments

The strict queue dependencies I implemented in f708e63 (see the bottom of mongosm, in the save function) was later removed in 3e448b5 . Is this something that needs reimplementing, as it consistently breaks the geometry creation on smaller files, and has the potential to break the geometry creation in larger files?

Answer 1 · 2013-07-19T22:37:55.000Z

I pushed up this commit which should fix it.

Answer 2 · 2013-07-19T22:38:40.000Z

its on the dev branch, ill pull it in to master once you have given it a look.

Answer 3 · 2013-07-20T09:35:57.000Z

This does not quite do it, I have resolved some of the issues and submitted a pull request:
#12

However, this does not fix everything. The end logic is currently, if the queues are empty, and file has been read, close the database connection and end. This probably works most of the time, as the interval is long enough such that when it runs, everything has been saved to the database, but a situation could arise where the queues are empty, but things still are not saved to the database (saveCB's have not executed yet).

Answer 4 · 2013-07-20T16:36:55.000Z

In the current logic and the previous mentioned commits. The nodes decide when ways start, the ways decide when routs start. This breaks when running a file that only contains ways or only contains routes.