Help Center>
Distributed Message Service for Kafka>
FAQs>
Topics and Partitions>
What Should I Do If Kafka Storage Space Is Used Up Because Retrieved Messages Are Not Deleted?
Updated on 2022-11-15 GMT+08:00
What Should I Do If Kafka Storage Space Is Used Up Because Retrieved Messages Are Not Deleted?
Messages are not deleted immediately after being retrieved. They are deleted only when the aging time expires.
You can shorten the aging time or expand the storage space.
Parent topic: Topics and Partitions
Topics and Partitions FAQs
- Is There a Limit on the Number of Topics in a Kafka Instance?
- Why Is Partition Quantity Limited?
- Can I Reduce the Partition Quantity?
- Why Do I Fail to Create Topics?
- Do Kafka Instances Support Batch Importing Topics or Automatic Topic Creation?
- Why Do Deleted Topics Still Exist?
- Can I View the Disk Space Used by a Topic?
- Can I Add ACL Permissions for Topics?
- What Should I Do If Kafka Storage Space Is Used Up Because Retrieved Messages Are Not Deleted?
- How Do I Increase the Partition Quantity?
- Will a Kafka Instance Be Restarted After Its Automatic Topic Creation Setting Is Modified?
- Can I Delete Unnecessary Topics in a Consumer Group?
- What Can I Do If a Consumer Fails to Retrieve Messages from a Topic Due to Insufficient Permissions?
- Why Does an Instance Contain Default Topics __trace and __consumer_offsets?
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.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbotmore