langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-20 19:50:06 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

ulimits .env variables for qdrant #22250

New Issue
Open
opened 2026-02-21 20:16:18 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 20:16:18 -05:00
Owner
Copy Link
Copy Source

Originally created by @sergeydi on GitHub (Feb 18, 2026).

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 have a problem with qdrant ulimits. In some case I have an error:
...mod.rs at line 246: Failed to load local shard.. Too many open files

Only ulimits section in docker-compose.yaml help solve the problem:

# Qdrant vector store.
# (if used, you need to set VECTOR_STORE to qdrant in the api & worker service.)
  qdrant:
    image: langgenius/qdrant:v1.7.3
    ulimits:
      nofile:
        soft: 524288
        hard: 524288

Could you please add this two options to .env file Variables.

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 @sergeydi on GitHub (Feb 18, 2026). ### 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. I have a problem with qdrant ulimits. In some case I have an error: `...mod.rs at line 246: Failed to load local shard.. Too many open files` Only **ulimits** section in `docker-compose.yaml` help solve the problem: ``` # Qdrant vector store. # (if used, you need to set VECTOR_STORE to qdrant in the api & worker service.) qdrant: image: langgenius/qdrant:v1.7.3 ulimits: nofile: soft: 524288 hard: 524288 ``` Could you please add this two options to .env file Variables. ### 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 20:16:18 -05:00
yindo commented 2026-02-21 20:16:19 -05:00
Author
Owner
Copy Link
Copy Source

@darshjme-codes commented on GitHub (Feb 20, 2026):

The Qdrant container crashes with “Too many open files” unless the ulimits are hard‑coded in docker‑compose.yml. Users want to set those limits through .env so they can adjust them without editing the compose file.

.env

QDRANT_ULIMIT_SOFT=524288
QDRANT_ULIMIT_HARD=524288

docker‑compose.yml (excerpt)

  qdrant:
    image: langgenius/qdrant:v1.7.3
    ulimits:
      nofile:
        soft: ${QDRANT_ULIMIT_SOFT}
        hard: ${QDRANT_ULIMIT_HARD}

Add the two variables to the repo’s .env template and reference them in the ulimits section. This lets anyone change the file‑descriptor limits via .env alone.

(Will close #xxxx once merged.)

@darshjme-codes commented on GitHub (Feb 20, 2026): The Qdrant container crashes with “Too many open files” unless the ulimits are hard‑coded in `docker‑compose.yml`. Users want to set those limits through `.env` so they can adjust them without editing the compose file. **.env** ``` QDRANT_ULIMIT_SOFT=524288 QDRANT_ULIMIT_HARD=524288 ``` **docker‑compose.yml (excerpt)** ```yaml qdrant: image: langgenius/qdrant:v1.7.3 ulimits: nofile: soft: ${QDRANT_ULIMIT_SOFT} hard: ${QDRANT_ULIMIT_HARD} ``` Add the two variables to the repo’s `.env` template and reference them in the `ulimits` section. This lets anyone change the file‑descriptor limits via `.env` alone. (Will close #xxxx once merged.)
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#22250
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?