Internal server error 500 when fetching large changesets #5247
Comments
Author: TomH This is (unfortunately) normal currently - they are just too big and complicated and in order to protect server resources we have a timeout in place which is what you are seeing. Hopefully one day the relation/full call will be moved into cgimap and we'll be able to handle larger relations. |
Author: ViriatoLusitano I see, should this ticket be closed since it's an already known issue? |
Author: TomH Well there are probably other tickets covering it, yes. |
Author: don-vip Replying to [comment:4 TomH]:
Yep, #4692 I think. |
Author: pnorman
relation/full is in cgimap, TomH presumably means the changeset download API call. |
Author: TomH Oh sorry, yes, whatever call this is ;-) |
Author: bastik It's an invitation to upload "unwanted" stuff and give people who have to fix it a hard time. What would be the solution when this happens? Maybe restrict the number of objects in one changeset to what can still be downloaded with |
Reporter: ViriatoLusitano
[Submitted to the original trac issue database at 9.12pm, Tuesday, 18th November 2014]
What steps will reproduce the problem?
Start JOSM
Open reverter plugin
Insert changeset 26757923
Wait up to 15 (or more) minutes since there is a lot of data
What is the expected result?
Should successfully download past changeset data without warning messages.
What happens instead?
A error message appears in roughly half of the attempts and every time at different points.
It is always a 500 Internal Server Error.
'''If any option is chosen an error message appears stating it's not possible to complete the request.
Please provide any additional information below. Attach a screenshot if possible.'''
The text was updated successfully, but these errors were encountered: