Skip to content

reopen(v9): checkConn for badConn(#1821, #1824), alwaysNewConn(#1737) #2053

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.

Sign up for GitHub

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

Jump to bottom
Closed
monkey92t opened this issue Mar 19, 2022 · 0 comments
Closed

reopen(v9): checkConn for badConn(#1821, #1824), alwaysNewConn(#1737) #2053

monkey92t opened this issue Mar 19, 2022 · 0 comments

Comments

@monkey92t
Copy link
Collaborator

monkey92t commented Mar 19, 2022 •
edited
Loading

checkConn: #1821, #1824
alwaysNewConn: #1737
link: #1849 (comment)

Works on the v9 branch.
@monkey92t monkey92t added the v9 label Mar 19, 2022
@naiqianz naiqianz mentioned this issue Mar 19, 2022
Merged
naiqianz added a commit to naiqianz/go-redis that referenced this issue Mar 19, 2022
@naiqianz
fix: badConn check(redis#2053)
c019094
monkey92t pushed a commit that referenced this issue Mar 20, 2022
@naiqianz
feat(pool): add check for badConnection
a8a7665 
* fix: badConn check(#2053)

* fix: internalpool test

* fix: sentinel test

* fix: conncheck ut

* fix: remove maxBadConnRetries

* fix: add connCheck.deadline check

Signed-off-by: monkey92t <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vmihailenco @monkey92t