Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1703267

Summary: [RFE] Expose MySQL lock_wait_timeout via puppet-tripleo
Product: Red Hat OpenStack Reporter: Andreas Karis <akaris>
Component: puppet-tripleoAssignee: Luca Miccini <lmiccini>
Status: CLOSED ERRATA QA Contact: pkomarov
Severity: medium Docs Contact:
Priority: high    
Version: 13.0 (Queens)CC: aschultz, jjoyce, jschluet, lmiccini, pkomarov, slinaber, tvignaud
Target Milestone: ---Keywords: FutureFeature, Triaged, ZStream
Target Release: 13.0 (Queens)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: puppet-tripleo-8.4.1-10.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-07-10 13:05:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Andreas Karis 2019-04-25 23:14:50 UTC 
Description of problem:
Expose MySQL lock_wait_timeout via puppet-tripleo

Internal link:
http://post-office.corp.redhat.com/archives/rhos-tech/2019-April/msg00319.html

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Michael Bayer
	
Apr 24, 2019, 2:01 PM (1 day ago)
	
to Alex, me, rhos-tech
There are various BZs and upstreams about exposing more innodb
parameters, but I don't see one that addresses lock_wait_timeout which
is a bit surprising:

https://review.opendev.org/#/c/603996/
https://bugzilla.redhat.com/show_bug.cgi?id=1472249
https://bugzilla.redhat.com/show_bug.cgi?id=1483656

the path to have innodb_lock_wait_timeout would be at least a setting
in puppet-tripleo so we can get to it via a hiera variable.

There's definitely been discussion about lock_wait_timeout which I
can't locate, but if I had to guess what the concern is on that one,
it's that a system that is subject to lots of these timeouts is
experiencing some other kind of performance issue, increasing the
timeouts just bakes in the slow behavior.  That's probably why the
kbase linked says "for testing" on it.

There's also been discussion about allowing all mysql / mariadb config
to be generically open in tripleo, I've been opposed to that for
reasons of being able to track what knobs customers are turning, but I
don't recall if that discussion had any resolution.   I'm certainly OK
with innodb_lock_wait_timeout being available at this point.
Comment 1 Luca Miccini 2019-05-09 12:04:05 UTC 
master: https://review.opendev.org/#/c/656943

cherry picks:

stein: https://review.opendev.org/#/c/658059
rocky: https://review.opendev.org/#/c/658060
queens: https://review.opendev.org/#/c/658061
Comment 12 errata-xmlrpc 2019-07-10 13:05:12 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, 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-2019:1738