Enable Kafka tiered storage for a topic and verify remote segment offload using the built-in RemoteLogMetadataManager

Steps

1. Set remote.log.storage.system.enable=true in broker server.properties and configure remote.log.metadata.manager.listener.name to the listener clients should use for RLMM internal topic access
2. Set remote.log.metadata.manager.class.name=org.apache.kafka.server.log.remote.storage.RemoteLogMetadataManager (the default Kafka built-in implementation) and provide the plugin jar path via remote.log.metadata.manager.class.path if using a custom storage backend
3. At the topic level set remote.storage.enable=true and local.retention.ms (or local.retention.bytes) to a value smaller than the topic's retention.ms so older segments are eligible for offload
4. Restart brokers and create or alter the target topic: kafka-topics.sh --alter --topic my-topic --config remote.storage.enable=true --config local.retention.ms=3600000
5. Verify offload: check broker logs for RemoteLogManager activity and query the internal __remote_log_metadata topic to confirm segment metadata entries exist
6. Test fetch from remote tier: consume an offset older than local.retention.ms and confirm data is retrieved from remote storage without errors