You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This failure seems to be closely related to [1]. The NRTReplicationReaderManager kind of caches the current set of segment files in constructor but the final set of segment files may change on flush / commit.
This is happening after the test flushes the primary, the engine.lastCommittedSegmentInfos is not equal to the engine.latestSegmentInfos.
the engine.segments() method computes off of the lastCommittedSegmentInfos. I haven't yet been able to figure out what set of conditions under this seed cause this mismatch.
We can change the test to update the replica with engine.latestSegmentInfos, but then it still fails on comparing engine.segments() between both engines.
Ah ok, I think you are right @reta#3561 could fix this. A merge is kicking in on the primary causing the mismatch.
For the sake of this test we want to assert the replica has been updated with the provided segments, I don't think asserting engine.segments() is necessary if we have already asserted against the passed in segments, will update to fix this.
Describe the bug
Comes from #3568 (comment)
To Reproduce
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: