Photon updates not working!?

[VonRehberg]

Hey guys,
I recently setup a nominatim instance in my kubernetes cluster and wanted to test the update functionality.
I found a typo in OSM and fixed it, and a day later the typo was fixed on my nominatim instance as well.

Yesterday I created a photon instance as well to test the fuzzy search. I connected it to my nominatim postgresql and started an update, but unfortunately the fixed typo was not reflected after the update...

Even your public instance still has the typo, although you claim it's up to date with OSM on a minutely base.
Here's the issue:
https://photon.komoot.io/api/?q=Martin%20Luther%20Lirche
Nominatim won't find it, as I fixed Lirche -> Kirche
https://nominatim.openstreetmap.org/search.php?q=Martin%20Luther%20Lirche&format=jsonv2

Is the update not working or is there something else off?

Best regards,
Joschi

[lonvia]

The demo instance at photon.komoot.io uses the Graphhopper dumps which are updated weekly. You'll see your changes by next Tuesday or so.

Regarding your local instance, you need to explain a bit more how you run updates for both the Nominatim and photon database.

[VonRehberg]

Ah I see. Thanks a lot I will try that.
But does that mean I will have to reimport the planet pbf?

[lonvia]

You have to do the Photon import again, I'm afraid, if you want to catch the updates you did. (Although just not bothering about them is probably just fine. It's unlikely that somebody searches for exactly that mistake that was fixed in the small interval you just updated.) Otherwise just switch to the photon update script and it should work fine for future updates. No need to reimport on the Nominatim side.

[VonRehberg]

Got it, guess you're right about the missing fixes ;-) I got a bit to concerned about making it perfect.

Now a not too important question:
From what I see so far, for each photon instance, we would need a nominatim instance. 1:1 because of the update process.
If I'm concerned about georeplication and load balancing of instances there is no way to have one nominatim instance, which delivers updates to 2 separate photon instances, right?

[lonvia]

No, that would require some evil hacking.

If you want load balancing, it might be better anyway to let ElasticSearch do the heavy lifting. You can run Photon against an external ES instance instead of using the embedded ES (see parameter -transport-addresses). You can then set up as many ES nodes as you like and have multiple Photons talk to them. Just be aware that a) you need to run an ES 5.6 and b) you need to be careful to really have only one Photon running the updates.

Oh, and the usual disclaimer: that's how it should work in theory, I've never tried that in practice. ;)

[VonRehberg]

Sounds reasonable. Thanks a lot for your help :-)