-
Notifications
You must be signed in to change notification settings - Fork 486
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
pageserver: add page_trace
API for debugging
#10293
Conversation
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.
LGTM.
7315 tests run: 6939 passed, 0 failed, 376 skipped (full report)Flaky tests (3)Postgres 17
Postgres 16
Code coverage* (full report)
* collected from Rust tests only The comment gets automatically updated with the latest test results
6a3dd3a at 2025-01-15T17:05:26.344Z :recycle: |
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.
Neat!
I think this is safe to deploy, barring the check_permission
problem.
Nits can be addressed in a follow-up.
@problame I cleaned this up a bit, should be ready for final review. |
6a4115a
to
c6e89d0
Compare
@jcsp I can't request a review from you (since you're the author), but if you could give this an LGTM I can merge based on my approval. |
Problem
When a pageserver is receiving high rates of requests, we don't have a good way to efficiently discover what the client's access pattern is.
Closes: #10275
Summary of changes
/v1/tenant/x/timeline/y/page_trace?size_limit_bytes=...&time_limit_secs=...
API, which returns a binary buffer.pagectl page-trace
tool to decode and analyze the output.