The current behavior when the possibility of data loss is encountered in replicated loglet is that the read stream will get stuck at the last possible read pointer and it will never return a data loss gap to the upper layers.
This issue tracks switching into active data loss boundary detection (when the loglet is sealed) to signal the data loss gap to bifrost and hand off the decision if data loss has been confirmed for a range of records.
The current behavior when the possibility of data loss is encountered in replicated loglet is that the read stream will get stuck at the last possible read pointer and it will never return a data loss gap to the upper layers.
This issue tracks switching into active data loss boundary detection (when the loglet is sealed) to signal the data loss gap to bifrost and hand off the decision if data loss has been confirmed for a range of records.