danpat
commented
4 years ago The hot-swap mechanism built into OSRM is to use osrm-datastore to load data into shared memory, then run osrm-routed -s to read from shared memory instead of files on disk.
This is difficult to do using Docker, although it is possibls. See this StackOverflow summary of the IPC flags to docker run - https://stackoverflow.com/a/37716609
The recipe would be something like this:
wget http://download.geofabrik.de/europe/france/ile-de-france-latest.osm.pbf
docker run -t -v "${PWD}:/data" osrm/osrm-backend osrm-extract -p /opt/car.lua /data/ile-de-france-latest.osm.pbf
docker run -t -v "${PWD}:/data" osrm/osrm-backend osrm-partition /data/ile-de-france-latest.osrm
docker run -t -v "${PWD}:/data" osrm/osrm-backend osrm-customize /data/ile-de-france-latest.osrm
# Load the initial data into a shared memory segment on the host (outside the docker container)
docker run --ipc=host "${PWD}:/data" osrm/osrm-backend osrm-datastore /data/ile-de-france-latest.osrm
# Start up osrm-routed and attach it to shared memory rather than the files
docker run -d -t -i -p 1000:5000 osrm/osrm-backend osrm-routed --algorithm mld -s
# Now start your traffic loop
while /bin/true ; do
sleep 300 # Sleep for 5 minutes
wget http://somewhere/traffic.csv # EXAMPLE for fetching latest traffic data
# Update the base files with new traffic data
docker run -t -v "${PWD}:/data" osrm/osrm-backend osrm-customize /data/ile-de-france-latest.osrm --segment-speed-file traffic.csv
# Load new data into the shared memory region
docker run --ipc=host "${PWD}:/data" osrm/osrm-backend osrm-datastore /data/ile-de-france-latest.osrm
doneThe trick is the use of osrm-datastore, osrm-routed -s, and the --ipc=host flag to docker run.
A completely alternative approach would be to run a reverse proxy, say, nginx in front of osrm-routed, and using its "load balancer" feature to mark backends as healthy/unhealthy and seamlessly swap between them: https://docs.nginx.com/nginx/admin-guide/load-balancer/http-load-balancer/
This would still require some starting/stopping of osrm-routed, but if you have nginx in front, you can do it without losing any requests.
abdelhakimbendjabeur
nhaskins01
johnjinwoua
IqbalLx
github-actions[bot]
Hello,
I am experimenting on osrm locally using docker and I have been trying to customize the graph using custom segment speed files. I only see the effect of my speed when I relaunch the
osrm-routed.Here are the commands I used
and now I have a working web server on
localhost:1000Next I do is just get copy the speed file inside the container
<container-id>and run the followinglog output
Now when I make requests to the
/route/v1/driving/endpoint, the speed file does not seem to be taken into account. But when I kill the container and recreate one, then the speed is taken into account and I have the ETAs as expected.How can I customize the graph using a segment speed file and observe the change without having to create a new
osrm-routedcontainer? (i.e. Is there a way of applying the speed file without having to recreate the container?)side question: How recommended is this usage in production?
Thank you