liveBook · Manning

High-water mark

A high-water mark is a maximum observed value or configured threshold that bounds, tracks, or controls progress, storage, or processing.

How 3 Manning books explain it

JavaScript in Depth

A stream buffering threshold that controls how much data may be queued before backpressure is applied.

How it is used
Controls when stream producers should slow down as internal queues fill.
How deep it goes
Explains buffer thresholds, producer signals, pipeline accumulation, and runtime-specific enforcement, stopping short of implementation internals.
Examples
Uses Node.js push(), write(), drain, Transform pipelines, desiredSize, pull(), and externally fed Web Streams.
What you can do after
Diagnose/debug with it by locating accumulating buffers and respecting push(), write(), drain, desiredSize, and pull() signals.

Read how JavaScript in Depth explains high-water mark →

Apache Kafka in Action

A high water mark is the highest offset in a Kafka partition whose record is available for consumption because the required replicas have received it.

How it is used
Uses replica progress to determine which Kafka records are committed and available to consumers.
How deep it goes
Explains HWM calculation through LEO and ISR fetches, then traces lag effects without detailing broker persistence internals.
Examples
Illustrates leader and follower offsets, a lagging ISR, HWM advancement, and blocked consumption when the minimum ISR is unavailable.
What you can do after
Diagnose/debug with it by relating consumer stalls and delayed visibility to ISR lag and minimum-replica settings.

Read how Apache Kafka in Action explains high-water mark →

Kafka Streams in Action, Second Edition

A high-water mark is the greatest partition offset replicated to all in-sync replicas and made accessible to consumers.

How it is used
Limits consumer visibility to records replicated across all in-sync replicas.
How deep it goes
Defines the replication boundary, works through offsets 8–10, and contrasts it with the transactional last stable offset.
Examples
Uses offsets 8–10 awaiting replication and contrasts nontransactional polling with read_committed polling.
What you can do after
Configure consumers with read_committed while distinguishing replication durability from transactional visibility.

Read how Kafka Streams in Action, Second Edition explains high-water mark →

Also covered in

What to know first

Related concepts

Questions about high-water mark

What is high-water mark?

A high-water mark is a maximum observed value or configured threshold that bounds, tracks, or controls progress, storage, or processing.

Which Manning books explain high-water mark?

JavaScript in Depth, Apache Kafka in Action and Kafka Streams in Action, Second Edition.

What should I know before learning high-water mark?

Manning books that teach high-water mark usually introduce offset first.

What is high-water mark a kind of?

High-water mark is a kind of offset. An offset is a position or displacement measured relative to a reference point, such as within an ordered sequence, memory region, or layout.

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.