-
Notifications
You must be signed in to change notification settings - Fork 592
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
archival: consistent log size probes across replicas (pull) #24342
archival: consistent log size probes across replicas (pull) #24342
Conversation
We called update probe only from leaders and after exiting the upload loop which led to inconsistent and stale metrics. Fix this by introducing a subscription mechanism to the STM which is the source of truth for the manifest state and must be consistent across all replicas. The first attempt was in redpanda-data#24257 but the feedback suggested that the approach in this commit is better.
ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/58887#01936eb1-72e3-4d67-a8ad-ae9f474b632b |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the lifetimes look ok to me. do you see any issues @Lazin ?
/backport v24.3.x |
/backport v24.2.x |
Failed to create a backport PR to v24.2.x branch. I tried:
|
/cdt |
/cdt |
We called update probe only from leaders and after exiting the upload loop which led to inconsistent and stale metrics.
Fix this by introducing a subscription mechanism to the STM which is the source of truth for the manifest state and must be consistent across all replicas.
The first attempt was in
#24257 but the feedback suggested that the approach in this commit is better.
Backports Required
Release Notes
Bug Fixes
redpanda_cloud_storage_cloud_log_size
metric consistent across all replicas. We used to update it seldomly from the leader replica only which lead to inconsistent/stale values.