You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Xue Liu (Jira)" <ji...@apache.org> on 2019/11/18 22:51:00 UTC

[jira] [Comment Edited] (KAFKA-9207) Replica Out of Sync as creating ReplicaFetcher thread failed with connection to leader

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

Xue Liu edited comment on KAFKA-9207 at 11/18/19 10:50 PM:
-----------------------------------------------------------

We have some further discovery:

When creating that thread, the follower had connection error to the leader. See attachment error-connection.jpg

 

 


was (Author: xuel1):
We have some further discovery:

 

When creating that thread, the follower had connection error to the leader. See attachment error-connection.jpg

 

 

> Replica Out of Sync as creating ReplicaFetcher thread failed with connection to leader
> --------------------------------------------------------------------------------------
>
>                 Key: KAFKA-9207
>                 URL: https://issues.apache.org/jira/browse/KAFKA-9207
>             Project: Kafka
>          Issue Type: Bug
>          Components: replication
>    Affects Versions: 2.3.0
>            Reporter: Xue Liu
>            Priority: Major
>         Attachments: Capture.PNG, error-connection.jpg
>
>
> We sometimes see a replica for a partition is out of sync. When the issue happens, it seems that we just lost that replica (would never catch-up), unless we restart that broker.
> It appears that ReplicaFetcher thread for that partition is dead and broker will not restart that thread. We didn't see any exception in server or controller logs.
> The screen capture is taken from the broker that has that replica. Leader is 2017.
>  
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)