Description
KIP-405 [1] introduces the Tiered Storage feature in Apache Kafka. One of the limitations mentioned in the KIP is inability to re-enable TS on a topic after it has been disabled.
Once tier storage is enabled for a topic, it can not be disabled. We will add this feature in future versions. One possible workaround is to create a new topic and copy the data from the desired offset and delete the old topic.
This task will propose a new KIP which extends on KIP-405 to describe the behaviour on on disablement and re-enablement of tiering storage for a topic. The solution will apply for both Zk and KRaft variants.
[1] KIP-405 - https://cwiki.apache.org/confluence/display/KAFKA/KIP-405%3A+Kafka+Tiered+Storage
Attachments
Issue Links
- is a child of
-
KAFKA-16947 Kafka Tiered Storage V2
-
- Open
-
- requires
-
KAFKA-7739 Kafka Tiered Storage
-
- Resolved
-
1.
|
KRaft - Add v2 of TopicRecord |
|
Resolved | Luke Chen |
2.
|
Add remote.log.disable.policy |
|
Resolved | Christo Lolov |
3.
|
Add *.thread.pool.size |
|
Resolved | Muralidhar Basani |
4.
|
Split RemoteLogManagerScheduledThreadPool |
|
Resolved | Abhijeet Kumar |
5.
|
KRaft - Wire replaying a TopicRecord |
|
Resolved | Luke Chen |
6.
|
bump metadata version for topic Record |
|
Resolved | Muralidhar Basani |
7.
|
Zookeeper - Add v5 of StopReplica |
|
Resolved | Christo Lolov |
8.
|
Zookeeper - Add new exception |
|
Resolved | Muralidhar Basani |
9.
|
Zookeeper - Add new ZNodes |
|
Resolved | Unassigned |
10.
|
Make configurations public |
|
Resolved | Unassigned |
11.
|
Allow topic config validation in controller level in KRaft mode |
|
Resolved | Luke Chen |
12.
|
local log should be deleted when remote copy disabled and no remote logs |
|
Resolved | Luke Chen |
13.
|
revert topicRecord changes |
|
Resolved | TengYao Chi |
14.
|
documentation for disablement feature |
|
Resolved | Luke Chen |