-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
[query-frontend] Unable to connect to Redis(elasticache) 6.2.6 #7672
Comments
didukh86
added a commit
to didukh86/thanos
that referenced
this issue
Aug 28, 2024
Issue: thanos-io#7672 Signed-off-by: didukh86 <didukh86@gmail.com>
didukh86
added a commit
to didukh86/thanos
that referenced
this issue
Aug 28, 2024
Issue: thanos-io#7672 Signed-off-by: didukh86 <didukh86@gmail.com> Signed-off-by: didukh86 <78904472+didukh86@users.noreply.github.com>
didukh86
added a commit
to didukh86/thanos
that referenced
this issue
Aug 28, 2024
Issue: thanos-io#7672 Signed-off-by: didukh86 <didukh86@gmail.com> Signed-off-by: didukh86 <78904472+didukh86@users.noreply.github.com> Signed-off-by: didukh86 <didukh86@gmail.com>
didukh86
added a commit
to didukh86/thanos
that referenced
this issue
Sep 4, 2024
Issue: thanos-io#7672 Signed-off-by: didukh86 <didukh86@gmail.com> Signed-off-by: didukh86 <78904472+didukh86@users.noreply.github.com> Signed-off-by: didukh86 <didukh86@gmail.com> Signed-off-by: Taras Didukh <taras.didukh@advancedmd.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Thanos, Prometheus and Golang version used: Thanos 0.34.1, AWS Elasticache 6.2.6
Object Storage Provider: AWS
What happened: I'm trying to configure cache (Redis) for Query-Frontend. but I'm encountering an "error: creating redis client: context deadline exceeded", and the connection fails. I've configured the same settings for the index and bucket cache, and the cache connection for the store component is working fine.
What you expected to happen: Query-Frontend can connect to Redis
How to reproduce it (as minimally and precisely as possible):
Full logs to relevant components:
Anything else we need to know:
I found a similar issue in the link below(#6094)
The text was updated successfully, but these errors were encountered: