A read-only client: it reads one group's queue and publishes nothing, so it opens no cluster session, takes no part in an election and needs no topology row. Audit, risk or a downstream feed. It replays local history through the co-located Replayer, switches to the live queue once caught up, and delivers every application message once, in clusterSeqNo order, as a Payload — the same view the producers' façades give.
More...
A read-only client: it reads one group's queue and publishes nothing, so it opens no cluster session, takes no part in an election and needs no topology row. Audit, risk or a downstream feed. It replays local history through the co-located Replayer, switches to the live queue once caught up, and delivers every application message once, in clusterSeqNo order, as a Payload — the same view the producers' façades give.
Fenced, like them, when it can no longer be trusted to see the queue: ClusterError.RecoveryStalled and ClusterError.QueueStalled. It takes no snapshots and so always restarts from the start of its queue, which a cluster with a <snapshots> policy no longer holds; a consumer there is an Application or Gateway with a snapshot listener that writes no records.
Single-threaded: every member belongs to the caller's one duty-cycle thread, which calls DoWork each iteration. Consumer.java and app/Consumer.hpp are its twins; keep the three in step. ReplayerStreamReceiver is the lower-level path this sits on.