Hi everyone,
We are running OpenRouteService (ORS) with VROOM using Docker and have encountered an issue where our requests exceed the configured limits, despite updating the configuration.
Issue:
When sending a VROOM request with 1 vehicle and 73 jobs, we receive the following error:
{
"code": 3,
"error": "Request parameters exceed the server configuration limits. Only a total of 2500 routes are allowed."
}
This suggests that the ORS matrix service is enforcing a 2500 route limit, even though we have modified config-ors.yml to allow higher limits.
What We Have Tried:
- Increased ORS Matrix Limits in ors-config.yml:
services:
matrix:
enabled: true
maximum_routes: 10000
maximum_routes_flexible: 25
maximum_search_radius: 5000
maximum_visited_nodes: 100000
allow_resolve_locations: true
We confirmed that these changes are present inside the running ORS container using:
docker exec -it ors-app cat config/ors-config.yml
- Restarted ORS and VROOM containers after changes:
docker-compose down
docker-compose up -d
-
Verified VROOM Configuration:
cliArgs:
maxlocations: 1000 # Tried increasing to 5000
maxvehicles: 200
limit: ‘1mb’ # Increased to ‘10mb’
router: ‘ors’No changes in behavior after restarting VROOM. -
Directly Tested ORS Matrix API:
- When sending a smaller matrix request directly to ORS via curl, the response works fine.
- However, larger requests might still be failing due to hidden limits.
Questions:
a) Are there any additional ORS configuration files or environment variables that could still be enforcing the 2500 route limit?
b) Is there an internal caching mechanism that needs to be cleared when modifying config-ors.yml?
c) Could VROOM itself have an internal limit that we need to override separately from maxlocations?
We tried rebuilding the graph but no luck, same response.
Would really appreciate any guidance on this! Thanks in advance. 