Windows: qdrant did not load / read the configuration file
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 34.7k
- Forks
- 2.7k
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 187
Description
Current Behavior
When I start qdrant.exe the config file is not loaded and the settings are not applied
Steps to Reproduce
1.Download qdrant and unzip
2. Create new folder config
3. Create new file config.yaml and development.yaml
4. Start qdrant: start screen showing no error but for example the port chang is not applied
Sample config:
log_level: INFO
storage:
storage_path: "./storage"
snapshot_path: "./snapshots"
quantization:
scalar:
type: int8
quantile: 0.99
always_ram: true
performance:
max_search_threads: 8
server:
http_port: 6333
grpc_port: 6334
enable_tls: false
telemetry_disabled: false
service:
api_port: 6333
Expected Behavior
Settings from the config file should be applied to the server settings.
Possible Solution
- Ensure that Qdrant is correctly looking for the configuration file in the expected directory.
- Verify if Qdrant requires an explicit --config-path argument when starting the server.
- Check for permission issues that might prevent Qdrant from reading the config files.
- Confirm that the configuration file format follows the required syntax and structure.
Context (Environment)
This issue prevents me from customizing Qdrant settings, such as changing the default port, modifying storage settings, and configuring logging options. As a result, the server does not run with the expected configuration.
Possible Implementation
- Add a log message indicating whether a configuration file was successfully loaded or not.
- Implement a validation step that warns users if the config file is ignored or contains syntax errors.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with qdrant.exe on Windows using config/config.yaml and development.yaml, then compare behavior when supplying the suggested --config-path argument. Check whether the configured port, storage paths, and logging settings are applied; the issue is resolved when the server uses those values or clearly reports why the files are ignored.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, database, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100