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

Connection failed when Redis master down #1593

Closed
SandyXSD opened this issue Mar 17, 2022 · 3 comments
Closed

Connection failed when Redis master down #1593

SandyXSD opened this issue Mar 17, 2022 · 3 comments
Assignees
Labels
kind/bug Something isn't working
Milestone

Comments

@SandyXSD
Copy link
Contributor

What happened:
Connection to Redis failed when master went down.

redis: 2022/03/17 05:37:39 sentinel.go:536: sentinel: GetMasterAddrByName name="redis" failed: dial tcp {old-master}:26379: i/o timeout
2022/03/17 05:37:39.428142 juicefs[7] <ERROR>: error: redis: connection pool timeout

What you expected to happen:
Automatically connect to the new master.

How to reproduce it (as minimally and precisely as possible):

  • Redis sentinel mode
  • Power down the Redis master node

Anything else we need to know?

Environment:

  • JuiceFS version (use juicefs --version) or Hadoop Java SDK version: 1.0.0-beta1
  • Metadata engine info (version, cloud provider managed or self maintained): Redis server v=6.2.6
@SandyXSD SandyXSD added the kind/bug Something isn't working label Mar 17, 2022
@davies davies added this to the Release 1.0 milestone Mar 18, 2022
@davies davies closed this as completed Mar 22, 2022
@davies
Copy link
Contributor

davies commented Mar 22, 2022

@SandyXSD we should update the docs on how to adjust these connection parameters.

@SandyXSD
Copy link
Contributor Author

I'm afraid it's a too advanced topic.

@Nick-0314
Copy link

I added a proxy (k8S service or any other load balancer with health check) in front of Sentinel, which effectively solved the sentinel Timeout problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants