Hi Krishnan,
In 0.10.2, there was some consolidation of the message format code and the
recompression code path is not as well optimised in the consolidated code
(recompression is supposed to be rare now). Not sure if this explains the
huge difference you are seeing though.
Changing log.message.f
Hi Ismael,
Thanks for the info. If 0.8.2.1 was also uncompressing and recompressing
data, do you have any insight as to what would cause higher memory usage on
0.10?
On 0.8, we are able to run our brokers with 1GB heap and they work
perfectly fine. On 0.10 we are seeing OutOfMemory errors even wi
Hi Krishnan,
0.8.2.1 brokers also uncompress and recompress data. The ability to avoid
recompression was introduced in 0.10.0.0
with a new message format (see KIP-31 and KIP-32). If you change
log.message.format.version
to 0.10.2, the broker will not uncompress and recompress messages produced
by
