google api - Webmaster API v3: getting servingLimitExceeded using batch requests -


i'm getting servinglimitexceeded error message results within batch not entire batch. example, may 100 records responding error , starts returning more results. within single batch.

if batches handled internally google api, how can adjust them not hit rate limit? tried adding 1-second delay between batches doesn't change this. set retries = 3 on ruby client, don't know if means retries failed batch. don't think it's retrying individual api calls within batch, because back-off should resolve this.

do have record failed results , create new batch recover separately?

incidentally, documented quota limit errors confusing. there dailylimitexceeded , ratelimitexceeded messages isn't returning 1 of those. servinglimitexceeded description of "the overall rate limit specified api has been reached" not helpful i'm assuming rate limit hit.

update

looking @ code, see retries in ruby google-api-client apply transmission , authorization (401) errors. 403 (which rate limit returns) raises clienterror not retried anyway.

so setting retries on client object has no bearing on this.

is there can address in batch?

we received word webmaster team api limited 20qps , there no way go higher.

one suggested solution make smaller batch requests.


Comments

Popular posts from this blog

c++ - Delete matches in OpenCV (Keypoints and descriptors) -

java - Could not locate OpenAL library -

sorting - opencl Bitonic sort with 64 bits keys -