-
Notifications
You must be signed in to change notification settings - Fork 40.7k
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
RedisReactiveHealthIndicator makes blocking call on error #16756
Closed
ayudovin
wants to merge
3
commits into
spring-projects:master
from
ayudovin:blocks-on-error-by-calling-close
Closed
RedisReactiveHealthIndicator makes blocking call on error #16756
ayudovin
wants to merge
3
commits into
spring-projects:master
from
ayudovin:blocks-on-error-by-calling-close
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
spring-projects-issues
added
the
status: waiting-for-triage
An issue we've not yet triaged
label
May 8, 2019
wilkinsona
added
the
status: waiting-for-feedback
We need additional information before we can continue
label
May 8, 2019
I filed DATAREDIS-977 to expose non-blocking connect methods. Right now, |
@wilkinsona, I would like to update PR |
@ayudovin The
|
wilkinsona
added
type: bug
A general bug
and removed
status: waiting-for-feedback
We need additional information before we can continue
status: waiting-for-triage
An issue we've not yet triaged
labels
May 9, 2019
philwebb
changed the title
RedisReactiveHealthIndicator blocks on error by calling close, which is not supported in thread reactor-http-epoll
RedisReactiveHealthIndicator makes blocking call on error
May 15, 2019
philwebb
added a commit
that referenced
this pull request
May 15, 2019
philwebb
added a commit
that referenced
this pull request
May 15, 2019
* pr/16756: Polish 'Drop blocking RedisReactiveHealthIndicator calls' Drop blocking RedisReactiveHealthIndicator calls
Thanks once again @ayudovin! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See #16705
While running a Spring Cloud Gateway application with Redis as session store, I observed the stack trace above. The cause is a blocking call in: https://github.com/spring-projects/spring-boot/blob/master/spring-boot-project/spring-boot-actuator/src/main/java/org/springframework/boot/actuate/redis/RedisReactiveHealthIndicator.java#L49
There is a
Mono<Void> closeLater();
https://github.com/spring-projects/spring-data-redis/blob/master/src/main/java/org/springframework/data/redis/connection/ReactiveRedisConnection.java#L68 which could be called instead.