Ok so it might be an issue somewhere in the pipeline (I'm guessing memory
issues?).
They are xml files, and that 30-100 was uncompressed.
On Tue, Jan 29, 2013 at 12:28 PM, Neha Narkhede wrote:
> > At linkedin, what is the largest payload size per message you guys have
> in
> > production?
> >
>
Ack, right you are Neha, my bad.
WRT to how to set the maximum there are two considerations:
1. It should be smaller then the fetch size your consumers use
2. Messages are fully instantiated in memory so obscenely large messages
(say hundreds of mb) will cause a lot of memory allocation churn/prob
> At linkedin, what is the largest payload size per message you guys have in
> production?
>
Roughly 30K after compression, but that is fairly rare. Most messages are <
500 bytes after compression.
Thanks,
Neha
Not quite in production yet, but we have payloads in the 30KB+ range. I
just added a
max.message.size to the broker's server.properties.
-Xavier
On 1/29/13 8:57 AM, S Ahmed wrote:
Neha/Jay,
At linkedin, what is the largest payload size per message you guys have in
production? My app might ha
Neha/Jay,
At linkedin, what is the largest payload size per message you guys have in
production? My app might have like 20-100 kilobytes in size and I am
hoping to get an idea if others have large messages like this for any
production use case.
On Tue, Jan 29, 2013 at 11:35 AM, Neha Narkhede wr
> In 0.7.x this
> setting is controlled by the broker configuration max.message.size.
>
Actually, in 0.7.x this setting is controlled by max.message.size on the
producer. In 0.8, we moved this setting to the broker.
Thanks,
Neha
There is a setting that controls the maximum message size. This is to
ensure the messages can be read on the server and by all consumers without
running out of memory or exceeding the consumer fetch size. In 0.7.x this
setting is controlled by the broker configuration max.message.size.
-Jay
On T
