[MDEV-24923] Port selected Galera conflict resolution changes from 10.6 - Jira

XML

Word

Printable

Details

Type: Bug
Status: Closed (View Workflow)
Priority: Critical
Resolution: Fixed
Affects Version/s: 10.2(EOL), 10.3(EOL), 10.4(EOL), 10.5
Fix Version/s: 10.2.38, 10.3.29, 10.4.19, 10.5.10
Component/s: Galera
Labels:
None

Description

Selected changes:

Add condition on trx->state == TRX_STATE_COMMITTED_IN_MEMORY in order to avoid unnecessary work. If a transaction has already been committed or rolled back, it will release its locks in lock_release() and let the waiting thread(s) continue execution.
Let BF wait on lock_rec_has_to_wait

Attachments

Issue Links

relates to

MDEV-23328 Server hang due to Galera lock conflict resolution

Closed

MDEV-25378 MariaDB 10.4.18 (galera) crash

Closed

MDEV-25427 InnoDB: Conflicting lock on table crash

Closed

MDEV-25579 MariaDB 10.4.18 crashes with InnoDB: Conflicting lock on table

Closed

MDEV-25170 Mariadb/Galera crashes after FreeSWITCH shutdown

Closed

MDEV-25266 Port Galera cleanups done in MDEV-24923 to 10.6

Closed

(1 relates to)

Activity

People

Assignee:: Jan Lindström (Inactive)

Reporter:: Jan Lindström (Inactive)

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Dates

Created:: 2021-02-19 06:11

Updated:: 2024-08-27 15:06

Resolved:: 2021-03-30 06:39

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.