Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
N/A
-
None
Description
Ian Gilfillan Can you document that innodb-lock-schedule-algorithm is read-only variables (i.e. it can't be changed dynamically) and that VATS method is not supported on Galera.
Here what documentation should mention:
10.1, default is FCFS and InnoDB will refuse to start if VATS is used with galera.
>=10.2 default is VATS and in galera it will be changed to FCFS.
Attachments
Issue Links
- relates to
-
MDEV-12837 WSREP: BF lock wait long
-
- Closed
-
Activity
Field | Original Value | New Value |
---|---|---|
Link |
This issue relates to |
Fix Version/s | N/A [ 14700 ] | |
Affects Version/s | N/A [ 14700 ] |
Resolution | Not a Bug [ 6 ] | |
Status | Open [ 1 ] | Closed [ 6 ] |
Resolution | Not a Bug [ 6 ] | |
Status | Closed [ 6 ] | Stalled [ 10000 ] |
Resolution | Fixed [ 1 ] | |
Status | Stalled [ 10000 ] | Closed [ 6 ] |
Workflow | MariaDB v3 [ 84629 ] | MariaDB v4 [ 153457 ] |
jplindst will setting innodb-lock-schedule-algorithm details to FCFS be sufficient for people currently running 10.2 (before 10.2.12 is released), or should people avoid upgrading altogether if running Galera?