During segment container ownership transfer readers get NoSuchSegment
See original GitHub issueProblem description
Readers were reading from a segment on a particular segment container. Then segmentContainer failover happened and post ownership transfer readers failed with NoSuchSegment.
This lead to readers rereading data from offset 0 in the segment 0#epoch.10
again.
It repeated 3 times before they were successfully able to read it.
segmentstore_2018-06-08.1.log:2018-06-08 14:24:26,941 103854 [core-10] WARN i.p.s.s.h.h.PravegaRequestProcessor - Segment 'testReadTxnWriteAutoScaleScope2092305162/testReadTxnWriteAutoScaleStream/0#epoch.10' does not exist and cannot perform operation 'Read segment'.
segmentstore_2018-06-08.1.log:2018-06-08 14:24:27,974 104887 [core-24] WARN i.p.s.s.h.h.PravegaRequestProcessor - Segment 'testReadTxnWriteAutoScaleScope2092305162/testReadTxnWriteAutoScaleStream/0#epoch.10' does not exist and cannot perform operation 'Read segment'.
segmentstore_2018-06-08.1.log:2018-06-08 14:24:29,016 105929 [core-28] WARN i.p.s.s.h.h.PravegaRequestProcessor - Segment 'testReadTxnWriteAutoScaleScope2092305162/testReadTxnWriteAutoScaleStream/0#epoch.10' does not exist and cannot perform operation 'Read segment'.
Problem location SegmentStore
Suggestions for an improvement Fix the issue
Issue Analytics
- State:
- Created 5 years ago
- Comments:12 (12 by maintainers)
Top Results From Across the Web
About segments and containers | Adobe Analytics
When building audience segments in the Segment Builder, you define conditions using the AND and OR operators between containers.
Read more >Container Basics - Salesforce Help
Containers provide a way to create relationships between your Related Attributes. Attributes within a container act on the same data row in the...
Read more >Segment containers in Adobe Analytics - YouTube
How to work with the three different segment container types in Adobe Analytics.For more information on this feature, ...
Read more >Adobe Analytics Segments: Which Container Should I Use?
There are 3 types of segment containers: Hit, Visit, and Visitors. ... When users browse your site, Adobe receives data in that same...
Read more >Transfer ownership of an OCP 4 cluster
Is there an expiry date for the cancellation of the cluster ownership transfer? Environment. Red Hat OpenShift Container Platform (RHOCP). 4.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
There are 5 readers in the test and each reader stops reading if it encounters a TruncationException. The below log snippets explain why duplicate events were read (4 instances of the same event were found)
==> First test reader got SegmentTruncationException from SSS after reading upto offset
59220+1170
=60390
==> The second reader acquired this segment and successfully read upto offset
60390
before throwing an exception.===> The third reader acquired this segment and successfully read upto offset
60390
before throwing an exception:===> The fourth reader successfully read this segment until it received a Segment sealed.
Thanks for all the help in debugging this. After further digging in the logs (which are really, really stuffy), I realized that this was indeed the test failure cause. The test itself could be improved to make it more clear what failed (and when), but that is an issue for another time (#2688).
I have a PR out that hopefully fixes this corner case bug. This needs fixing, despite the fact that we had a good number of master build test successes recently.