mrmaddy99 opened a new issue, #14037: URL: https://github.com/apache/apisix/issues/14037
### Current Behavior When `limit-count` (or any plugin using `apisix/utils/rediscluster.lua`) is configured with a **TLS-enabled** Redis cluster (`redis_cluster_ssl = true`), the health check in the bundled `lua-resty-redis-cluster` connects over plain TCP. The TLS server rejects it, so every node fails the check and is eventually marked unhealthy, even though the cluster is fine. The root cause is in the dependency, not in APISIX itself. In `lua-resty-redis-cluster` , `run_health_check` calls `red:connect(ip, port)` without `config.connect_opts`. All other connect calls in that file pass the options. Upstream issue: https://github.com/api7/lua-resty-redis-cluster/issues/19 Upstream file: https://github.com/api7/lua-resty-redis-cluster/blob/v1.3.3/lib/resty/rediscluster.lua ### Expected Behavior With `redis_cluster_ssl = true`, health checks should connect with TLS, and a healthy cluster should not be marked unhealthy. ### Error Logs 2026/10/02 23:59:57 [error] 74#74: *47074186 [lua] rediscluster.lua:80: health check failed for: rediscluster-shard.redis-cluster:6379 - failures: 154388, context: ngx.timer 2026/10/02 23:59:56 [error] 74#74: *47074122 [lua] rediscluster.lua:80: health check failed for: rediscluster-shard.redis-cluster:6379 - failures: 154387, context: ngx.timer . . . 2026/10/02 23:59:58 [error] 74#74: *47074272 [lua] rediscluster.lua:80: health check failed for: rediscluster-shard.redis-cluster:6379 - failures: 154389, context: ngx.timer . . untill retry ### Steps to Reproduce 1. Run a Redis cluster with TLS enabled. 2. Configure a route with `limit-count`, `policy: redis-cluster`, `redis_cluster_nodes`, `redis_cluster_name`, and `redis_cluster_ssl: true`. 3. Send traffic and watch the error log. Health check failures appear for every node. ### Environment - APISIX version: 3.18.0 (`apache/apisix:3.18.0-debian`) - `lua-resty-redis-cluster`: 1.3.3 - Redis service and version: 7.1.0 - OS: ubuntu -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
