Kafka Best Practices
This section summarizes best practices of Distributed Message Service (DMS) for Kafka in common scenarios. Each practice is given a description and procedure.
Best Practice |
Description |
---|---|
This document provides producers and consumers with message suggestions, improving the efficiency and reliability of message sending and consumption. |
|
This document describes how to optimize consumer polling in scenarios where real-time message consumption is not required, saving resources when there are few or no messages. |
|
Interconnecting Logstash to Kafka to Produce and Consume Messages |
Kafka instances are available as the input and output sources of Logstash. This document describes how to connect Logstash to Kafka instances for message production and consumption. |
MirrorMaker can mirror data from a source cluster to a target cluster. This document describes how to use MirrorMaker to synchronize data between two Kafka instances unidirectionally or bidirectionally. |
|
This document describes the causes of message stacking and the handling measures. |
|
This document describes the causes of high CPU usage and full disk space and the handling measures. |
|
This document describes the causes of unbalanced service data and the handling measures. |
|
This document describes how to generate an alarm when the number of stacked messages exceeds a specified threshold. In this way, you can be aware of the service running status in time by SMS or email. |
|
This document describes security best practices of using Kafka. It aims to provide a standard guide for overall security capabilities. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot