Bug 1859201

Summary: etcd: Fix deadlock bug in mvcc
Product: OpenShift Container Platform Reporter: Sam Batschelet <sbatsche>
Component: EtcdAssignee: Sam Batschelet <sbatsche>
Status: CLOSED ERRATA QA Contact: ge liu <geliu>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.5CC: geliu
Target Milestone: ---   
Target Release: 4.5.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1859196 Environment:
Last Closed: 2020-08-10 13:50:20 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1859196    
Bug Blocks:    

Description Sam Batschelet 2020-07-21 12:26:02 UTC
+++ This bug was initially created as a clone of Bug #1859196 +++

Description of problem: In the case where a slow or new member receives a snapshot from leader and attempts to applySnapshot meanwhile cluster runs compaction a deadlock can occur.


Version-Release number of selected component (if applicable): etcd 3.x


How reproducible: conditions would need to exist which would be relatively low probability. But the result would be very hard for an already struggling cluster to overcome.


Steps to Reproduce:
1.partition member
2.perform a lot of writes to cluster
3.unpartition member right before compaction

Actual results: cluster can experience deadlock and hang causing possible disruption.


Expected results: cluster remains available 


Additional info:

Comment 3 ge liu 2020-07-29 10:08:23 UTC
Close this bug according to test result in jira issue: https://issues.redhat.com/browse/ETCD-105

Comment 5 errata-xmlrpc 2020-08-10 13:50:20 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.5.5 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:3188