Skip to content

feat: Ignore --query-modules-directory on coordinators #1636

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
as51340 wants to merge 1 commit into
base: release/3.11
Choose a base branch
from
+24 −2
Open

feat: Ignore --query-modules-directory on coordinators #1636

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion pages/clustering/high-availability/how-high-availability-works.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -123,7 +123,14 @@ well as `SET DATABASE SETTING` and `RELOAD SSL`.

Since coordinators do not store user data, the following restrictions apply:
- **Snapshots are automatically disabled** on coordinators, even if
`--storage-snapshot-interval-sec` is set.
`--storage-snapshot-interval-sec` is set. The `storage.snapshot.interval`
setting is not registered on coordinators, so attempting to read or modify it
via `SHOW DATABASE SETTING` / `SET DATABASE SETTING` returns an unknown
setting error.
- **The `--query-modules-directory` flag is ignored** on coordinators.
Coordinators do not execute data queries, so query modules are never loaded
and the embedded Python runtime is not initialized. The flag is still accepted
(so packaged defaults do not need to be overridden) but has no effect.
- **The `--init-file` and `--init-data-file` flags are not supported** on
coordinators (and likewise not supported on data instances in HA mode). The
instance will fail to start if either flag is provided.
Expand Down
2 changes: 1 addition & 1 deletion pages/database-management/configuration.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -451,7 +451,7 @@ execution in Memgraph.
| `--query-cost-planner=true` | Use the cost-estimating query planner. When enabled (`true`), Memgraph generates multiple query plans, selecting the one with the lowest cost. If disabled (`false`), it creates a single plan that is executed. | `[bool]` |
| `--query-execution-timeout-sec=600` | Maximum allowed query execution time. <br/>Queries exceeding this limit will be aborted. Value of 0 means no limit. | `[uint64]` |
| `--query-max-plans=1000` | Maximum number of generated plans for a query. | `[uint64]` |
| `--query-modules-directory=/usr/lib/memgraph/query_modules` | Directory where modules with custom query procedures are stored. NOTE: Multiple comma-separated directories can be defined. | `[string]` |
| `--query-modules-directory=/usr/lib/memgraph/query_modules` | Directory where modules with custom query procedures are stored. NOTE: Multiple comma-separated directories can be defined. The flag is ignored on coordinator instances in a [high availability](/clustering/high-availability) setup. | `[string]` |
| `--query-plan-cache-max-size=1000` | Maximum number of query plans to cache. | `[int32]` |
| `--query-vertex-count-to-expand-existing=10` | Maximum count of indexed vertices which provoke indexed lookup and then expand to existing, <br/>instead of a regular expand. Default is 10, to turn off use -1. | `[int64]` |
| `--query-log-directory=/var/log/memgraph/session_trace` | Location to store log files for session tracing. | `[string]` |
Expand Down
15 changes: 15 additions & 0 deletions pages/release-notes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,21 @@ guide.

### Memgraph v3.11.0 - June 17th, 2026

{<h4 className="custom-header">⚠️ Breaking changes</h4>}

- `--query-modules-directory` is now ignored on coordinator instances and
query modules are no longer loaded there. The embedded Python runtime is also
skipped on coordinators, so any Python-based modules that previously loaded
(but were unusable) will no longer be initialized. The flag itself is still
accepted so packaged defaults do not need to be overridden when starting a
coordinator. Additionally, `storage.snapshot.interval` is no longer registered
as a runtime setting on coordinators — `SHOW DATABASE SETTING
'storage.snapshot.interval'` and `SET DATABASE SETTING
'storage.snapshot.interval'` now return `Unknown setting name` instead of
`Coordinators don't support snapshots`. Update any tooling that pattern-matched
on the previous error message.
[#4066](https://github.com/memgraph/memgraph/pull/4066)

### Lab v3.11.0 - June 16th, 2026

<LabReleasesClient version="3.11.0" />
Expand Down