[MDEV-17029] mariabackup fails under load with schema changes Created: 2018-08-21 Updated: 2019-06-19 Resolved: 2018-09-05 |
|
| Status: | Closed |
| Project: | MariaDB Server |
| Component/s: | mariabackup |
| Affects Version/s: | 10.2.16 |
| Fix Version/s: | N/A |
| Type: | Bug | Priority: | Critical |
| Reporter: | Konstantin Vasserman | Assignee: | Vladislav Vaintroub |
| Resolution: | Incomplete | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Ubuntu 18:04, Ubuntu 16:04, Galera cluster |
||
| Issue Links: |
|
||||||||||||||||||||||||
| Description |
|
When we run mariabackup on a galera cluster nodes with a lot of data/databases (over 1500 databases with 700GB of data at the moment), if the servers are under moderate use mariabackup tool fails with the following log messages:
The cluster is under load, but I think these are happening when schema is being modified (databases created, dropped and so on). It could be related to tables flooded with records, because when we create databases we populate them with a lot of records. This happens both when running mariabackup manually or when it's triggered by SST. The log file mentioned in the message "innobackup.backup.log" cannot be found anywhere on the system. So we have no more info about the error. Unfortunately, this is a production cluster and we can't do much in a way of debugging on these machines. |
| Comments |
| Comment by Vladislav Vaintroub [ 2018-09-05 ] |
|
I'm going to close it since there is no actionable info about the bug. |