This document lists the limits of certain metrics and performance in CKafka. Be careful not to exceed the limits during use to avoid exceptions.
Item | Description |
---|---|
Number of topics | The topic limit depends on product specifications. For details, see Billing Overview. |
Number of partitions |
|
Partition throughput |
|
Duration |
Featuring high-traffic and high-throughput message queues, Kafka cannot guarantee that each request has low latency. The recommended timeout period settings are as follows:
|
Number of consumer groups |
|
Instance |
|
Version |
|
Routes | An instance can create up to five routes, with only one of them being a public network route. |
Public network bandwidth | CKafka provides a public network bandwidth of 3 Mbps for free by default. Pro Edition instances can upgrade public network bandwidth to 198 Mbps additionally. |
Exposing ZooKeeper | It is not supported. |
Exposing underlying resources | It is not supported so as to avoid risks caused by user's operation. |
Message size | It cannot exceed 12 MB; otherwise, messages will fail to be sent. |
Tag | Each Tencent Cloud resource can have up to 50 tags. |
Concurrent operations in the console | Some management and control operations may cause the instance metadata to be modified, leading to data inconsistency when the concurrency is high, and underlying data distribution will be affected. Therefore, some API operations will be locked to limit the request concurrency. To improve the stability and success rate of console operations, up to 20 concurrent console requests (including those directly initiated via SDK) can be initiated for a single instance. |
NoteDue to CKafka's partition architecture, business data size, request frequency, and the stability of the physical layer, CKafka cannot guarantee that each request has low latency.
- We will try our best to guarantee that:
- The percentage of an instance’s monthly low production duration is the same as the instance’s stability SLA.
- The percentage of an instance’s monthly low consumption duration is the same as the instance’s stability SLA.
- The calculation formula is as follows:
The percentage of low production duration in a month = (the number of minutes when the production duration 99.9th percentile per minute is less than or equal to 30s that month / the monthly service duration in minutes) * 100%
The percentage of low consumption duration in a month = (the number of minutes when the consumption duration 99.9th percentile per minute is less than or equal to 60s that month / the monthly service duration in minutes) * 100%
Was this page helpful?