[
https://issues.apache.org/jira/browse/KUDU-1731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Grant Henke resolved KUDU-1731.
-------------------------------
Fix Version/s: NA
Resolution: Incomplete
> Evict replicas that are alive but lagging
> -----------------------------------------
>
> Key: KUDU-1731
> URL: https://issues.apache.org/jira/browse/KUDU-1731
> Project: Kudu
> Issue Type: Bug
> Components: consensus
> Reporter: Mike Percy
> Priority: Major
> Fix For: NA
>
>
> In the case that a replica is consistently behind the other replicas, we may
> be able to detect that the node is slow and evict it. (Currently under high
> write load we very often degrade to all tablets having just two live replicas
> and one COPYING)
> * In fact, this would also be useful for leaders that are significantly
> slower than their followers.
> * We should instead recruit a new replica and only evict the lagging one once
> the new one is online.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
