[MDEV-19229] Allow innodb_undo_tablespaces to be changed after database creation - Jira

Thirunarayanan Balathandayuthapani created issue - 2019-04-10 08:02

Thirunarayanan Balathandayuthapani made changes - 2019-04-10 08:02

Field	Original Value	New Value
Status	Open [ 1 ]	Confirmed [ 10101 ]

Thirunarayanan Balathandayuthapani added a comment - 2019-04-10 08:08

I don't see the reason for innodb_rollback_segments variable value have lesser value than 128. Hopefully, we can remove it in the future.

Thirunarayanan Balathandayuthapani added a comment - 2019-04-10 08:08 I don't see the reason for innodb_rollback_segments variable value have lesser value than 128. Hopefully, we can remove it in the future.

Marko Mäkelä made changes - 2019-04-10 08:09

Description

Requirements:
==============
(1) Slow shutdown should have happened before increasing the undo log tablespaces.

This patch should come to effect when there is an increase in the *innodb_undo_tablespaces* variable.

Steps:
=======

(1) Check whether the existing undo log exists. If exists then give the warnings about the slow shutdown and start the server normally.
(2) If not exist then create the specified number of undo tablespace.
(3) Create the rollback segment for each rollback segment in a round robin fashion
(4) Step (2), (3) should happen with the same MTR.

h1. Requirements
* A prior shutdown with {{SET GLOBAL innodb_fast_shutdown=0}} must be executed before adding the undo log tablespaces.

This is because the undo logs must be empty (no incomplete or XA PREPARE transactions, nothing to be purged) so that the old undo tablespaces can discarded and new ones created.

This patch should come to effect when there is an increase in the *innodb_undo_tablespaces* variable.

h1. Steps
# Check whether the existing undo log exists. If exists then give the warnings about the slow shutdown and start the server normally.
# If not exist then create the specified number of undo tablespace.
# Create the rollback segment for each rollback segment in a round robin fashion
# The modifications must happen atomically within a single mini-transaction.

Marko Mäkelä made changes - 2019-04-12 15:31

Link

This issue relates to ~~MDEV-14481~~ [ ~~MDEV-14481~~ ]

Thirunarayanan Balathandayuthapani made changes - 2019-04-23 08:59

Status

Confirmed [ 10101 ]

In Progress [ 3 ]

Marko Mäkelä made changes - 2019-12-04 13:01

Link

This issue is blocked by ~~MDEV-21216~~ [ ~~MDEV-21216~~ ]

Thirunarayanan Balathandayuthapani made changes - 2020-05-19 09:58

Status

In Progress [ 3 ]

Stalled [ 10000 ]

Marko Mäkelä made changes - 2021-10-26 11:56

Link

This issue relates to MENT-1304 [ MENT-1304 ]

Marko Mäkelä made changes - 2021-11-25 06:40

Link

This issue relates to ~~MDEV-27121~~ [ ~~MDEV-27121~~ ]

Sergei Golubchik made changes - 2021-12-06 21:35

Workflow

MariaDB v3 [ 95312 ]

MariaDB v4 [ 143586 ]

Marko Mäkelä made changes - 2022-08-04 06:09

Link

This issue relates to ~~MDEV-21952~~ [ ~~MDEV-21952~~ ]

Marko Mäkelä made changes - 2022-08-04 06:09

Fix Version/s		10.3 [ 22126 ]
Fix Version/s		10.5 [ 23123 ]
Fix Version/s		10.6 [ 24028 ]
Fix Version/s		10.7 [ 24805 ]
Fix Version/s		10.8 [ 26121 ]
Fix Version/s		10.9 [ 26905 ]
Fix Version/s		10.10 [ 27530 ]
Affects Version/s		10.3 [ 22126 ]
Affects Version/s		10.4 [ 22408 ]
Affects Version/s		10.5 [ 23123 ]
Affects Version/s		10.6 [ 24028 ]
Affects Version/s		10.7 [ 24805 ]
Affects Version/s		10.8 [ 26121 ]
Affects Version/s		10.9 [ 26905 ]
Affects Version/s		10.10 [ 27530 ]
Priority	Major [ 3 ]	Critical [ 2 ]
Summary	Increase the undo log tablespace during startup	Allow innodb_undo_tablespaces to be changed after database creation

Thirunarayanan Balathandayuthapani made changes - 2022-08-09 11:07

Status

Stalled [ 10000 ]

In Progress [ 3 ]

Marko Mäkelä made changes - 2022-08-24 10:38

Link

This issue blocks MENT-1304 [ MENT-1304 ]

Marko Mäkelä made changes - 2022-08-24 10:38

Link

This issue relates to MENT-1304 [ MENT-1304 ]

Thirunarayanan Balathandayuthapani made changes - 2022-08-29 06:35

Assignee	Thirunarayanan Balathandayuthapani [ thiru ]	Marko Mäkelä [ marko ]
Status	In Progress [ 3 ]	In Review [ 10002 ]

Matthias Leich added a comment - 2022-09-01 13:09

origin/bb-10.6-~~MDEV-19229~~ 23ab688cec4b3031262bc93921592a04749a4341 2022-08-29T11:58:22+05:30
performed well in RQG testing.

Matthias Leich added a comment - 2022-09-01 13:09 origin/bb-10.6- MDEV-19229 23ab688cec4b3031262bc93921592a04749a4341 2022-08-29T11:58:22+05:30 performed well in RQG testing.

Marko Mäkelä added a comment - 2022-09-05 07:50

thiru, please update the Description to say what will happen when the requirements are not met, and to document each failure scenario.

To my understanding, it was always possible to start InnoDB with a smaller number of innodb_undo_tablespaces so that some of the previously created undo tablespaces would be left unused. The main change here is that we allow new undo tablespaces to be created if the specified innodb_undo_tablespaces exceeds the number of undo tablespace files.

Marko Mäkelä added a comment - 2022-09-05 07:50 thiru , please update the Description to say what will happen when the requirements are not met, and to document each failure scenario. To my understanding, it was always possible to start InnoDB with a smaller number of innodb_undo_tablespaces so that some of the previously created undo tablespaces would be left unused. The main change here is that we allow new undo tablespaces to be created if the specified innodb_undo_tablespaces exceeds the number of undo tablespace files.

Marko Mäkelä made changes - 2022-09-05 07:50

Fix Version/s	10.3 [ 22126 ]
Fix Version/s	10.4 [ 22408 ]
Fix Version/s	10.5 [ 23123 ]
Summary	Allow innodb_undo_tablespaces to be changed after database creation	Allow innodb_undo_tablespaces to be increased after database creation

Marko Mäkelä added a comment - 2022-09-05 08:21

If it is possible to implement the following, I would suggest that we do it like this:

If innodb_undo_tablespaces matches the number of undo tablespace files, the database will start up normally.
Else, if the undo logs are not empty, InnoDB will refuse to start up.
Else, undo tablespace files will be created or deleted to match the specified number of innodb_undo_tablespaces.

This would imply a notable change of existing behaviour: If innodb_undo_tablespaces is specified to be smaller than the number of undo tablespace files, InnoDB could refuse to start up (instead of just ignoring the ‘extra’ files).

Marko Mäkelä added a comment - 2022-09-05 08:21 If it is possible to implement the following, I would suggest that we do it like this: If innodb_undo_tablespaces matches the number of undo tablespace files, the database will start up normally. Else, if the undo logs are not empty, InnoDB will refuse to start up. Else, undo tablespace files will be created or deleted to match the specified number of innodb_undo_tablespaces . This would imply a notable change of existing behaviour: If innodb_undo_tablespaces is specified to be smaller than the number of undo tablespace files, InnoDB could refuse to start up (instead of just ignoring the ‘extra’ files).

Marko Mäkelä made changes - 2022-09-05 08:21

Assignee	Marko Mäkelä [ marko ]	Thirunarayanan Balathandayuthapani [ thiru ]
Status	In Review [ 10002 ]	Stalled [ 10000 ]

Thirunarayanan Balathandayuthapani made changes - 2022-09-14 07:05

Status

Stalled [ 10000 ]

In Progress [ 3 ]

Thirunarayanan Balathandayuthapani made changes - 2022-09-23 09:41

Assignee	Thirunarayanan Balathandayuthapani [ thiru ]	Marko Mäkelä [ marko ]
Status	In Progress [ 3 ]	In Review [ 10002 ]

Marko Mäkelä added a comment - 2022-09-26 09:13

Thank you. This looks feature-complete, including testing that incremental backup will be refused if the undo tablespaces have been reinitialized.

I posted some review comments.

Marko Mäkelä added a comment - 2022-09-26 09:13 Thank you. This looks feature-complete, including testing that incremental backup will be refused if the undo tablespaces have been reinitialized. I posted some review comments .

Marko Mäkelä made changes - 2022-09-26 09:13

Assignee	Marko Mäkelä [ marko ]	Thirunarayanan Balathandayuthapani [ thiru ]
Status	In Review [ 10002 ]	Stalled [ 10000 ]

Thirunarayanan Balathandayuthapani made changes - 2022-10-02 17:56

Assignee	Thirunarayanan Balathandayuthapani [ thiru ]	Marko Mäkelä [ marko ]
Status	Stalled [ 10000 ]	In Review [ 10002 ]

Marko Mäkelä added a comment - 2022-10-04 12:26

I posted some more review comments, mostly minor, mainly about the fault injection.

Marko Mäkelä added a comment - 2022-10-04 12:26 I posted some more review comments , mostly minor, mainly about the fault injection.

Marko Mäkelä made changes - 2022-10-04 12:26

Assignee	Marko Mäkelä [ marko ]	Thirunarayanan Balathandayuthapani [ thiru ]
Status	In Review [ 10002 ]	Stalled [ 10000 ]

Thirunarayanan Balathandayuthapani made changes - 2022-10-07 12:27

Assignee	Thirunarayanan Balathandayuthapani [ thiru ]	Marko Mäkelä [ marko ]
Status	Stalled [ 10000 ]	In Review [ 10002 ]

Marko Mäkelä added a comment - 2022-10-10 09:06

Before this change, in trx_assign_rseg_low() there was some code that would avoid using anything else than the first rollback segment in the system tablespace when the server is started with innodb_undo_tablespaces=0.

With this change, we should rebuild the undo tablespaces whenever the detected number of undo tablespace files disagrees with the specified number. That is, the special handling in trx_assign_rseg_low() can be simplified.

Marko Mäkelä added a comment - 2022-10-10 09:06 Before this change, in trx_assign_rseg_low() there was some code that would avoid using anything else than the first rollback segment in the system tablespace when the server is started with innodb_undo_tablespaces=0 . With this change, we should rebuild the undo tablespaces whenever the detected number of undo tablespace files disagrees with the specified number. That is, the special handling in trx_assign_rseg_low() can be simplified.

Marko Mäkelä made changes - 2022-10-10 09:07

Summary

Allow innodb_undo_tablespaces to be increased after database creation

Allow innodb_undo_tablespaces to be changed after database creation

Thirunarayanan Balathandayuthapani made changes - 2022-10-12 13:36

Description

h1. Requirements
* A prior shutdown with {{SET GLOBAL innodb_fast_shutdown=0}} must be executed before adding the undo log tablespaces.

This is because the undo logs must be empty (no incomplete or XA PREPARE transactions, nothing to be purged) so that the old undo tablespaces can discarded and new ones created.

This patch should come to effect when there is an increase in the *innodb_undo_tablespaces* variable.

h1. Steps
# Check whether the existing undo log exists. If exists then give the warnings about the slow shutdown and start the server normally.
# If not exist then create the specified number of undo tablespace.
# Create the rollback segment for each rollback segment in a round robin fashion
# The modifications must happen atomically within a single mini-transaction.

To change the number of undo tablespaces, we need to reinitialize the data directory (dump + restore).
InnoDB should allow changing number of undo tablespaces as a part of restart process.
System tablespace contains InnoDB dictionary tables, doublewrite buffer, change buffer tree
and undo log pages. By allowing this change, InnoDB can reduce the workload on system tablespace.

h1. Requirements
* A prior shutdown with {{SET GLOBAL innodb_fast_shutdown=0}} must be executed before adding the undo log tablespaces.

This is because the undo logs must be empty (no incomplete or XA PREPARE transactions, nothing to be purged) so that the old undo tablespaces can discarded and new ones created.

This patch should come to effect when there is an increase in the *innodb_undo_tablespaces* variable.

h1. Steps

# Check whether the existing undo log exists. If exists then give the warnings about the slow shutdown and start the server normally.
# If not exist then create the specified number of undo tablespace.
# Create the rollback segment for each rollback segment in a round robin fashion
# The modifications must happen atomically within a single mini-transaction.

Thirunarayanan Balathandayuthapani made changes - 2022-10-12 13:37

Description

To change the number of undo tablespaces, we need to reinitialize the data directory (dump + restore).
InnoDB should allow changing number of undo tablespaces as a part of restart process.
System tablespace contains InnoDB dictionary tables, doublewrite buffer, change buffer tree
and undo log pages. By allowing this change, InnoDB can reduce the workload on system tablespace.

h1. Requirements
* A prior shutdown with {{SET GLOBAL innodb_fast_shutdown=0}} must be executed before adding the undo log tablespaces.

This is because the undo logs must be empty (no incomplete or XA PREPARE transactions, nothing to be purged) so that the old undo tablespaces can discarded and new ones created.

This patch should come to effect when there is an increase in the *innodb_undo_tablespaces* variable.

h1. Steps

# Check whether the existing undo log exists. If exists then give the warnings about the slow shutdown and start the server normally.
# If not exist then create the specified number of undo tablespace.
# Create the rollback segment for each rollback segment in a round robin fashion
# The modifications must happen atomically within a single mini-transaction.

To change the number of undo tablespaces, we need to reinitialize the data directory (dump + restore).
InnoDB should allow changing number of undo tablespaces as a part of restart process.
System tablespace contains InnoDB dictionary tables, doublewrite buffer, change buffer tree
and undo log pages. By allowing this change, InnoDB can reduce the workload on system tablespace.

h1. Requirements
A prior shutdown with {{SET GLOBAL innodb_fast_shutdown=0}} must be executed before adding the undo log tablespaces.

This is because the undo logs must be empty (no incomplete or XA PREPARE transactions, nothing to be purged) so that the old undo tablespaces can discarded and new ones created.

h1. Steps

# Check whether the existing undo log exists. If exists then give the warnings about the slow shutdown and start the server normally.
# If not exist then create the specified number of undo tablespace.
# Create the rollback segment for each rollback segment in a round robin fashion
# The modifications must happen atomically within a single mini-transaction.

Thirunarayanan Balathandayuthapani made changes - 2022-10-12 13:40

Description

To change the number of undo tablespaces, we need to reinitialize the data directory (dump + restore).
InnoDB should allow changing number of undo tablespaces as a part of restart process.
System tablespace contains InnoDB dictionary tables, doublewrite buffer, change buffer tree
and undo log pages. By allowing this change, InnoDB can reduce the workload on system tablespace.

h1. Requirements
A prior shutdown with {{SET GLOBAL innodb_fast_shutdown=0}} must be executed before adding the undo log tablespaces.

This is because the undo logs must be empty (no incomplete or XA PREPARE transactions, nothing to be purged) so that the old undo tablespaces can discarded and new ones created.

h1. Steps

# Check whether the existing undo log exists. If exists then give the warnings about the slow shutdown and start the server normally.
# If not exist then create the specified number of undo tablespace.
# Create the rollback segment for each rollback segment in a round robin fashion
# The modifications must happen atomically within a single mini-transaction.

To change the number of undo tablespaces, we need to reinitialize the data directory (dump + restore).
InnoDB should allow changing number of undo tablespaces as a part of restart process.
System tablespace contains InnoDB dictionary tables, doublewrite buffer, change buffer tree
and undo log pages. By allowing this change, InnoDB can reduce the workload on system tablespace.

h1. Requirements
A prior shutdown with {{SET GLOBAL innodb_fast_shutdown=0}} must be executed before adding the undo log tablespaces.

This is because the undo logs must be empty (no incomplete or XA PREPARE transactions, nothing to be purged) so that the old undo tablespaces can discarded and new ones created.

h1. Steps

# Check whether the existing undo log exists. If exists then give the warnings about the slow shutdown and start the server normally.
# If not exist then free the system tablespace rollback segment header page else throw message about slow shutdown and continue the normal server start operation
# Free the system tablespace rollback segment header page of the slots 1...127
# Set the rollback segment slots (1...127) to
# Create the rollback segment for each rollback segment in a round robin fashion
# The modifications must happen atomically within a single mini-transaction.

Marko Mäkelä made changes - 2022-10-12 14:36

Link

This issue relates to DBAAS-10561 [ DBAAS-10561 ]

Thirunarayanan Balathandayuthapani made changes - 2022-10-12 15:50

Description

To change the number of undo tablespaces, we need to reinitialize the data directory (dump + restore).
InnoDB should allow changing number of undo tablespaces as a part of restart process.
System tablespace contains InnoDB dictionary tables, doublewrite buffer, change buffer tree
and undo log pages. By allowing this change, InnoDB can reduce the workload on system tablespace.

h1. Requirements
A prior shutdown with {{SET GLOBAL innodb_fast_shutdown=0}} must be executed before adding the undo log tablespaces.

This is because the undo logs must be empty (no incomplete or XA PREPARE transactions, nothing to be purged) so that the old undo tablespaces can discarded and new ones created.

h1. Steps

# Check whether the existing undo log exists. If exists then give the warnings about the slow shutdown and start the server normally.
# If not exist then free the system tablespace rollback segment header page else throw message about slow shutdown and continue the normal server start operation
# Free the system tablespace rollback segment header page of the slots 1...127
# Set the rollback segment slots (1...127) to
# Create the rollback segment for each rollback segment in a round robin fashion
# The modifications must happen atomically within a single mini-transaction.

To change the number of undo tablespaces, we need to reinitialize the data directory (dump + restore).
InnoDB should allow changing number of undo tablespaces as a part of restart process.
System tablespace contains InnoDB dictionary tables, doublewrite buffer, change buffer tree
and undo log pages. By allowing this change, InnoDB can reduce the workload on system tablespace.

h1. Requirements
A prior shutdown with {{SET GLOBAL innodb_fast_shutdown=0}} must be executed before adding the undo log tablespaces.

This is because the undo logs must be empty (no incomplete or XA PREPARE transactions, nothing to be purged) so that the old undo tablespaces can discarded and new ones created.

h1. Steps

# Check whether the existing undo log exists. If exists then give the warnings about the slow shutdown and start the server normally.
# If not exist then free the system tablespace rollback segment header page else throw message about slow shutdown and continue the normal server start operation
# Free the system tablespace rollback segment header page of the slots 1...127
# Reset the TRX_SYS page and reinitialize the system tablespace rollback segment slot(0th slot), doublewrite information,
update the binlog info and WSREP info in system rollback segment header page (0th slot page)
Step(3) and (4) should happen within a single mini-transaction
# Delete the old undo tablespaces if any
# Make checkpoint to get rid of old undo tablespace redo log records
# Read the latest MAX_SPACE_ID from dictionary header page
# Create the new specified undo log tablespace and initialize the page0 of all undo tablespaces
Step (7) and Step (8) should happen within a single mini-transaction
# Make the checkpoint again to make sure that next startup or backup reads the undo log tablespaces before
opening the redo log records
# Create the rollback segment for each rollback segment in a round robin fashion

Thirunarayanan Balathandayuthapani made changes - 2022-10-14 10:29

Status

In Review [ 10002 ]

In Testing [ 10301 ]

Thirunarayanan Balathandayuthapani made changes - 2022-10-14 10:29

Assignee

Marko Mäkelä [ marko ]

Matthias Leich [ mleich ]

Matthias Leich added a comment - 2022-10-19 10:18

origin/bb-10.6-MDEV-19229 162cccee73bc04cf089d35cf457eb109596aec4e 2022-10-17T21:51:01+05:30

performed well in RQG testing. The bad effects observed are in origin/10.6 1feccb505f9ec5cada8f8e2c544f736c1a533633 2022-10-13T09:09:03+03:00 too.

Matthias Leich added a comment - 2022-10-19 10:18 origin/bb-10.6-MDEV-19229 162cccee73bc04cf089d35cf457eb109596aec4e 2022-10-17T21:51:01+05:30 performed well in RQG testing. The bad effects observed are in origin/10.6 1feccb505f9ec5cada8f8e2c544f736c1a533633 2022-10-13T09:09:03+03:00 too.

Matthias Leich made changes - 2022-10-19 10:19

Assignee	Matthias Leich [ mleich ]	Thirunarayanan Balathandayuthapani [ thiru ]
Status	In Testing [ 10301 ]	Stalled [ 10000 ]

Marko Mäkelä added a comment - 2022-10-20 10:29

To reduce the risk of potentially breaking anything in stable releases, a decision was made to only fix this in the 10.11 series for now. Technically, the same change should work in any version starting with 10.6 where it was developed and tested.

Marko Mäkelä added a comment - 2022-10-20 10:29 To reduce the risk of potentially breaking anything in stable releases, a decision was made to only fix this in the 10.11 series for now. Technically, the same change should work in any version starting with 10.6 where it was developed and tested.

Marko Mäkelä made changes - 2022-10-20 10:29

Fix Version/s		10.11 [ 27614 ]
Fix Version/s	10.6 [ 24028 ]
Fix Version/s	10.7 [ 24805 ]
Fix Version/s	10.8 [ 26121 ]
Fix Version/s	10.9 [ 26905 ]
Fix Version/s	10.10 [ 27530 ]
Affects Version/s		10.11 [ 27614 ]

Marko Mäkelä added a comment - 2022-10-20 13:46

I posted some review comments for the 10.11 version.

Marko Mäkelä added a comment - 2022-10-20 13:46 I posted some review comments for the 10.11 version .

Marko Mäkelä added a comment - 2022-10-21 14:13

The revised patch for 10.11 is OK to push, as soon as it has passed the stress tests.

Marko Mäkelä added a comment - 2022-10-21 14:13 The revised patch for 10.11 is OK to push, as soon as it has passed the stress tests.

Thirunarayanan Balathandayuthapani made changes - 2022-10-25 06:31

Fix Version/s		10.11.1 [ 28454 ]
Fix Version/s	10.11 [ 27614 ]
Resolution		Fixed [ 1 ]
Status	Stalled [ 10000 ]	Closed [ 6 ]

Marko Mäkelä made changes - 2022-11-09 09:33

Link

This issue relates to ~~MDEV-29983~~ [ ~~MDEV-29983~~ ]

Marko Mäkelä made changes - 2022-11-09 09:44

Link

This issue blocks ~~MDEV-29986~~ [ ~~MDEV-29986~~ ]

Julien Fritsch made changes - 2022-11-15 16:16

Link

This issue blocks MENT-1650 [ MENT-1650 ]

Marko Mäkelä made changes - 2022-11-29 10:25

Link

This issue causes ~~MDEV-30122~~ [ ~~MDEV-30122~~ ]

Ralf Gebhardt made changes - 2023-01-11 15:44

Affects Version/s	10.3 [ 22126 ]
Affects Version/s	10.4 [ 22408 ]
Affects Version/s	10.5 [ 23123 ]
Affects Version/s	10.6 [ 24028 ]
Affects Version/s	10.7 [ 24805 ]
Affects Version/s	10.8 [ 26121 ]
Affects Version/s	10.9 [ 26905 ]
Affects Version/s	10.10 [ 27530 ]
Affects Version/s	10.11 [ 27614 ]
Issue Type	Bug [ 1 ]	Task [ 3 ]

Marko Mäkelä made changes - 2023-01-25 10:33

Link

This issue causes ~~MDEV-30158~~ [ ~~MDEV-30158~~ ]

Thirunarayanan Balathandayuthapani made changes - 2023-02-24 10:18

Link

This issue causes ~~MDEV-30311~~ [ ~~MDEV-30311~~ ]

Ralf Gebhardt made changes - 2023-03-02 14:03

Link

This issue causes MENT-1751 [ MENT-1751 ]

Marko Mäkelä made changes - 2023-06-26 09:13

Link

This issue relates to ~~MDEV-31488~~ [ ~~MDEV-31488~~ ]

Marko Mäkelä made changes - 2023-08-02 12:44

Link

This issue relates to ~~MDEV-14795~~ [ ~~MDEV-14795~~ ]

Marko Mäkelä made changes - 2024-03-07 07:55

Link

This issue causes ~~MDEV-32974~~ [ ~~MDEV-32974~~ ]

Marko Mäkelä made changes - 2024-04-03 09:37

Link

This issue is duplicated by ~~MDEV-17555~~ [ ~~MDEV-17555~~ ]

Marko Mäkelä made changes - 2024-04-24 05:13

Link

This issue is duplicated by ~~MDEV-10373~~ [ ~~MDEV-10373~~ ]

Thirunarayanan Balathandayuthapani made changes - 2024-05-21 13:45

Link

This issue causes ~~MDEV-34200~~ [ ~~MDEV-34200~~ ]

Jira Automation (IT) made changes - 2024-07-04 04:03

Zendesk Related Tickets

131727

MariaDB Server

Allow innodb_undo_tablespaces to be changed after database creation

Details

Description

Requirements

Steps

Attachments

Issue Links

Activity

People

Dates

Git Integration