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
Why does RedisQues spread those 'redisAPI' calls to several threads in QueueStatisticsCollector? It should be just fine to call 'redisAPI.send()' directly from EventLoop. Unluckily, original code does not tell us anything about this.
IMHO there are TWO ways to resolve this issue:
Make sure redisAPI never ever blocks the EventLoop thread so we can just remove 'executeBlocking()' and call 'redisAPI' directly.
Explain, AS A COMMENT, DIRECTLY WITHIN THE AFFECTED CODE, in an UNAMBIGUOUS way, WHY RedisQues has to use 'executeBlocking()' in this specific case. I guess maybe Is Vertx Redis API blocking? #165 could be the reason?
The text was updated successfully, but these errors were encountered:
Why does RedisQues spread those 'redisAPI' calls to several threads in QueueStatisticsCollector? It should be just fine to call 'redisAPI.send()' directly from EventLoop. Unluckily, original code does not tell us anything about this.
IMHO there are TWO ways to resolve this issue:
The text was updated successfully, but these errors were encountered: