-
Notifications
You must be signed in to change notification settings - Fork 985
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
Sentinel lookup connection leaks if no master address reported #1558
Comments
I'm not sure what you're asking for. Can you explain what you expect that should happen? |
if “c.reactive().getMasterAddrByName(sentinelMasterId)” is empty,”c::closeAsync “ should be called。 |
if “c.reactive().getMasterAddrByName(sentinelMasterId)” is empty,”c::closeAsync “ should be called。 |
Technically, I don't know why this happens, however, you're right, the connection remains open and causes a resource leak. Can you capture a log on trace level to see the actual Redis response? Independent from that, we need to fix the issue. |
The trace log is below.
|
Is there a way how to test that? I wasn't able to reproduce an empty response. However, going to fix the issue. |
…ugh Sentinel #1558 Previously, we used our own hooks to open and close the lookup connection that could leave connections open when no master node was found.
…ugh Sentinel #1558 Previously, we used our own hooks to open and close the lookup connection that could leave connections open when no master node was found.
…ugh Sentinel #1558 Previously, we used our own hooks to open and close the lookup connection that could leave connections open when no master node was found.
That's fixed now. |
Bug Report
Current Behavior
The collection to sentinel can't be closed when the master Id is error.
Input Code
Input Code
// your code here;
Expected behavior/code
The collection to sentinel with an exception should be closed.
Environment
Possible Solution
Additional context
The text was updated successfully, but these errors were encountered: