[
https://issues.apache.org/jira/browse/KUDU-2322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16394025#comment-16394025
]
Alexey Serbin edited comment on KUDU-2322 at 3/13/18 3:29 PM:
--------------------------------------------------------------
I posted a patch to throttle log messages. I think it will take longer to
adjust the 3-4-3 scheme to evict failed-behind-log-GC followers, and I'm not
quite sure yet whether such a shortcut would be advantageous.
was (Author: aserbin):
I posted a patch to throttle log messages. I think it will take longer to
adjust the 3-4-3 scheme to evict failed-behind-log-GC followers, and I'm not
quite sure yet whether such a shortcut is advantageous.
> 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
>
> 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
(v7.6.3#76005)
