server: replica.fetch.max.bytes should be >= message.max.bytes. Otherwise, the follower will get stuck when replicating data from the leader.
Thanks, Jun On Wed, Jul 31, 2013 at 10:10 AM, Sam Meder <sam.me...@jivesoftware.com>wrote: > I also noticed that there are two properties related to messages size on > the server: replica.fetch.max.bytes and message.max.bytes. What happens > when replica.fetch.max.bytes is lower than message.max.bytes? Should there > even be two properties? > > /Sam > > On Jul 31, 2013, at 5:25 PM, Sam Meder <sam.me...@jivesoftware.com> wrote: > > > We're expecting to occasionally have to deal with pretty large messages > being sent to Kafka. We will of course set the fetch size appropriately > high, but are concerned about the behavior when the message exceeds the > fetch size. As far as I can tell the current behavior when a message that > is too large is encountered is to pretend it is not there and not notify > the consumer in any way. IMO it would be better to throw an exception than > silently ignoring the issue (with the current code one can't really > distinguish a large message from no data at all). > > > > Thoughts? > > > > /Sam > >
