2 ms·
Or it could have just been a recordio file that was being written by something that crashed in the middle of doing it, and the committed offset was at a valid e
by jeffbee 4y ago
Or it could have just been a recordio file that was being written by something that crashed in the middle of doing it, and the committed offset was at a valid end of record.
Really there's 1000 ways for this to happen all of which are going to sound obvious in retrospect but are easy to commit.
- q3k 4y agoEven straight up Proto is vulnerable to this (either with an unlucky crash right between fields being actually written to a file, or when attempting to stream top-level fields).