We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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):
Anything else we need to know?
Environment:
juicefs --version
The text was updated successfully, but these errors were encountered:
@SandyXSD we should update the docs on how to adjust these connection parameters.
Sorry, something went wrong.
I'm afraid it's a too advanced topic.
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
SandyXSD
No branches or pull requests
What happened:
Connection to Redis failed when master went down.
What you expected to happen:
Automatically connect to the new master.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?
Environment:
juicefs --version
) or Hadoop Java SDK version: 1.0.0-beta1The text was updated successfully, but these errors were encountered: