Cool - thanks for clarifying this!
On Thu, Mar 23, 2017 at 10:54 AM, Ismael Juma <ism...@juma.me.uk> wrote: > Hi Kostas, > > Yes, equal is fine. The code that prints an error if replication fails due > to this: > > error(s"Replication is failing due to a message that is greater than > replica.fetch.max.bytes for partition $topicPartition. " + > "This generally occurs when the max.message.bytes has been > overridden to exceed this value and a suitably large " + > "message has also been sent. To fix this problem increase > replica.fetch.max.bytes in your broker config to be " + > "equal or larger than your settings for max.message.bytes, both at > a broker and topic level.") > > Ismael > > On Thu, Mar 23, 2017 at 2:37 PM, Kostas Christidis <kos...@gmail.com> wrote: > >> On Thu, Mar 23, 2017 at 5:04 AM, Ben Stopford <b...@confluent.io> wrote: >> > Hi Kostas - The docs for replica.fetch.max.bytes should be helpful here: >> > >> > The number of bytes of messages to attempt to fetch for each partition. >> > This is not an absolute maximum, if the first message in the first >> > non-empty partition of the fetch is larger than this value, the message >> > will still be returned to ensure that progress can be made. >> >> Hi Ben >> >> When I'm reading this bit (which I have done before), I am left with >> the impression that replica.fetch.max.bytes can in fact be equal to >> message.max.bytes. Am I wrong? This interpretation goes against points >> 3 and 4 in the original email. >> >> Kostas >>
