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

Arpit Goyal edited comment on KAFKA-16088 at 1/28/24 9:51 AM:
--------------------------------------------------------------

[~satish.duggana] [~divijvaidya] [~ckamal] I am going to start working on it. 
As per my code understanding next fetch offset will be incremented only when 
there is some set of records in the response. 

In the case mentioned above, I was thinking  to introduce the delayedFetch for 
next higher offset within the DelayedRemoteFetch instead of calling the 
callback when number of records is empty. Let me know if there are other 
possible option to handle the above scenario. 




was (Author: JIRAUSER301926):
[~satish.duggana] [~divijvaidya] [~ckamal] I am going to start working on it. 
As per my code understanding next offset will be incremented only when there is 
some set of records in the response. 

In the case mentioned above, I was thinking  to introduce the delayedFetch for 
next higher offset within the DelayedRemoteFetch instead of calling the 
callback when number of records is empty. Let me know if there are other 
possible option to handle the above scenario. 



>  Not reading active segments  when RemoteFetch return Empty Records.
> --------------------------------------------------------------------
>
>                 Key: KAFKA-16088
>                 URL: https://issues.apache.org/jira/browse/KAFKA-16088
>             Project: Kafka
>          Issue Type: Bug
>          Components: Tiered-Storage
>            Reporter: Arpit Goyal
>            Assignee: Arpit Goyal
>            Priority: Critical
>              Labels: tiered-storage
>
> This issue is about covering local log segments also while finding the 
> segment for a specific offset when the topic is compacted earlier but it is 
> changed to retention and enabled with tiered storage.
> Please refer to this comment for details 
> https://github.com/apache/kafka/pull/15060#pullrequestreview-1802495064



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

Reply via email to