|
| 1 | +storage: |
| 2 | + # Where to store all the data |
| 3 | + storage_path: ./storage |
| 4 | + |
| 5 | + # Where to store snapshots |
| 6 | + snapshots_path: ./storage/snapshots |
| 7 | + |
| 8 | + # If true - point's payload will not be stored in memory. |
| 9 | + # It will be read from the disk every time it is requested. |
| 10 | + # This setting saves RAM by (slightly) increasing the response time. |
| 11 | + # Note: those payload values that are involved in filtering and are indexed - remain in RAM. |
| 12 | + on_disk_payload: true |
| 13 | + |
| 14 | + # Write-ahead-log related configuration |
| 15 | + wal: |
| 16 | + # Size of a single WAL segment |
| 17 | + wal_capacity_mb: 32 |
| 18 | + |
| 19 | + # Number of WAL segments to create ahead of actual data requirement |
| 20 | + wal_segments_ahead: 0 |
| 21 | + |
| 22 | + # Normal node - receives all updates and answers all queries |
| 23 | + node_type: "Normal" |
| 24 | + |
| 25 | + # Listener node - receives all updates, but does not answer search/read queries |
| 26 | + # Useful for setting up a dedicated backup node |
| 27 | + # node_type: "Listener" |
| 28 | + |
| 29 | + performance: |
| 30 | + # Number of parallel threads used for search operations. If 0 - auto selection. |
| 31 | + max_search_threads: 0 |
| 32 | + # Max total number of threads, which can be used for running optimization processes across all collections. |
| 33 | + # Note: Each optimization thread will also use `max_indexing_threads` for index building. |
| 34 | + # So total number of threads used for optimization will be `max_optimization_threads * max_indexing_threads` |
| 35 | + max_optimization_threads: 1 |
| 36 | + |
| 37 | + optimizers: |
| 38 | + # The minimal fraction of deleted vectors in a segment, required to perform segment optimization |
| 39 | + deleted_threshold: 0.2 |
| 40 | + |
| 41 | + # The minimal number of vectors in a segment, required to perform segment optimization |
| 42 | + vacuum_min_vector_number: 1000 |
| 43 | + |
| 44 | + # Target amount of segments optimizer will try to keep. |
| 45 | + # Real amount of segments may vary depending on multiple parameters: |
| 46 | + # - Amount of stored points |
| 47 | + # - Current write RPS |
| 48 | + # |
| 49 | + # It is recommended to select default number of segments as a factor of the number of search threads, |
| 50 | + # so that each segment would be handled evenly by one of the threads. |
| 51 | + # If `default_segment_number = 0`, will be automatically selected by the number of available CPUs |
| 52 | + default_segment_number: 0 |
| 53 | + |
| 54 | + # Do not create segments larger this size (in KiloBytes). |
| 55 | + # Large segments might require disproportionately long indexation times, |
| 56 | + # therefore it makes sense to limit the size of segments. |
| 57 | + # |
| 58 | + # If indexation speed have more priority for your - make this parameter lower. |
| 59 | + # If search speed is more important - make this parameter higher. |
| 60 | + # Note: 1Kb = 1 vector of size 256 |
| 61 | + # If not set, will be automatically selected considering the number of available CPUs. |
| 62 | + max_segment_size_kb: null |
| 63 | + |
| 64 | + # Maximum size (in KiloBytes) of vectors to store in-memory per segment. |
| 65 | + # Segments larger than this threshold will be stored as read-only memmaped file. |
| 66 | + # To enable memmap storage, lower the threshold |
| 67 | + # Note: 1Kb = 1 vector of size 256 |
| 68 | + # If not set, mmap will not be used. |
| 69 | + memmap_threshold_kb: null |
| 70 | + |
| 71 | + # Maximum size (in KiloBytes) of vectors allowed for plain index. |
| 72 | + # Default value based on https://github.com/google-research/google-research/blob/master/scann/docs/algorithms.md |
| 73 | + # Note: 1Kb = 1 vector of size 256 |
| 74 | + indexing_threshold_kb: 20000 |
| 75 | + |
| 76 | + # Interval between forced flushes. |
| 77 | + flush_interval_sec: 5 |
| 78 | + |
| 79 | + # Max number of threads, which can be used for optimization per collection. |
| 80 | + # Note: Each optimization thread will also use `max_indexing_threads` for index building. |
| 81 | + # So total number of threads used for optimization will be `max_optimization_threads * max_indexing_threads` |
| 82 | + # If `max_optimization_threads = 0`, optimization will be disabled. |
| 83 | + max_optimization_threads: 1 |
| 84 | + |
| 85 | + # Default parameters of HNSW Index. Could be overridden for each collection individually |
| 86 | + hnsw_index: |
| 87 | + # Number of edges per node in the index graph. Larger the value - more accurate the search, more space required. |
| 88 | + m: 16 |
| 89 | + # Number of neighbours to consider during the index building. Larger the value - more accurate the search, more time required to build index. |
| 90 | + ef_construct: 100 |
| 91 | + # Minimal size (in KiloBytes) of vectors for additional payload-based indexing. |
| 92 | + # If payload chunk is smaller than `full_scan_threshold_kb` additional indexing won't be used - |
| 93 | + # in this case full-scan search should be preferred by query planner and additional indexing is not required. |
| 94 | + # Note: 1Kb = 1 vector of size 256 |
| 95 | + full_scan_threshold_kb: 10000 |
| 96 | + # Number of parallel threads used for background index building. If 0 - auto selection. |
| 97 | + max_indexing_threads: 0 |
| 98 | + # Store HNSW index on disk. If set to false, index will be stored in RAM. Default: false |
| 99 | + on_disk: false |
| 100 | + # Custom M param for hnsw graph built for payload index. If not set, default M will be used. |
| 101 | + payload_m: null |
| 102 | + |
| 103 | +service: |
| 104 | + |
| 105 | + # Maximum size of POST data in a single request in megabytes |
| 106 | + max_request_size_mb: 32 |
| 107 | + |
| 108 | + # Number of parallel workers used for serving the api. If 0 - equal to the number of available cores. |
| 109 | + # If missing - Same as storage.max_search_threads |
| 110 | + max_workers: 0 |
| 111 | + |
| 112 | + # Host to bind the service on |
| 113 | + host: 0.0.0.0 |
| 114 | + |
| 115 | + # HTTP port to bind the service on |
| 116 | + http_port: 6333 |
| 117 | + |
| 118 | + # gRPC port to bind the service on. |
| 119 | + # If `null` - gRPC is disabled. Default: null |
| 120 | + grpc_port: 6334 |
| 121 | + # Uncomment to enable gRPC: |
| 122 | + # grpc_port: 6334 |
| 123 | + |
| 124 | + # Enable CORS headers in REST API. |
| 125 | + # If enabled, browsers would be allowed to query REST endpoints regardless of query origin. |
| 126 | + # More info: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS |
| 127 | + # Default: true |
| 128 | + enable_cors: true |
| 129 | + |
| 130 | + {{- if eq (index . "TLS_ENABLED") "true" }} |
| 131 | + enable_tls: true |
| 132 | + {{- end }} |
| 133 | + |
| 134 | + {{- if index . "service_api_key" }} |
| 135 | + api_key: {{ .service_api_key | quote }} |
| 136 | + {{- end }} |
| 137 | + |
| 138 | +cluster: |
| 139 | + # Use `enabled: true` to run Qdrant in distributed deployment mode |
| 140 | + enabled: true |
| 141 | + |
| 142 | + # Configuration of the inter-cluster communication |
| 143 | + p2p: |
| 144 | + # Port for internal communication between peers |
| 145 | + port: 6335 |
| 146 | + {{- if eq (index . "TLS_ENABLED") "true" }} |
| 147 | + enable_tls: true |
| 148 | + {{- end }} |
| 149 | + |
| 150 | + # Configuration related to distributed consensus algorithm |
| 151 | + consensus: |
| 152 | + # How frequently peers should ping each other. |
| 153 | + # Setting this parameter to lower value will allow consensus |
| 154 | + # to detect disconnected nodes earlier, but too frequent |
| 155 | + # tick period may create significant network and CPU overhead. |
| 156 | + # We encourage you NOT to change this parameter unless you know what you are doing. |
| 157 | + tick_period_ms: 100 |
| 158 | + |
| 159 | +{{- if eq (index . "TLS_ENABLED") "true" }} |
| 160 | +tls: |
| 161 | + cert: {{ .TLS_MOUNT_PATH }}/tls.crt |
| 162 | + key: {{ .TLS_MOUNT_PATH }}/tls.key |
| 163 | + ca_cert: {{ .TLS_MOUNT_PATH }}/ca.crt |
| 164 | +{{- end }} |
| 165 | + |
| 166 | +# Set to true to prevent service from sending usage statistics to the developers. |
| 167 | +# Read more: https://qdrant.tech/documentation/telemetry |
| 168 | +{{- if hasKey . "telemetry_disabled" }} |
| 169 | +telemetry_disabled: {{ index . "telemetry_disabled" }} |
| 170 | +{{- else }} |
| 171 | +telemetry_disabled: true |
| 172 | +{{- end }} |
0 commit comments