Rate limits from new IBM Bluemix Cloudant plans are not managed by the connector about loopback-connector-cloudant HOT 13 CLOSED

It seems like this issue is actually about not supporting plugin configuration in the connector; we're not passing through an options object that allows configuration of the nodejs-cloudant module.
https://github.com/strongloop/loopback-connector-cloudant/blob/master/lib/cloudant.js#L56
cc @superkhau @jannyHou

from loopback-connector-cloudant.

It would be great if StrongLoop's Cloudant connector could wrap Cloudant's nodejs library. The Shared plan has been deprecated in favour of the new rate-capped Lite & Standard plans, and at the moment SL dies when used against the Lite plan. The Lite plan is intended to serve as a free-forever taster/development tier but applications using that need to be mindful of the caps. Cloudant's library has configurable backoff&retry handling through its retry plugin.

Stefan Kruger, IBM Cloudant.

from loopback-connector-cloudant.

@xpqz Thanks for the feedback, this is definitely something we should take into consideration (using the native nodejs library that supports rate-capped lite and standard plans).

@jannyHou We should add this to your connector's roadmap doc -- high priority too because this is obviously a barrier to entry for this project.

from loopback-connector-cloudant.

Hi, do we have an idea when the 3.0.0 will be released?

from loopback-connector-cloudant.

@patsvc I'll add this to our backlog. It's not a breaking change, so I imagine it wouldn't be too much work.

from loopback-connector-cloudant.

I tried a local fix l2fprod@f342236 enabling the retry plugin and obviously it solves the issue. Ideally this should be built-in into the connector with configuration from the datasource.

from loopback-connector-cloudant.

@kjdelisle you're right. I've a straightforward fix l2fprod@f342236 for my own app but would love to see plugin support built in the connector!

from loopback-connector-cloudant.

I've merged the passthrough into the master stream, and it should be a part of the connector's 3.0.0 release when that time comes.

from loopback-connector-cloudant.

Any plans to port this to the LTS release? We would really like to have this fix because we keep hitting these limits.

from loopback-connector-cloudant.

This should be released on v1.2.3

from loopback-connector-cloudant.

Hi, still running into this issue after upgrading to 1.2.3 and adding the following to my datasource config:
'plugin': 'retry', 'retryAttempts': 5, 'retryTimeout': 1000

Seems like the issue is caused by a validatesUniquenessOf constraint added to my model.
Indeed, when performing a bulk create with this model, I get the following 422 error:
uniqueness.Error: You've exceeded your current limit of 5 requests per second for query class. Please try later."
Removing the uniqueness constraint solves the issue, but is not an acceptable solution.

Any advice?

from loopback-connector-cloudant.

@jmereaux Is your model a User model or just a regular persistedModel? And which cloudant server are you using? A bluemix one or docker one or?

from loopback-connector-cloudant.

@jannyHou It is a regular PersistedModel. I'm using a Cloudant server on Bluemix (standard plan = 100 lookups/s, 50 writes/s, 5 queries/s)

from loopback-connector-cloudant.