-
Notifications
You must be signed in to change notification settings - Fork 586
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
[v23.1.x] Add cloud_storage statistics to usage reporting #9670
[v23.1.x] Add cloud_storage statistics to usage reporting #9670
Conversation
Looks like there is a dependency on this PR #9121 |
0cb338e
to
34ccf64
Compare
(cherry picked from commit 6d2b262)
(cherry picked from commit ff3145a)
- New method for manually invoking a refresh of the cloud stats. Will only work if invoked on controller leader. (cherry picked from commit 1e4ad97)
(cherry picked from commit c5236a5)
(cherry picked from commit 6647fae)
- close window currently contains an async job that in all cases will run in a very short amount of time. - the concern is adding more asynchronous work before in the close_window method could hold up the opening of the subsequent window. - Solution is to make close_window synchronous, but start a background fiber that runs the asynchronous work and later places the results at the correct historical bucket. (cherry picked from commit cebeeb9)
- Fixes: redpanda-data#9527 (cherry picked from commit 1171554)
- All requests made to the usage endpoint in the usage_test will check response entries are correctly ordered (cherry picked from commit 892e1b2)
- Extend the duration of the test to cover scenarios where the max number of windows is reached and the oldest historical windows are overwritten. - Fixes: redpanda-data#9524 (cherry picked from commit a47866c)
34ccf64
to
b911af0
Compare
For reviewers, the PR initially failed to compile. This is because in the first commit of this PR i removed a static member var called To prevent having to depend on #9121 , i've manually edited the first commit in this PR to re-include the |
Apparently this also depends on #9204 |
b911af0
to
4af2b9b
Compare
- In scenarios where options are triggered on and off quickly it is possible that inconsistent data may appear on disk. - There is a race between shutting down of a usage_manager::accounting_fiber and the start of a new one. - Fixes: redpanda-data#9652
/ci-repeat 2 |
/ci-repeat 2 |
/ci-repeat 2 |
/ci-repeat 2 |
/ci-repeat 2 |
/ci-repeat 2 |
- Test asserts that 0 bytes are accounted for within metering after starting up a new node, but that is not necessiarily true. A small amount of non-client traffic may be observed, and the disk persistance interval has been set to 1s so post-restart it is expected that some data may have been accounted for. - Fixes: redpanda-data#9568
/ci-repeat 2 |
Leaving a helpful note to explain what occured in the manual rebase here:
|
Cover Letter
Backport of PR: #9574
Release Notes
Improvements