langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-08-26 18:36:52 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Add load balancing env variable for external databases. #16690

New Issue
Closed
opened 2026-02-21 19:27:11 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 19:27:11 -05:00
Owner
Copy Link
Copy Source

Originally created by @NotAnAddictz on GitHub (Sep 3, 2025).

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.

Am currently running Dify through a helm chart in a kubernetes cluster. I want to use an elastic-search cluster as my Vector Database. However, I only see the option for a single endpoint via ELASTICSEARCH_HOST. Does Dify offer internal client-side load balancing? ie: variable accepts a list of endpoints, rather than a single variable

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @NotAnAddictz on GitHub (Sep 3, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [x] I confirm that I am using English to submit this report, otherwise it will be closed. - [x] 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. Am currently running Dify through a helm chart in a kubernetes cluster. I want to use an elastic-search cluster as my Vector Database. However, I only see the option for a single endpoint via ELASTICSEARCH_HOST. Does Dify offer internal client-side load balancing? ie: variable accepts a list of endpoints, rather than a single variable ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 💪 enhancement label 2026-02-21 19:27:11 -05:00
yindo closed this issue 2026-02-21 19:27:11 -05:00
yindo commented 2026-02-21 19:27:12 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Sep 3, 2025):

If you are interested, you can submit a PR for this feature.

@crazywoola commented on GitHub (Sep 3, 2025): If you are interested, you can submit a PR for this feature.
yindo commented 2026-02-21 19:27:12 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 4, 2025):

Hi, @NotAnAddictz. I'm Dosu, and I'm helping the Dify team manage their backlog and am marking this issue as stale.

Issue Summary:

  • You requested support for an environment variable to enable client-side load balancing with multiple Elasticsearch endpoints.
  • This is to accommodate running Dify on Kubernetes with an Elasticsearch cluster.
  • Currently, Dify only supports a single ELASTICSEARCH_HOST, which limits your setup.
  • A maintainer encouraged you to submit a pull request to add this feature.
  • No further updates or contributions have been made on this issue.

Next Steps:

  • Please let me know if this feature is still relevant to your use case with the latest version of Dify by commenting here.
  • Otherwise, this issue will be automatically closed in 15 days.

Thanks for your understanding and contribution!

@dosubot[bot] commented on GitHub (Oct 4, 2025): Hi, @NotAnAddictz. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary:** - You requested support for an environment variable to enable client-side load balancing with multiple Elasticsearch endpoints. - This is to accommodate running Dify on Kubernetes with an Elasticsearch cluster. - Currently, Dify only supports a single ELASTICSEARCH_HOST, which limits your setup. - A maintainer encouraged you to submit a pull request to add this feature. - No further updates or contributions have been made on this issue. **Next Steps:** - Please let me know if this feature is still relevant to your use case with the latest version of Dify by commenting here. - Otherwise, this issue will be automatically closed in 15 days. Thanks for your understanding and contribution!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 💪 enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#16690
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?