MDEV-33523 Spurious deadlock error when wsrep_on=OFF

[sciascid]

Avoid starting transactions in wsrep-lib side when wsrep is disabled. It is unnecessary, and causes spurious deadlock errors on transaction clean up.

[janlindstrom]

Can you extend test case for problematic case i.e. where local wsrep_on=OFF transaction is idle too long so that lock wait timeout or similar is triggered for conflicting transaction.

(1) Both local but conflicting is TOI
(2) local and applier (TOI or BF)

[sciascid]

Can you extend test case for problematic case i.e. where local wsrep_on=OFF transaction is idle too long so that lock wait timeout or similar is triggered for conflicting transaction.

(1) Both local but conflicting is TOI (2) local and applier (TOI or BF)

I'm not sure I understand the request: TOI or BF transaction are not subject to lock wait timeouts. They initiate abort and wait until the victim is gone.

[sciascid]

Closing and submitting upstream