Details
-
Bug
-
Status: Stalled (View Workflow)
-
Minor
-
Resolution: Unresolved
-
10.3
-
None
Description
2018-05-21 18:14:11 10 [Warning] mysqld: Versioned table `test`.`table2_int_autoinc`: partition `ver_p1` is full, add more HISTORY partitions
|
2018-05-21 18:14:11 10 [Warning] mysqld: Versioned table `test`.`table0_int_autoinc`: partition `ver_p3` is full, add more HISTORY partitions
|
2018-05-21 18:14:11 10 [Warning] mysqld: Versioned table `test`.`table0_int_autoinc`: partition `ver_p3` is full, add more HISTORY partitions
|
2018-05-21 18:14:11 10 [Warning] mysqld: Versioned table `test`.`table0_int_autoinc`: partition `ver_p3` is full, add more HISTORY partitions
|
2018-05-21 18:14:11 10 [Warning] mysqld: Versioned table `test`.`table0_int_autoinc`: partition `ver_p3` is full, add more HISTORY partitions
|
2018-05-21 18:14:11 10 [Warning] mysqld: Versioned table `test`.`table0_int_autoinc`: partition `ver_p3` is full, add more HISTORY partitions
|
2018-05-21 18:14:11 10 [Warning] mysqld: Versioned table `test`.`table0_int_autoinc`: partition `ver_p3` is full, add more HISTORY partitions
|
2018-05-21 18:14:11 10 [Warning] mysqld: Versioned table `test`.`table2_int_autoinc`: partition `ver_p1` is full, add more HISTORY partitions
|
The warning can be written many times per second, on a busy instance it might completely flood the log. It's good to warn about the problem, but it's not that important to create gigabytes of identical log record. We have some examples for certain records being throttled, I think this one should be as well.