Consumption on Clients
- Method for troubleshooting exceptions that occur when you access Message Queue for Apache Kafka for the first time
- Message accumulation occurs when you use Message Queue for Apache Kafka
- Why does rebalancing frequently occur on the client?
- The consumer of Message Queue for Apache Kafka cannot pull messages from the server or the messages are pulled slowly
- Best practices for subscribers
- Client errors when you use Message Queue for Apache Kafka
- The error message "Not authorized to access group" is displayed when you use message queue for Apache Kafka
- The endpoint of the Message Queue for Apache Kafka instance cannot be pinged
- How do I access a Kafka instance from an ECS instance that is not in the same zone
- Can I access a Message Queue for Apache Kafka instance from the Internet?
- ow do I access a Message Queue for Apache Kafka instance through a proxy
- Do I have to select the 172.16.0.0/12 CIDR block for a classic network?
- Can we connect Message Queue for Apache Kafka instances in two different VPCs?
Sending on Clients
- How can I determine whether a message is sent after I send the message on the client?
- Does the callback setting on the Java client affect the message sending speed?
- How many connections to the broker can a producer establish?
- How can I test the message sending?
- Why is the sending delay of PHP long?
- Which open-source Apache Kafka versions are supported by Message Queue for Apache Kafka instances?
- How can I select the instance edition?
- How can I obtain the VPC information required for deploying an instance?
- What is impact of upgrading brokers?
- Why am I unable to change the region or network type of the instance?
- How can I quickly test whether the Message Queue for Apache Kafka broker is normal?
- Are delayed messages supported?
- Is data compression supported?
- When are old messages deleted in Message Queue for Apache Kafka?
- Why am I unable to reduce the number of partitions for a topic?
- When recreating a deleted Topic in a Message Queue for Apache Kafka instance, the system prompts that the number of partitions must be no less than the number of previously configured partitions
- Why does "Last Updated At" display 1970 for the partitions of a topic?
- What is the relationship between the topic count and partition count?
- Why is the total number of topics (partitions) limited?
- Is data compression supported?
- Why is automatic creation of topics not supported?
- What are the types of topic storage?
- Can I get one topic free for each purchased topic for instances of the Professional Edition?
Consumer Group FAQ
- The consumption time of partitions in Message Queue for Apache Kafka is different
- What does "Last Consumed At" mean in the console?
- Why does "Last Consumed At" display 1970 for the partitions of the topic that corresponds to a consumer group?
- How do I determine which IP addresses are consuming messages?
- Do the NFS cloud disks attached to consumers affect the message processing speed of consumers?
- What is the consumer group count?
- Why is automatic creation of consumer groups not supported?
- How can I manage the consumer offset in the console?
- You can still receive messages after you delete the Consumer Group
Monitoring and Alerts
- What are dead partitions and false accumulation?
- Why is the number of accumulated messages indicated by an alert different from that displayed in the console?
- Monitoring information is not displayed after a RAM user logs on to the console
- Why do I need to upgrade my instance to support monitoring and alerts?
- Why am I unable to log on to the instance with Message Queue for Apache Kafka deployed?
- "Insufficient data" is displayed in the alarm item column of the Message Queue for Apache Kafka console
- You can still receive alarm information about message accumulation after you delete the Consumer Group
- How do I monitor open-source Apache Kafka?