Add committed offset in stream stats#15225
Merged
acogoluegnes merged 2 commits intomainfrom Jan 27, 2026
Merged
Conversation
acogoluegnes
added a commit
to rabbitmq/rabbitmq-stream-java-client
that referenced
this pull request
Jan 8, 2026
acogoluegnes
force-pushed
the
stream-committed-offset
branch
2 times, most recently
from
0c6e8be to
4328a92
Compare
acogoluegnes
force-pushed
the
stream-committed-offset
branch
2 times, most recently
from
94cdf44 to
89fcfd2
Compare
ansd
reviewed
Jan 20, 2026
acogoluegnes
force-pushed
the
stream-committed-offset
branch
3 times, most recently
from
4eba54b to
f296d19
Compare
The committed offset (offset of the last entry in the stream) is now available in Osiris. It is used instead of the "committed chunk ID" where appropriate: to calculate the offset lag and the number of available messages. It is more accurate to use the committed offset for the offset lag than to use the committed chunk ID. Before: offset lag = committed chunk ID - ID of the last dispatched chunk Now: offset lag = committed offset - offset of the last message in the last dispatched chunk This change uses the rabbitmq_4.3.0 feature flag to enable the calculation of the committed offset in Osiris only when all the nodes have been migrated. The streams need to be restarted as the feature is enabled when starting the writer and the replicas. References rabbitmq/osiris#203
When not all counters are wanted, instead of osiris_counters:overview/1, which loads all the counters.
acogoluegnes
force-pushed
the
stream-committed-offset
branch
from
f296d19 to
6ed5d5a
Compare
acogoluegnes
added a commit
to rabbitmq/rabbitmq-stream-java-client
that referenced
this pull request
Jan 27, 2026
This was referenced Feb 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The committed offset (offset of the last entry in the stream) is now
available in Osiris. It is used instead of the "committed chunk ID"
where appropriate: to calculate the offset lag and the number of
available messages.
It is more accurate to use the committed offset for the offset lag than
to use the committed chunk ID.
Before: offset lag = committed chunk ID - ID of the last dispatched
chunk
Now: offset lag = committed offset - offset of the last message in the
last dispatched chunk
This change uses the rabbitmq_4.3.0 feature flag to
enable the calculation of the committed offset in Osiris only when all
the nodes have been migrated. The streams need to be restarted as the
feature is enabled when starting the writer and the replicas.
This PR bumps Osiris to v1.11.0.
References rabbitmq/osiris#203