To provide more stable and easier-to-use messaging services, Tencent Cloud CKafka will retire the Elastic Topic feature. This feature entered the end-of-public-beta phase in April 2025 and has stopped accepting new creations Elastic Topic Feature Plan Termination Public Beta Announcement. It will be officially retired on December 31, 2026(UTC+8). After retirement, existing Elastic Topics will no longer be available. Please complete your migration before the retirement date to avoid business impact.
Retirement schedule
|
April 2025 | New creation stopped | Elastic Topic has stopped accepting new creations. Existing Elastic Topics can continue to be used before retirement. |
December 31, 2026(UTC+8) | Official retirement | Elastic Topic will stop providing services. Please complete migration before this date. |
Impact scope
This retirement affects the creation, configuration, and use of Elastic Topics in the CKafka console.
If you are still using Elastic Topics, please migrate to standard CKafka Topics or CKafka Serverless instances as soon as possible.
Migration recommendations
Migrate to standard CKafka Topics: Suitable for workloads with relatively stable traffic or clear capacity planning. You can create standard Topics in an existing or new CKafka instance. For short-term traffic bursts, you can use the elastic bandwidth capability of CKafka Pro Edition.
Migrate to CKafka Serverless: Suitable for workloads with fluctuating traffic or scenarios where you want to reduce capacity planning and O&M costs.
Recommended actions
1. Check the producers, consumers, and dependencies of your existing Elastic Topics.
2. Select a migration target based on traffic, retention period, and partition configuration.
3. Create standard CKafka Topics or CKafka Serverless instances.
4. Update producer and consumer connection configurations and verify your business.
5. Stop using the original Elastic Topics after migration.