Repository navigation
e103-grouping: cross-container grouping on 1.1.150 and on the E103 fix - #70
Merged
Merged
Conversation
Fluent Bit and the Receiver as the hot-tier rig starts them, without Elasticsearch, on ghcr.io/log-10x/edge-10x:1.1.150. A sender that interleaves containers on one Forward connection in five cases, and a scorer that fails on any cross-container record, missing or duplicated line. E103_CONFIG_DIR / E103_MODULES_DIR mount a candidate fix over the image's config and modules. Run on Docker pending. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Shipped 1.1.150: cases a, b and c return 512, 509 and 512 cross-container records; the one-container control (d) and one tag per container (e) return none; no line missing or duplicated. run.sh: readiness check no longer fails under pipefail, drain counts tokens in the parsed message, the guard allows census-ch. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Engine bc9ff152 with modules a35b44a9 (local/edge-10x:e103, TENX_JAVA_HEAP=320M): every case returns 0 cross-container records, 0 missing, 0 duplicated, every record under tenx.<sent tag>. No trace returned whole on 1.1.150 splits; three unpaused case a traces split within one container. run.sh takes E103_JAVA_HEAP; Fluent Bit keeps the returned tag (_fb_tag) and the scorer fails on a wrong one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Engine 0cd458f0 with modules 6c69d90a (local/edge-10x:e103 sha256:8f74b8bb, TENX_JAVA_HEAP=320M): 0 cross-container records, 0 missing, 0 duplicated, 0 wrong tags; all twelve split traces follow a 5 or 6 s pause. Replaces the run on bc9ff152 / a35b44a9. 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.
Adds
e103-grouping/, a minimal reproduction of engine ask E103. In the hot-tier run, multi-line grouping put lines from more than one container into one record. The rig runs it on 1.1.150 as shipped and on the fix.The rig is the hot-tier rig's Fluent Bit and Receiver path with Elasticsearch dropped. The Receiver gets the same arguments, environment and limits as in the two-arm runs. A sender interleaves containers on one Forward connection in five cases: a timestamped line from another container inside a stack trace, kafka's banner lines after a jaeger line, two stack traces at once, a one-container control, and the first three with one tag per container. The scorer matches every returned line to the line sent by its token. It fails on any cross-container record, missing line, duplicated line or record returned under the wrong tag.
The fix is engine commit 0cd458f0 with modules commit 6c69d90a, both on branch
fix/e103-sequence-key, run from a local image built on 1.1.150. No stack trace returned whole on 1.1.150 splits with the fix. All twelve traces that split with the fix were in episodes paused 5 or 6 s, and no returned record holds trace lines from more than one episode.run.shtakesE103_IMAGE,E103_CONFIG_DIR,E103_MODULES_DIRandE103_JAVA_HEAP, so a candidate fix runs on the same harness. The results for both runs are committed undere103-grouping/results/.🤖 Generated with Claude Code