You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Mydumper hangs on table mysql.time_zone_name if --rows is specified.
The dump finishes if
mysql schema is excluded with the regex option
--rows is not specified
Looking at the processlist on my mariadb it shows these two lines from time to time: SELECT /*!40001 SQL_NO_CACHE */ MAX(Name) FROM 'mysql'.'time_zone_name' WHERE BINARY Name like 'H%' SELECT /*!40001 SQL_NO_CACHE */ MIN(Name) FROM 'mysql'.'time_zone_name' WHERE BINARY Name > 'HST'
I am running mariadb 10.5.12 in a docker container locally on an M1 macbook.
I have tried different values for --rows such as 1, 1820(# of rows in this table), 50000 but it will always hang.
I have tried with a fresh docker container.
Describe the bug
Mydumper hangs on table
mysql.time_zone_name
if--rows
is specified.The dump finishes if
Looking at the processlist on my mariadb it shows these two lines from time to time:
SELECT /*!40001 SQL_NO_CACHE */ MAX(Name) FROM 'mysql'.'time_zone_name' WHERE BINARY Name like 'H%'
SELECT /*!40001 SQL_NO_CACHE */ MIN(Name) FROM 'mysql'.'time_zone_name' WHERE BINARY Name > 'HST'
I am running mariadb 10.5.12 in a docker container locally on an M1 macbook.
I have tried different values for --rows such as 1, 1820(# of rows in this table), 50000 but it will always hang.
I have tried with a fresh docker container.
To Reproduce
Command executed:
mydumper --port=3306 --host=127.0.0.1 --user=root --password=test --outputdir=backup/2022-09-21T11:06:11+02:00 --compress --trx-consistency-only --compress-protocol --rows=50000 --verbose=3
What mydumper and myloader version has been used?
mydumper: mydumper 0.12.7-1, built against MySQL 8.0.30
Expected behavior
Dump finishing.
Log
emptydb.log
Backup
If applicable, add the list of content of the database path, an
ls -l
will be enoughEnvironment (please complete the following information):
The text was updated successfully, but these errors were encountered: