You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

This is an early access release for tiered storage feature(KIP-405), and it is not recommended for use in production environments. Instead, we advise users to create clusters with version 3.6.0 and test the feature there. Alternatively, you can try the tiered storage feature on existing non-production clusters running version 2.8.0 or later, upgraded to version 3.6.0.

The criteria for this release are as follows:

  • The tiered storage feature should not cause any regressions on other supported features, even when it is disabled.

In this early access release, the following features related to tiered storage are supported:

  • Setting tiered storage for a specific topic.
  • Deletion of topics that are using tiered storage.
  • Consuming records from remote storage.
  • Only topics on existing clusters with version 2.8.0 or later are supported for tiered storage.
  • A default implementation of a local file-based RemoteStorageManager, known as 'LocalTieredStorage,' is provided.
  • Several metrics have been added to monitor tiered storage operations.

Main limitations 

  • Tiered storage is not supported on clusters with multiple Log directories on a broker (a.k.a JBOD feature).
  • Tiered storage is not supported for compacted topics.
  • Disabling tiered storage on a topic in a graceful manner is supported.


If you encounter any issues or want to disable tiered storage at the cluster level, you can follow these steps:

  • Disable tiered storage for all existing topics that were previously enabled with this feature.
  • After that, set the cluster or broker level configuration 'remote.log.storage.system.enable' to 'false' to disable tiered storage for the entire cluster.





  • No labels