[jira] [Assigned] (KAFKA-18832) ShareFetch behaviour seems incorrect when MaxBytes is less than record size

["Andrew Schofield (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KAFKA-18832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Schofield reassigned KAFKA-18832:
----------------------------------------

        Fix Version/s: 4.1.0
    Affects Version/s: 4.1.0
             Assignee: Apoorv Mittal
          Description: 
Experimenting with the console-share-consumer, I set the fetch.max.bytes consumer property to a low value, 10000. Then I started producing records larger than this. No records were returned, essentially blocking delivery of the topic.

The limit should be interpreted as a soft limit, just as it is for regular consumers.
              Summary: ShareFetch behaviour seems incorrect when MaxBytes is less than record size  (was: ShareFetch behaviour seems incorrect when MaxBytes is less than record d)

> ShareFetch behaviour seems incorrect when MaxBytes is less than record size
> ---------------------------------------------------------------------------
>
>                 Key: KAFKA-18832
>                 URL: https://issues.apache.org/jira/browse/KAFKA-18832
>             Project: Kafka
>          Issue Type: Sub-task
>    Affects Versions: 4.1.0
>            Reporter: Andrew Schofield
>            Assignee: Apoorv Mittal
>            Priority: Major
>             Fix For: 4.1.0
>
>
> Experimenting with the console-share-consumer, I set the fetch.max.bytes consumer property to a low value, 10000. Then I started producing records larger than this. No records were returned, essentially blocking delivery of the topic.
> The limit should be interpreted as a soft limit, just as it is for regular consumers.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)