Repository navigation
elastic-hot-tier-budget: E103 fix on the two-arm smoke, arm A, 0 cross-container records - #72
Merged
Merged
Conversation
phases-two-arm.sh takes ARM_A_ONLY=1 (no cluster B, no copy to it), render-fb-two-arm.py then keeps every returned record whole, and gen-receiver-values.mjs passes TENX_JAVA_HEAP for an engine image that runs on a JVM. score-e103.py matches each returned record's lines to the lines sent and counts records holding more than one container. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s-container records Engine 0cd458f0f with modules 6c69d90a (local/edge-10x:e103, TENX_JAVA_HEAP=320M), the 2026-10-24 smoke's schedule and feed, arm A alone: 79,415 records, none holding lines from more than one container; all 101,637 non-blank lines fed are in exactly one record; Elasticsearch holds 79,416 documents summing to 101,637 lines. score-e103.py counts by lines; its self-test checks both groupings on the run's feed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
This PR reruns the elastic-hot-tier-budget two-arm smoke for arm A alone on the E103 fix, on the rig where 71 of 848,190 returned records held lines from more than one container. The fix is engine commit 0cd458f0f with modules commit 6c69d90a, both on branch
fix/e103-sequence-key. They ran in a local image built on 1.1.150, withTENX_JAVA_HEAP=320M. The schedule, feed, log10x-mcp version, ILM policies and policy branch are the 2026-10-24 smoke's.The count matches each returned record's lines to the lines sent (
rig/score-e103.py). The earlier count treated each record as the run of seqs up to the next record's seq, which holds only for grouping in arrival order. The scorer's self-test groups the run's feed with one head rule both ways. In arrival order it finds 4,333 cross-container records, as many as the run-based count. Per container it finds none.Rig changes:
ARM_A_ONLY=1inphases-two-arm.shruns arm A without cluster B and keeps every returned record whole.gen-receiver-values.mjspassesTENX_JAVA_HEAP.🤖 Generated with Claude Code