[ 
https://issues.apache.org/jira/browse/KAFKA-16060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17801126#comment-17801126
 ] 

Divij Vaidya commented on KAFKA-16060:
--------------------------------------

Hey [~jianbin] 

Questions are best asked by sending an email to developer mailing list or user 
mailing list specified at [https://kafka.apache.org/contact] 
I will answer your questions as a one time exception here but in future, please 
send an email.

1. It's only the leader that copies data to remote storage. Any replica will 
not delete logs locally even if local expiration time is reaches until it knows 
that leader has copied the specifed log to remote, i.e. data from local storage 
is never removed until there is a copy available in remote. You can find more 
information about this at 
[https://cwiki.apache.org/confluence/display/KAFKA/KIP-405%3A+Kafka+Tiered+Storage]
 

2. Yes, compression sounds like a typo. Where did you find it? As a reference, 
the early access notes for Tiered Storage at 
[https://cwiki.apache.org/confluence/display/KAFKA/Kafka+Tiered+Storage+Early+Access+Release+Notes]
 mention it more clearly.

> Some questions about tiered storage capabilities
> ------------------------------------------------
>
>                 Key: KAFKA-16060
>                 URL: https://issues.apache.org/jira/browse/KAFKA-16060
>             Project: Kafka
>          Issue Type: Wish
>          Components: core
>    Affects Versions: 3.6.1
>            Reporter: Jianbin Chen
>            Priority: Major
>
> # If a topic has 3 replicas, when the local expiration time is reached, will 
> all 3 replicas trigger the log transfer to the remote storage, or will only 
> the leader in the isr transfer the log to the remote storage (hdfs, s3)
>  # Topics that do not support compression, do you mean topics that 
> log.cleanup.policy=compact?



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to