This repository was archived by the owner on Sep 26, 2026. It is now read-only.
Increase staging cache capacity and document hit renewal - #201
Merged
Merged
Conversation
import-pandas-as-numpy
deleted the
fix/staging-cache-renewal-capacity
branch
September 17, 2026 22:12
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.
1 participant
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.
Raise the staging durable cache limit from 500,000 to 1,000,000 entries per scanner. YARA has reached the current cap while avoiding roughly 27% of engine file inputs. Keep the 64 MiB per-scanner payload budget, 512 MiB physical storage admission threshold, and 24-hour TTL unchanged.
Document Mainframe's accompanying cache-hit expiry renewal: hourly write coalescing, bounded updates, invalid-entry exclusion, unchanged quota accounting, and renewal telemetry. No production configuration changes. Deploy the merged Mainframe renewal image with this staging ConfigMap and record rollout verification in the audit.
Validation: complete infrastructure hooks and pedantic zizmor pass. Rollback restores the previous Mainframe image and the 500,000-entry setting; existing rows are retained and new admissions stop until below the configured limit.