This repository was archived by the owner on Nov 8, 2026. It is now read-only.
Repository navigation
Separate role configuration and simplify process memory protection - #112
Merged
Merged
Conversation
This was referenced Sep 19, 2026
Merged
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Separate reusable Store connection/Kafka policy from Gateway, Engine and Worker files through
--store-config. Gateway owns public validation, caller contexts control request lifetime, Worker owns consumption, and MongoDB concurrency belongs to the shared Store. Kafka policy applies to source and DLQ with minimum ISR 1; batching defaults to 32 operations and 2 ms. Replace allocation accounting and snapshot/output quotas with process memory watermarks (80% reject/pause, 70% resume). Admitted batches finish together; startup panics with a sizing breakdown if estimated minimum working memory cannot fit below the high watermark. Remove obsolete admission/reservation metrics and update alerts, KEDA queries, examples and migration documentation. Watermarks reduce overload but do not guarantee against OOM.Validated with unit/race/coverage gates, lint, component regressions, real MongoDB/Elasticsearch/OpenSearch integration, public conformance plus a separate startup-panic subprocess run (48 top-level tests), Chart rendering/config checks, and a four-case fixed-resource container smoke. Live Engine/Gateway metrics expose the seven replacement memory families without the retired families. Qualification: batchstream/sink-production-suite#28; Chart: batchstream/sink-charts#12; SDK: batchstream/sink-go#24. Private forwarding is version 6 and requires matching Gateway/Engine builds; this is a breaking configuration migration.