[BUG] No binlog info in Metadata
if-jeremy opened this issue · comments
Describe the bug
A clear and concise description of what the bug is.
Metadata file does not include binlog position when dumping RDS Aurora 2 (mysql 5.7) database
To Reproduce
Command executed:
- mydumper with all the parameters
mydumper --ssl \
-h {hostname} -o /dump --verbose=3 --port=3306 \
--kill-long-queries --chunk-filesize=5120 --build-empty-files \
--events --routines --triggers --compress --less-locking \
--success-on-1146 -B db1,db2,db3 \
-u {user} -p \"{password}\""
What mydumper and myloader version has been used?
mydumper v0.16.3-2, built against MySQL 8.4.0 with SSL support
Expected behavior
A clear and concise description of what you expected to happen.
Expect to see master log position in the metadata file
Environment (please complete the following information):
- OS version: [e.g. CentOS 7.9, Ubuntu 20.04]
- MyDumper version: [ mydumper --version ]
Amazon Linux 2023 for ARM64, mydumper 0.16.3-2 (within Docker container)
Additional context
Add any other context about the problem here.
I suspect this is because of the patch #1512 - SHOW MASTER STATUS is deprecated in 8.2 - but it still needs to be used for older versions that do not support show_binary_log_status
Hi @if-jeremy,
I reviewed the code and I had to test it on my own and I found no issue. What I got on the log is:
2024-06-06 16:54:27 [WARNING] - Couldn't get master position: Access denied; you need (at least one of) the SUPER, REPLICATION CLIENT privilege(s) for this operation
I will need a log on your end to confirm that you are not seeing that entry.