the plugin_daemon does't support redis cluster?

[ROBODRILL]

Self Checks

• I have read the Contributing Guide and Language Policy.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report, otherwise it will be closed.
• Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing? Tell me about your story.

I want to use the redis cluster,the config is :
#REDIS_HOST=
#REDIS_PORT=
#REDIS_USERNAME=
#REDIS_PASWORD=
...
REDIS_USE_CLUSTERS=true
REDIS_CLUSTERS=ip1:port1,ip2:port2,ip3:port3,ip4:port4,ip5:port5,ip6:port6
REDIS_CLUSTERS_PASSWORD=password
;
starting the docker dify ,the error is :
plugin_daemon_1 |panic: [PANIC] init redis client failed: dial tcp: lookup redis: i/o timeout;

this is the dify_plugin_daemon source code:

whether the dify_plugin_daemon can not use redis cluster?

2. Additional context or comments

No response

3. Can you help us with this feature?

• I am interested in contributing to this feature.

[dosubot]

Dify does support Redis Cluster mode for internal caching if you set REDIS_USE_CLUSTERS=true and provide your cluster node addresses in REDIS_CLUSTERS—the system will initialize a RedisCluster client and connect as expected. However, Redis Cluster is not supported as the Celery broker; only standard Redis and Redis Sentinel are supported for that purpose. Your error (dial tcp: lookup redis: i/o timeout) is likely a network or DNS issue, not a lack of Redis Cluster support in the core platform. For more details, see the official discussion and configuration guidance and Celery broker limitations.

If you’re using Redis Cluster for internal caching, double-check your Docker network and DNS settings. If you’re trying to use it as a Celery broker, switch to Redis Sentinel or standalone Redis for that component.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}    

[ROBODRILL]

the way I check Docker network and DNS settings is wrong? please tell me the right way to check these two points

[taowujie]

Dify-api supports Redis Cluster mode for internal caching when the REDIS_USE_CLUSTERS=true setting is configured. However, Redis Cluster does not work with TLS and Redis Cluster username. For example, when using AWS ElastiCache Redis OSS with clustering enabled, it fails to run properly.
Additionally, I noticed that dify-plugin-daemon does not support Redis Cluster, as its configuration file does not read the REDIS_USE_CLUSTERS=true parameter. You can check the relevant code here: https://github.com/langgenius/dify-plugin-daemon/blob/main/internal/types/app/config.go