Richard Ellis commented on BAHIR-130:

Trying to throttle the query to the returned rate limit assumes that there is 
nothing else running queries against the DB and if there is it will still fail. 
The approach followed in some of the other Cloudant libraries is to 
(optionally) retry requests that receive a 429 at an increasing back-off 
interval, which may be a more robust solution.

> Support Cloudant Lite Plan
> --------------------------
>                 Key: BAHIR-130
>                 URL: https://issues.apache.org/jira/browse/BAHIR-130
>             Project: Bahir
>          Issue Type: Improvement
>          Components: Spark SQL Data Sources
>    Affects Versions: Spark-2.0.0, Spark-2.0.1, Spark-2.0.2, Spark-2.1.0, 
> Spark-2.1.1, Spark-2.2.0
>         Environment: ApacheSpark, any
>            Reporter: Romeo Kienzer
>            Priority: Minor
>             Fix For: Spark-2.1.1, Spark-2.2.0
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> Cloudant has a plan called "Lite" supporting only five requests per second. 
> So you end up with the following exception:
> org.apache.spark.SparkException: Job aborted due to stage failure: Task 4 in 
> stage 0.0 failed 10 times, most recent failure: Lost task 4.9 in stage 0.0 
> (TID 42, yp-spark-dal09-env5-0040): java.lang.RuntimeException: Database 
> harlemshake2 request error: {"error":"too_many_requests","reason":"You've 
> exceeded your current limit of 5 requests per second for query class. Please 
> try later.","class":"query","rate":5}
>       at 
> org.apache.bahir.cloudant.common.JsonStoreDataAccess.getQueryResult(JsonStoreDataAccess.scala:158)
>       at 
> org.apache.bahir.cloudant.common.JsonStoreDataAccess.getIterator(JsonStoreDataAccess.scala:72)
> Suggestion: Change JsonStoreDataAccess.scala in a way that when a 403 HTTP 
> status code is returned the response is parsed in order to obtain the rate 
> limit and then throttle the query down to that limit. In addition issue a 
> WARNING in the log

This message was sent by Atlassian JIRA

Reply via email to