All Products
Search
Document Center

Method for troubleshooting exceptions that occur when you access Message Queue for Apache Kafka for the first time

Last Updated: Sep 28, 2020

Overview

This article describes how to troubleshoot exceptions that occur when you access Message Queue for Apache Kafka for the first time.

Details

When you access Kafka for the first time, you can troubleshoot the error in the following three aspects:

  • Network connectivity problems: clients may fail to connect to the Kafka broker due to a network connection failure.
    • The ECS instance (client) and the Kafka instance are not in the same VPC. For more information about how to connect to log service through a VPC, see VPC.
    • When a local client accesses a Kafka instance of a non-public network.
    • The client ip address is not added to the whitelist. For more information about how to add a whitelist, see configure a whitelist.
  • Exceptions regarding the client version: if the client version is too old, an exception may occur. We recommend that you upgrade the client version as needed. For more information about the client Demo, see Demo library of message queue for Kafka.
    Description: Message Queue for Apache Kafka has restrictions on client versions. For example, if the server version is "0.10.2.2", the recommended client version is "0.10.2.2". The server version applies.
  • Configuration problems: the default access point is incorrectly configured, and the RAM user is not authorized. You can see quick start checks the configuration.

Application scope

  • Message Queue for Apache Kafka