Repository navigation
Reject process-local graph backends in multi-process deployments - #1810
Open
mikemikimike wants to merge 1 commit into
Open
mikemikimike wants to merge 1 commit into
mikemikimike wants to merge 1 commit into
Conversation
Signed-off-by: mikemikimike <[email protected]>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose of the change
Prevent deployments with multiple server processes from silently using graph
backends whose schema, index or semantic-set caches are local to one process.
Issue: #1753
Description
and NebulaGraph declarative graph stores.
sessions. Enforce the same limit in resource factories and resolved session
overrides, including AUTO semantic storage's Neo4j fallback.
HTTP processes selected by MEMMACHINE_WORKERS require at least HOST scope;
deployments on multiple hosts declare CLUSTER.
Document the configuration and the affected backends' limits.
Fixes/Closes
Fixes #1753
Type of change
How Has This Been Tested?
2406 passed, 4 skipped. Three existing invalid-credential tests time out
contacting the OpenAI API; all three fail identically on unchanged main.
all 92 passed. The POSIX-specific time-zone regression and the 11 local
resource-manager tests also passed; the same three external API tests
failed with connection errors.
Python 3.10/3.14 successfully.
start/stop with external resources replaced by test doubles: unchanged main
accepts each affected backend in CLUSTER scope; this change refuses all
three before creating background tasks and preserves PROCESS startup.
Project test commands:
Checklist
disabled components, repeated calls and failure recovery.