You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the problem
When connecting to a TLS enabled cluster (specifically AWS Elasticache, but doesn't seem relevant), there is a timeout when refreshing cluster slots due to TLS not being enabled.
In the gomodule/redigo library, which is a dependency of mna/redisc there are two pathways to connect that are being utilized by redis_exporterDial and DialURL
DialURL is used when connecting not in cluster mode, and Dial is used when clustering is enabled.
Describe the problem
When connecting to a TLS enabled cluster (specifically AWS Elasticache, but doesn't seem relevant), there is a timeout when refreshing cluster slots due to TLS not being enabled.
In the
gomodule/redigo
library, which is a dependency ofmna/redisc
there are two pathways to connect that are being utilized byredis_exporter
Dial
andDialURL
DialURL
is used when connecting not in cluster mode, andDial
is used when clustering is enabled.Clustering Enabled:
https://github.com/oliver006/redis_exporter/blob/de4f5eb0bfc3e15e3aa882db262572ed3bb45dcb/exporter/redis.go#LL98C10-L98C10
Clustering Disabled:
https://github.com/oliver006/redis_exporter/blob/de4f5eb0bfc3e15e3aa882db262572ed3bb45dcb/exporter/redis.go#LL53
The problem here is that in the
redigo
lib when usingDialURL
it automatically appends theDialUseTLS
DialOption when the scheme is set torediss
. This does not happen inDial
https://github.com/gomodule/redigo/blob/d6854479365f0307560fa28e18e2bd0634b05229/redis/conn.go#L389
What version of redis_exporter are you running?
Please run
redis_exporter --version
if you're not sure what version you're running.1.48.0
Running the exporter
What's the full command you're using to run the exporter? (please remove passwords and other sensitive data)
Expected behavior
Exporter does not time out when attempting to refresh cache slots on a TLS enabled cluster.
Screenshots
N/A
Additional context
N/A
The text was updated successfully, but these errors were encountered: