Page History

...

• 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. Also, if this topic WAS a compacted topic, and later updated as a non-compacted topic. In this case, enabling remote storage will not throw configuration exceptions. However, this is still not supported because we assume the topics are not compacted.
  

• 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 prior to 3.0 are limited in performing administrative actions, such as enabling Tiered Storage on a topic (ex: they might change directly in ZK using --zookeeper  option). 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.

• Log segments without producerSnapshot file: When there are log segments missing producer snapshot file while the transaction or idempotent producer is used, the remote log Manager will break a contract with the RSM API and would result in failure. Missing snapshot files can happen when topic is created before v2.8.0.
• Max one remote partition's worth of data fetched per Fetch Request: A Fetch Request can request data for multiple partitions, but when the data isn't present locally - only one partition (the first one we find whose local data isn't present) will have its data served from the remote store. The others will receive an empty response. This can limit client throughput - consider configuring max.partition.fetch.bytes  appropriately.

For the latest information regarding known issues, their resolutions, and possible workarounds, please visit the parent tracker for next release of Tiered Storage feature at