The high-water mark is the greatest partition offset stored by every in-sync replica. Kafka exposes consumers only to records at or below this boundary, preventing recently read records from disappearing after a replica failure. section 2.9.1
Pending replication at offsets 8–10
If offsets 8–10 exist on the leader but have not reached every in-sync replica, offset 7 is the high-water mark. Consumers can read through 7; if the leader fails, the producer receives no acknowledgment for the unavailable records and retries them. section 2.9.1
Use the high-water mark alongside these related boundaries:
- In a nontransactional environment, the last stable offset equals the high-water mark, so consumers can poll through it. section 4.4.3
- With transactions, read_committed consumers stop at the last stable offset, which may be below the high-water mark while a transaction remains open. section 4.4.3
Figure 4.24 High water mark vs. last stable offset in a transactional environment
Compare the high-water mark with the last stable offset in a transactional environment. section 4.4.3

