Help Center>
Distributed Message Service for Kafka>
FAQs>
Topics and Partitions>
Can I View the Disk Space Used by a Topic?
Updated on 2022-11-15 GMT+08:00
Can I View the Disk Space Used by a Topic?
Yes. Use either of the following methods to check the disk space used by a topic:
- Click next to the Kafka instance name to go to the Cloud Eye console. On the Queues tab page, set Queue to the name of the topic whose disk space you want to view and Scope to Basic monitoring. The Message Size metric reflects the message size of the selected topic.
- Click the desired Kafka instance to view its details. In the navigation pane, choose Monitoring. On the By Topic tab page, set Topic to the name of the topic whose disk space you want to view and Monitoring Type to Basic monitoring. The Message Size metric reflects the message size of the selected topic.
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 Change 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?
- Why Can't I See "Create Topic" and "Delete Topic" Buttons on the Topic Management Page?
- 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?
- How Do I Disable Automatic Topic Creation?
- 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.
The system is busy. Please try again later.
more