-
Notifications
You must be signed in to change notification settings - Fork 614
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
pandaproxy: add max memory check for incoming requests #24537
pandaproxy: add max memory check for incoming requests #24537
Conversation
/dt |
non flaky failures in https://buildkite.com/redpanda/redpanda/builds/59616#0193b7b4-8c87-4047-b52a-c85d1f6a6b2f:
|
Retry command for Build#59616please wait until all jobs are finished before running the slash command
|
c0293e3
to
a8b2628
Compare
Retry command for Build#59721please wait until all jobs are finished before running the slash command
|
CI test resultstest results on build#59721
test results on build#59729
test results on build#59811
test results on build#59848
|
a8b2628
to
83e1b8d
Compare
changes in force-push:
|
Retry command for Build#59729please wait until all jobs are finished before running the slash command
|
83e1b8d
to
55c3907
Compare
Changes in force-push:
|
55c3907
to
1c5c454
Compare
Changes in force-push:
|
Hi guys. I asked other doc writers to take a look. While we're here, I see the labels are defined as "shards". How does that work? It's because they have Feel free to DM me if you want to talk about it. |
It's a number representing the logical core that the Redpanda reactor is running on. When Redpanda is given 4 CPU Cores there will be 4 reactors, one on each of the CPU cores, e.g.: |
I'll add these metrics to our docs for 24.3 and backport to 24.2: https://redpandadata.atlassian.net/browse/DOC-869 I assume they will go out in the next patch release for each. |
1c5c454
to
0919453
Compare
Changes in force-push:
|
Retry command for Build#59811please wait until all jobs are finished before running the slash command
|
0919453
to
067fc7b
Compare
changes in force-push:
|
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.
Please fix the cover letter to reflect the latest changes.
Retry command for Build#59848please wait until all jobs are finished before running the slash command
|
CI Failures: |
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.
One question about aggregation of metrics
/backport v24.3.x |
/backport v24.2.x |
/backport v24.1.x |
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.
👍
fixes: CORE-8335
In the pandaproxy server, if a request comes in that is larger than the total available memory, every other request is blocked. A test is added to make sure that a request bigger than the available memory returns an error.
For better monitoring, the following metrics have been added,
prefixed with
[vectorized|redpanda]_[rest_proxy|schema_registry]_
:inflight_requests_usage_ratio
shard
inflight_requests_memory_usage_ratio
shard
queued_requests_memory_blocked
shard
Backports Required
Release Notes
Improvements