...

Currently, data is stored in both tiers for the first 24 hoursday, resulting in about 16 hours of redundant storage (ignore the active segement gap). This can lead leads to cost increases.

So we can reduce the tiered storage redundancy for cost saving. In this case, it will save about 25% cost pay for total size 's costof disk.

Currently, data is stored in both tiers for the first 24 hours, resulting in 24 hours of 
redundant storage. With typical data volumes, this can lead to significant cost increases.

However, some users/topics rely on remote storage for real-time analytics and need the 
the latest data to be available as soon as possible (In fact, it only tries to stay as up-to-date as possible, but it still can’t include the latest data because the active segment hasn’t been uploaded yet.). Therefore, this optimization should be 
is offered as an **a topic's optional configuration**  rather than the default behavior.

Public Interfaces

This KIP introduces one new broker configuration property:  remote.log.metadata.topic.min.isr

...