forked from lbovet/vertx-redisques
-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is Vertx Redis API blocking? #165
Comments
Another example:
|
Merged
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why do I have the impression that vertx redis API seems to perform blocking IO on the eventloop?
See attached vertx-redis-client-blocking-EventLoop.log [6.7MiB].
I already opened #161 to fix one specific case. But still, I'm confused that redisAPI seems to be blocking.
Question 1: In which extent is my assumption correct here? Or do I see some other effect I'm not aware of?
Question 2: If my assumption is correct, does this mean ALL our calls to redis API throughout our codebase are potentially blocking the eventloop?
The text was updated successfully, but these errors were encountered: