diff options
| author | Jan Lindström <jan.lindstrom@mariadb.com> | 2018-07-25 08:21:25 +0300 |
|---|---|---|
| committer | Jan Lindström <jan.lindstrom@mariadb.com> | 2018-07-25 08:24:09 +0300 |
| commit | 57cde8ccd19675dc98e3cbacf0ef5c72cb188e49 (patch) | |
| tree | 814037fceab4737ec78f72ef56e409d755e68050 /support-files | |
| parent | a0d33dc6ef6f380fb5a2d166e75ed6fed2dfce9d (diff) | |
| download | mariadb-git-57cde8ccd19675dc98e3cbacf0ef5c72cb188e49.tar.gz | |
MDEV-15822: WSREP: BF lock wait long for trx
In Galera BF (brute force) transactions may not wait for lock requests
and normally BF-transaction would select transaction holding conflicting
locks as a victim for rollback. However, background statistic calculation
transaction is InnoDB internal transaction and it has no thd i.e. it can't be
selected as a victim. If background statistics calculation transaction holds
conflicting locks to statistics tables it will cause BF lock wait long
error message. Correct way to handle background statistics calculation is to
acquire thd for transaction but that change is too big for GA-releases and
there are other reported problems on background statistics calculation.
This fix avoids adding a table to background statistics calculation if
Diffstat (limited to 'support-files')
0 files changed, 0 insertions, 0 deletions