docs: file BUG report for staging VPC connector saturation - #430
Open
ran-taig wants to merge 1 commit into
Open
Conversation
Captures the RCA chain for the Path C entity-aware judge being silently bypassed: e2-micro VPC connector saturating under burst → ConnectTimeout cascade → asyncio.gather exhausts the 30s _CONTEXT_FETCH_TIMEOUT_SECONDS budget → fallback to base LLM judge. Storage-server-side latency is fine (15-141ms); the bottleneck is connection establishment through the shared connector. Grounded with timestamped log queries; includes two infra-side mitigations (machine-type upgrade or egress-mode change) and a verification plan. Signed-off-by: Ran Taig <ran@caura.ai>
Contributor
|
Claude Code Review — skipped: PR author 'ran-taig' is not a public member of the 'caura-ai' org |
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
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.
Summary
Files the RCA report for the staging VPC Serverless Connector saturation bug that silently disables Path C entity-aware contradiction detection on dev.
Grounded in timestamped Cloud Run + storage_client logs from the 2026-06-16 wet-test window:
POST /memories/entity-linkscalls from core-api all hitConnectTimeoutat TCP-handshake — they never reached the server.memclaw-staging-vpcconnector was e2-micro × min=2, shared by 10+ Cloud Run services withvpc-access-egress=all-traffic._CONTEXT_FETCH_TIMEOUT_SECONDS(CAURA-134) cannot be raised high enough to mask a connector that drops handshakes outright.Mitigation status (verified before PR)
Infra has applied Option A: connector machine type upgraded
e2-micro → e2-standard-4. Path C failure rate dropped from ~100% during bursts to ~10-15% (see PR description for daily trend). The 9-way fan-out shape from_fetch_entity_contextis still observable in logs and remains a separate architectural concern (tracked elsewhere).Test plan
alpine-theory-469016-c8🤖 Generated with Claude Code