[
https://issues.apache.org/jira/browse/KUDU-1469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated KUDU-1469:
------------------------------
Resolution: Fixed
Fix Version/s: 1.0.0
Status: Resolved (was: In Review)
> Consensus can get "stuck" after a leader change when committed index is far
> behind replicated
> ---------------------------------------------------------------------------------------------
>
> Key: KUDU-1469
> URL: https://issues.apache.org/jira/browse/KUDU-1469
> Project: Kudu
> Issue Type: Bug
> Components: consensus
> Affects Versions: 0.8.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Critical
> Fix For: 1.0.0
>
>
> A YCSB stress test hit a bug whereby a tablet was "stuck" - operations were
> left in flight for hours/days and no progress could be made, despite a
> majority of replicas being alive.
> Detailed analysis below.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
