-
Notifications
You must be signed in to change notification settings - Fork 412
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Calculating lots of isochrones can lead to "infinite loops"? #1897
Comments
Thanks for reporting. We haven't faced this behavior so far. Normally ORS should stop calculations once Things you could try to narrow down the issue:
If you have useful information in your log-file or a specific request that causes the issue you may also post it here. |
Hi @lenalebt , did you try any of @sfendrich 's suggestions? In case you have any new insights, it would be great if you could share them. Cheers! |
Hey together,
I created a thread dump using jstack directly from the container (I'm running it via docker). This is what the thread under question is doing currently (using the official docker image, version 8.2.0, with the command
I ran it a few times to find out whether it is changing, but it is always in that same line (Tri.java:564). I skipped all the parked threads. I can't say whether it always is that line, since I have only one thread that went wild in this moment. I can try it again when it happens again. Regarding the Cheers, |
Is there an existing issue for this?
Problem description
I am calculating lots of isochrones for different purposes, basically hammering ORS with isochrones requests for days in a row. In most cases, everything works just fine. Sometimes, ORS does not stop calculating an isochrone, which can lead to the whole server running crazy on CPU cycles on all cores without any perceivable output. The threads going crazy live for hours (basically until I manually stop ORS), although the Isos are "only" being calculated for up to 60 minutes (car). I would expect them to stop calculating when a certain size has been reached.
I do not yet have an idea what is actually happening. It does not happen immediately, but it's basically guaranteed to happen after a few hours. I find it hard to debug because I could not yet see for which request this might have started actually. I'm in for some debugging, but before I go deeper here:
Proposed solution
More debugging needed, wanted to ask first and then invest more time.
Additional context
ORS 8.2.0 from docker
ORS Settings:
Forum Topic Link
No response
The text was updated successfully, but these errors were encountered: