Skip to content
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

Follower cannot connect to master because of bad IP #1179

Open
astingengo opened this issue Dec 20, 2024 · 3 comments
Open

Follower cannot connect to master because of bad IP #1179

astingengo opened this issue Dec 20, 2024 · 3 comments
Labels
question Further information is requested

Comments

@astingengo
Copy link

Describe your question
I'm having a redis cluster (size: 3) and everything looks good except one follower (the other two are connecting to leaders correctly)
One follower is trying to connect to an unexisting leader IP.

20 Dec 2024 09:27:35.882 * Connecting to MASTER 10.42.2.147:6379                                                                                                                                                                                                                                                                                      │
20 Dec 2024 09:27:35.882 * MASTER <-> REPLICA sync started                                                                                                                                                                                                                                                                                            │
20 Dec 2024 09:27:38.692 # Error condition on socket for SYNC: Host is unreachable 

the problem is that my leader not connected with a follower IP is not 10.42.2.147 (I don't have that IP on any leader actually)

What version of redis-operator are you using?
redis-operator version: 0.18.1

Additional context
redis version: 7.0.12

@astingengo astingengo added the question Further information is requested label Dec 20, 2024
@husnialhamdani
Copy link
Contributor

A valid issue, I’m facing the same

@astingengo
Copy link
Author

astingengo commented Dec 23, 2024

So I think I know how to reproduce this.

  1. Have redis operator on version: 0.18.0
  2. Upgrade to 0.18.1
  3. Delete all redis pods and allow them to redeploy
  4. Check logs and you should see the errors

I completely removed the redis and redeploy it with operator 0.18.1 and can't reproduce the error now (but is not an upgrade from 0.18.0 is a fresh install of 0.18.1)

@husnialhamdani
Copy link
Contributor

cc @drivebyer

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants