[MDEV-32629] 【mariadb-galera】 I have three nodes, but only one node, ibdata1, is very large, what is the reason for this? Created: 2023-10-31 Updated: 2023-10-31 Resolved: 2023-10-31 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | Galera, Storage Engine - InnoDB |
| Affects Version/s: | 10.6.8 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Major |
| Reporter: | luorui | Assignee: | Marko Mäkelä |
| Resolution: | Not a Bug | Votes: | 0 |
| Labels: | None | ||
| Environment: |
centos7 x86 |
||
| Issue Links: |
|
||||||||
| Description |
|
【mariadb-galera】 I have a three-node mariadb-galera cluster, all three are master, but only one node ibdata1 file is very large, what is the reason for this? thanks |
| Comments |
| Comment by Marko Mäkelä [ 2023-10-31 ] |
|
You already asked the same question in MDEV-32622. In short, the reason is that like any other replication for MariaDB Server, Galera is based on logical replication. Each node has its own physical instance of data. The way in which the purge of committed transaction history is scheduled and executed is nondeterministic and can differ between nodes. Furthermore, the existence of a read view will block the purge of any transaction history that would be visible in the read view. An example would be to execute START TRANSACTION WITH CONSISTENT SNAPSHOT and to leave the connection open. |