Our Community is getting an upgrade! To get everything ready for the relaunch, we’ll be placing the site in read-only mode starting September 21st.
We really appreciate your understanding while we get things set up behind the scenes. Catch up on all the exciting details about the move here.
Need help or have questions? Drop us a line at [email protected]

Support Questions

Find answers, ask questions, and share your expertise
Announcements
Share your experience with Cloudera on G2 and get a $25 Amazon Gift card.
Hi, I'm CLEO! Something exciting is coming to the Community. Stay Tuned!

questions about kafka and compression.type

avatar
Rising Star

Hello,

is it possible to alter compression.type on a kafka topic while having applications on the topic running?

 

What should be expected hard drive saving factor for text records like json (2KB size) and compression.type=gzip.

 

In CM, I see a global setting.

Jarinek_0-1651842889847.png

 


Does it apply to KafkaMirrorMaker only?

 

Are producer and consumer applications somehow affected, when the global parameter changes.

Best regards
Jaro

1 ACCEPTED SOLUTION

avatar
Super Collaborator

 

@Jarinek 

 

Please check my inline answer to your queries: 

 

1) is it possible to alter compression.type on a kafka topic while having applications on the topic running?
>> Yes, we would recommend stopping the producer and then alert compression type as whenever the Kafka broker gets a compressed batch of messages from a producer. It will decompress the data to validate if the compression type is different at the topic level and producer level and if compression is the same from both sides, then it will write directly to the topic/leader partition. 

 

2) What should be expected hard drive saving factor for text records like json (2KB size) and compression.type=gzip.
>> You should use and test snappy or lz4 for best speed/compression ratio

 

3) Does it apply to KafkaMirrorMaker only?
>> Yes, as per the screenshot it will apply for the MM only.

 

4) Are producer and consumer applications somehow affected, when the global parameter changes.
>> If you are changing it from the Kafka side, then it should not affect the applications.

 

If you found this response assisted with your query, please take a moment to log in and click on  KUDOS 🙂 & ”Accept as Solution" below this post.

 

Thank you.

View solution in original post

1 REPLY 1

avatar
Super Collaborator

 

@Jarinek 

 

Please check my inline answer to your queries: 

 

1) is it possible to alter compression.type on a kafka topic while having applications on the topic running?
>> Yes, we would recommend stopping the producer and then alert compression type as whenever the Kafka broker gets a compressed batch of messages from a producer. It will decompress the data to validate if the compression type is different at the topic level and producer level and if compression is the same from both sides, then it will write directly to the topic/leader partition. 

 

2) What should be expected hard drive saving factor for text records like json (2KB size) and compression.type=gzip.
>> You should use and test snappy or lz4 for best speed/compression ratio

 

3) Does it apply to KafkaMirrorMaker only?
>> Yes, as per the screenshot it will apply for the MM only.

 

4) Are producer and consumer applications somehow affected, when the global parameter changes.
>> If you are changing it from the Kafka side, then it should not affect the applications.

 

If you found this response assisted with your query, please take a moment to log in and click on  KUDOS 🙂 & ”Accept as Solution" below this post.

 

Thank you.