Skip to content
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.

Sign up for GitHub

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

Jump to bottom

kafka: noisy "Fetch requested very large response" messages #3964

Closed
jcsp opened this issue Mar 9, 2022 · 0 comments · Fixed by #3965
Closed

kafka: noisy "Fetch requested very large response" messages #3964

jcsp opened this issue Mar 9, 2022 · 0 comments · Fixed by #3965
Labels
area/kafka kind/tech-debt

Comments

@jcsp
Copy link
Contributor

jcsp commented Mar 9, 2022

This message was introduced to flag up clients behaving badly by asking for more data than the server could reasonably deliver.

However, this turns out to be more common in the field than expected, probably as a result of franz-go's default per-partition fetch size being 10MB (i.e. if you try and consume from a 7-partition topic, you exceed the default 64MB request limit).
jcsp added a commit to jcsp/redpanda that referenced this issue Mar 9, 2022
@jcsp
kafka: reduce oversized fetch log from info to debug
cee055e 
This turns out to be fairly common in the field: clients
are routinely setting their per-partition fetch limit
to something much higher than they really expect to read.

Fixes redpanda-data#3964
@jcsp jcsp mentioned this issue Mar 9, 2022
Merged
@jcsp jcsp closed this as completed in #3965 Mar 9, 2022
jcsp added a commit to jcsp/redpanda that referenced this issue Mar 9, 2022
@jcsp
kafka: reduce oversized fetch log from info to debug
968d0fe 
This turns out to be fairly common in the field: clients
are routinely setting their per-partition fetch limit
to something much higher than they really expect to read.

Fixes redpanda-data#3964

(cherry picked from commit cee055e)
@jcsp jcsp mentioned this issue Mar 9, 2022
Merged
dotnwat added a commit that referenced this issue Mar 9, 2022
@dotnwat
Merge pull request #3970 from jcsp/issue-3964-backport
cda79dc 
v21.11.x/backport: #3964 (kafka: reduce oversized fetch log from info to debug)
ajfabbri pushed a commit to ajfabbri/redpanda that referenced this issue Mar 16, 2022
@jcsp
kafka: reduce oversized fetch log from info to debug
2f005b0 
This turns out to be fairly common in the field: clients
are routinely setting their per-partition fetch limit
to something much higher than they really expect to read.

Fixes redpanda-data#3964
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/kafka kind/tech-debt
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

kafka: reduce oversized fetch log from info to debug jcsp/redpanda
1 participant
@jcsp