Hi all, I have completed the code optimization and all tests.
Compared with the previous KIP, I made one small change and would like to inform everyone: For the delay-related config, the default value is changed from 0 to -2. This is to clearly distinguish: no check/-2 (time check and size check: if one is -2, the other one is used to check as result) vs immediate upload/0 (any config is 0. upload at once without check any other). Any feedback you can help to give comment on the PR( https://github.com/apache/kafka/pull/20913) or reply mail. Thank you all. Regards Jian jian fu <[email protected]> 于2026年3月19日周四 06:49写道: > Hi Chia-Ping: > > Thanks for review and vote!The discussion improved the KIP. > > Hi All: > > Thank you all for taking the time to review and for offering many valuable > suggestions and insightful questions. > > KIP-1241 is accepted. > > +3 (binding): Kamal, Chia-Ping, Luke Chen > > I will focus on the test and target 4.4.0. > > Thanks, > Jian > > Chia-Ping Tsai <[email protected]> 于2026年3月18日周三 19:28写道: > >> +1 (binding) >> >> On 2026/01/12 13:12:13 jian fu wrote: >> > Hi all: >> > >> > I would like to start a vote for the KIP: >> > >> > The KIP: https://cwiki.apache.org/confluence/x/A4LMFw >> > The Draft PR: https://github.com/apache/kafka/pull/20913 >> > >> > Summary: >> > >> > Currently, Kafka's tiered storage implementation uploads all non-active >> > local log segments to remote storage immediately, even when they are >> still >> > within the local retention period. >> > This results in redundant storage of the same data in both local and >> remote >> > which don't have real value in some cases. >> > This KIP's goal is to reduce the remote storage as an optional topic >> > feature which can be implemented with few code lines. >> > >> > Thanks. >> > Jian >> > >> >
