Versions Compared

Old Version 12

changes.mady.by.user Satish Duggana

Saved on

compared with

New Version 13

changes.mady.by.user Divij Vaidya

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Clusters with Multiple Log Directories: Tiered storage is not supported on clusters utilizing the multiple Log directories on a broker (JBOD feature). When attempting to enable remote storage on a broker with multiple Log directories (JBOD feature), you will receive a configuration exception.
  • Compacted Topics: Currently, tiered storage is not available for compacted topics. If you attempt to enable remote storage on a compacted topic, you will receive a configuration exception
  • Disabling Tiered Storage for a Topic: Once Tiered Storage is enabled for a topic, it becomes a permanent configuration and cannot be disabled. The only way to remove the tiered storage feature from a topic is by deleting the topic itself. It is essential to be aware that deleting the topic will result in the data being removed from remote storage. Therefore, exercise caution when enabling Tiered Storage for topics, as it becomes an irreversible operation. In future versions, KIP-950 will remove this limitation and add flexibility to disable / re-enable remote storage for a topic.
  • Disabling Tiered Storage at the Cluster Level: Disabling Tiered Storage for the entire cluster requires manual deletion of all topics using Tiered Storage. Attempting to disable tiered storage at the cluster level without deleting the topics using tiered storage will result in an exception."Delete Records" API for Topics with Remote Storage Enabled: The "delete records" API cannot be used for topics with remote storage enabled. When remote storage is activated for a topic, using the "delete records" API to delete specific records from that topic is not supported. Alternative strategies, such as logical deletion or data retention policies, should be considered for data management in topics with remote storage enabled

  • Client Compatibility: All Kafka clients, regardless of their version, can continue to produce and consume records from topics utilizing Tiered Storage. However, clients with versions earlier than 3.0 are limited in performing administrative actions, such as enabling Tiered Storage on a topic. To successfully enable Tiered Storage for a topic, clients must be running Kafka version 3.0 or later, as administrative actions related to Tiered Storage are only supported on clients from version 3.0 onwards.