kamalcph opened a new pull request, #20201:
URL: https://github.com/apache/kafka/pull/20201

   Improve the error handling while building the remote-log-auxiliary state 
when a follower node with an empty disk begin to synchronise with the leader. 
If the topic has remote storage enabled, then the ReplicaFetcherThread attempt 
to build the remote-log-auxiliary state. Note that the remote-log-auxiliary 
state gets invoked only when the leader-log-start-offset is non-zero and 
leader-log-start-offset is not equal to leader-local-log-start-offset.
   
   When the LeaderAndISR request is received, then the 
ReplicaManager#becomeLeaderOrFollower invokes 'makeFollowers' initially, 
followed by the RemoteLogManager#onLeadershipChange call. As a result, when 
ReplicaFetcherThread initiates the 
RemoteLogManager#fetchRemoteLogSegmentMetadata, the partition may not have been 
initialized at that time.
   
   Introducing a new RetriableRemoteStorageException requires a KIP as it is a 
public API change, so wrapping the IllegalStateException in 
RemoteStorageException to gracefully handle the error.
   
   Delete this text and replace it with a detailed description of your change. 
The 
   PR title and body will become the squashed commit message.
   
   If you would like to tag individuals, add some commentary, upload images, or
   include other supplemental information that should not be part of the 
eventual
   commit message, please use a separate comment.
   
   If applicable, please include a summary of the testing strategy (including 
   rationale) for the proposed change. Unit and/or integration tests are 
expected
   for any behavior change and system tests should be considered for larger
   changes.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: jira-unsubscr...@kafka.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to