[OSM-dev] Overpass-API 0.7.52 : HTTP 429 error even after kill_my_queries

Michael Larsen mvl.osm at network42.dk
Sun Jun 12 03:37:22 UTC 2016


Hi,

A while back I tried consuming augmented diffs from overpass API 
(sequentially, once per minute), with similar results.  My conclusion back 
then was that the rate limiting algorithm had other ways of attributing your 
load on overpass than merely the number of simultaneous connections. My guess 
is that your queries are simply 'too big' and placed 'too closely' in time to 
be allowed by the rate limiting algorithm. If you add some delay between your 
queries I guess they will be fine.

Back when trying to consume minutely augmented diffs I ended up concluding 
that this was not possible on a minutely basis due to the rate limiting 
algorithm, unfortunately.

Regards,
MichaelVL

On søndag den 12. juni 2016 00.53.08 CEST François Lacombe wrote:
> Hi all,
> 
> It seems that GET kill_my_queries request won't prevent oAPI to give HTTP
> 429 error.
> 
> I'm curently using a script which send synchronously 10 queries to oAPI on
> http://overpass-api.de/api (v0.7.52).
> It calls kill_my_queries between each (even if it sounds useless, just to
> really be sure no other request is still pending from my IP).
> 
> And this is what I get in the log :
> 
> [00:42:07] Kill Overpass-API OK : No query running from IP 1.2.3.4
> [00:42:08] oAPI request : [timeout:480];
> area["ISO3166-1"="FX"]["admin_level"="3"]->.france;  (node (area.france)
> ["power"="substation"] ["operator"="RTE"]  ["substation"="transmission"]
> ["ref:FR:RTE_nom"](newer:"2016-06-10T23:00:00+0200"); way  (area.france)
> ["power"="substation"]  ["operator"="RTE"]  ["substation"="transmission"]
> ["ref:FR:RTE_nom"](newer:"2016-06-10T23:00:00+0200")); out body;>; out skel;
> [00:42:23] HTTP 429 runtime error: open64: 0 Success
> /osm3s_v0.7.52_osm_base
> Dispatcher_Client::request_read_and_idx::rate_limited. Another request from
> your IP is still running.
> 
> [00:42:24] Kill Overpass-API OK : No query running from IP 1.2.3.4
> [00:42:25] oAPI request : [timeout:480];
> area["ISO3166-1"="FX"]["admin_level"="3"]->.france;  (node (area.france)
> ["power"="substation"]["substation"="distribution"]["ref:FR:RTE_nom"]
> (newer:"2016-06-10T23:00:00+0200"); way (area.france)
> ["power"="substation"] ["substation"="distribution"]["ref:FR:RTE_nom"]
> (newer:"2016-06-10T23:00:00+0200")); out body;>; out skel;
> [00:42:40] HTTP 429 runtime error: open64: 0 Success
> /osm3s_v0.7.52_osm_base
> Dispatcher_Client::request_read_and_idx::rate_limited. Another request from
> your IP is still running.
> 
> and so on...
> 
> Can someone explain why kill_my_queries tells there is no request and then
> an interpreter call fails in HTTP 429 ?
> 
> Kind regards
> 
> François
> 
> --
> *François Lacombe*
> 
> fl dot infosreseaux At gmail dot com
> www.infos-reseaux.com
> @InfosReseaux <http://www.twitter.com/InfosReseaux>





More information about the dev mailing list