osiris_writer: Track diff between writer and replica offsets#197
Open
the-mikedavis wants to merge 1 commit intorabbitmq:mainfrom
Open
osiris_writer: Track diff between writer and replica offsets#197the-mikedavis wants to merge 1 commit intorabbitmq:mainfrom
the-mikedavis wants to merge 1 commit intorabbitmq:mainfrom
Conversation
the-mikedavis
force-pushed
the
replication-diff-metric
branch
from
8272b66 to
0fa0df1
Compare
Collaborator
Author
|
In addition to this (or maybe instead of this) we could track replica freshness. The stream coordinator is calculates "freshness" as a requirement in |
This introduces a metric calculated at every batch which records the difference between the timestamps of the last chunks in the logs of the writer and its replicas. This can be used to watch replicas catch up on replication, or to diagnose situations when replication is being starved out (network-wise) by high-throughput publishing. The replication diff should usually be low but, for streams seeing traffic, non-zero. This calculation is also used in the stream coordinator when adding a member, via `osiris_writer:query_replication_state/1`. With this change the stream coordinator could be updated to use the counter instead of calling the writer.
the-mikedavis
force-pushed
the
replication-diff-metric
branch
from
0fa0df1 to
680b7a9
Compare
Collaborator
Author
|
I updated this to perform the same calculation as the stream coordinator does: https://github.com/rabbitmq/rabbitmq-server/blob/765d2c5d748f1a3227b97e966a31a73f4b561867/deps/rabbit/src/rabbit_stream_coordinator.erl#L209-L221 (Also see discussion in rabbitmq/rabbitmq-server#15098) So we could use this metric instead of querying the replication state with a call. |
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
1 participant
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.
This introduces a metric calculated at every batch which records the difference between the timestamps of the last chunks in the logs of the writer and its replicas. This can be used to watch replicas catch up on replication, or to diagnose situations when replication is being starved out (network-wise) by high-throughput publishing. The replication diff should usually be low but, for streams seeing traffic, non-zero.
This calculation is also used in the stream coordinator when adding a member, via
osiris_writer:query_replication_state/1. With this change the stream coordinator could be updated to use the counter instead of calling the writer.