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
The invocation of the new segmentClosed callback introduced in #5388 occurs
asynchronously with respect to the manager and the progression through logical
log numbers. This test was flaky in two ways: If the segmentClosed callback was
invoked /before/ the writerClosed callback for the same WAL, writerClosed would
append a second record for the same logical log containing the set of WALs
other than the one inserted by the segmentClosed callback. Conversely, if the
segmentClosed callback was sufficiently delayed relative to the closing of the
writer, it might not be invoked until after the test listed the set of obsolete
logs.
The first race is fixed by a refactoring of the segmentClosed and writerClosed
callbacks, adapting them to share the same logic for merging logs. The second
race is fixed through use of (datadriven.TestData).Retry to account for the
nondeterminism.
Fix#5401.
0 commit comments