You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, when we get 429 errors, the node API is generally hammered with a whole bunch of additional requests due to the concurrent nature of the multiple NSQ consumers. It would be better to have these executed with a certain flow control (maximum rate), so that we can actually minimize the exponential back off and have better throughput.
The text was updated successfully, but these errors were encountered:
Currently, when we get 429 errors, the node API is generally hammered with a whole bunch of additional requests due to the concurrent nature of the multiple NSQ consumers. It would be better to have these executed with a certain flow control (maximum rate), so that we can actually minimize the exponential back off and have better throughput.
The text was updated successfully, but these errors were encountered: