Modify

Opened 6 days ago

Last modified 13 hours ago

#19934 new enhancement

Smarter retry mechanism to avoid thousands repeated requests in case of errors 500 from imagery servers

Reported by: rpnpif@… Owned by: team
Priority: normal Milestone:
Component: Core imagery Version:
Keywords: error retry Cc:

Description

An imagery server had temporary issues and sent errors 500 (internal error).
When aerial images was requested, JOSM repeated thousand times the request with logs, doing a great activity of my system CPU.

It should have a limit of the interval of time between requests in errors when they was repeated.

For example : after ten errors, the interval of request should be of 10 seconds, after 100 errors, 30 seconds, after 200 errors, 5 minutes.

Attachments (0)

Change History (3)

comment:1 Changed 6 days ago by skyper

Component: CoreCore imagery

comment:2 Changed 15 hours ago by Don-vip

Keywords: error retry added
Summary: Errors 500 on imagery servers makes thousands repeated requests of JOSMSmarter retry mechanism to avoid thousands repeated requests in case of errors 500 from imagery servers
Type: defectenhancement

comment:3 Changed 13 hours ago by stoecker

I usually use a factor of 1.5 for retry with an upper limit. E.g in seconds

0 1 2 3 5 8 12 18 27 ... 300 (rounded up and special for 0 to 1). This is extremely fast for short problems, but gets slow soon for larger outages.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to rpnpif@trob.eu
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.