You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kudu.apache.org by "Alexey Serbin (Jira)" <ji...@apache.org> on 2020/02/27 23:33:00 UTC

[jira] [Updated] (KUDU-2322) Leader spews logs when follower falls behind log GC

     [ https://issues.apache.org/jira/browse/KUDU-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Serbin updated KUDU-2322:
--------------------------------
    Fix Version/s:     (was: 1.7.0)
                   1.7.1

> Leader spews logs when follower falls behind log GC
> ---------------------------------------------------
>
>                 Key: KUDU-2322
>                 URL: https://issues.apache.org/jira/browse/KUDU-2322
>             Project: Kudu
>          Issue Type: Bug
>          Components: consensus
>    Affects Versions: 1.7.0
>            Reporter: Todd Lipcon
>            Assignee: Alexey Serbin
>            Priority: Critical
>             Fix For: 1.8.0, 1.7.1
>
>
> I'm running a YCSB-based write stress test and found that one of the followers fell behind enough that its logs got GCed by the leader. At this point, the leader started logging about 100 messages per second indicating that it could not obtain a request for this peer.
> I believe this is a regression since 1.6, since before 3-4-3 replication we would have evicted the replica as soon as it fell behind GC.



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