This is the KIP-74 write up if you want to learn more about the motivation and implementation of the fetch.max.bytes feature.
For example, the 5th message in your example can now be fetched even if it is larger than fetch.max.bytes which was a great improvement in large message handling. Previous the consumer could get stuck and not make progress. https://cwiki.apache.org/confluence/display/KAFKA/KIP-74%3A+Add+Fetch+Response+Size+Limit+in+Bytes -hans > On Feb 25, 2018, at 8:04 AM, adrien ruffie <adriennolar...@hotmail.fr> wrote: > > Hi Waleed, > > thank for you reply, that I thought too ! > but it was just to check if someone thought like me. > > Best regards, > Adrien > ________________________________ > De : Waleed Fateem <waleed.fat...@gmail.com> > Envoyé : dimanche 25 février 2018 16:36:28 > À : users@kafka.apache.org > Objet : Re: replica.fetch.max.bytes split message or not ? > > I would say you will get that 5th message in the next request. > > I don't believe under any circumstance a Kafka broker will send or receive > a partial message. > > On Feb 24, 2018 10:52 AM, "adrien ruffie" <adriennolar...@hotmail.fr> wrote: > >> Hello, >> >> >> I have found this description in only documentation (without taking into >> account spelling errors 'byes of messages'), a question stays in my mind ... >> >> what happens if the size does not fall correctly on a message number? >> >> Example if in one parition I have 10(messages) of 1024 bytes --> I have >> 10240 bytes. >> >> But If I set the replica.fetch.max.bytes option to 5000, >> >> the 5th message will be splitted of of 120 bytes, and send after ? Or just >> 4 messages will be sent and the 5th will be sent in the next fetch request ? >> >> >> Thank and best regards, >> >> Adrien >> >> replica.fetch.max.bytes 1024 * 1024 The number of byes of messages to >> attempt to fetch for each partition in the fetch requests the replicas send >> to the leader. >> >>
