Details
-
Task
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
None
Description
Upon upgrade from MySQL to MariaDB master-info-repository and relay-log-info-repository are completely ignored without even warning in .err log. This causes troubles when migrating slave servers. There should be at least warning if not error in .err log.
Ideally mysql_upgrade script should take care of that and extract the data from mysql.slave_master_info and mysql.slave_relay_log_info to store them in master.info file.
The ticket description is edited to stress on the missed warnings at or after upgrade to mariadb, the former description text is below. In fact its aim to have table-based master info is addressed through mysql.gtid_slave_pos which in combination with CHANGE MASTER TO ... master_use_gtid = slave_pos provides failure tolerance to slave.
Attachments
Issue Links
- relates to
-
MDEV-21753 convert the upstream"s "*-info-repository=TABLE" tables into info files
-
- Stalled
-
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Andrei Elkin [ elkin ] |
| Fix Version/s | 10.5 [ 23123 ] |
julien.fritsch: to why would it be possible to do.. - I merely offered an option if this feature request can be rated as a bug. After all no new option seem need to be provided for the user.
But now when I dwelt into the matter better, the ultimate goal's changes in the upgrade script do not look significant at all.
salle, how about executing a couple of sql queries on the MySQL slave side prior its ultimate stopping:
set @@global.master_info_repository='file'; |
set @@global.relay_log_info_repository='file'; |
I am not sure where to place those lines but the mysql_upgrade docs leaves hope we can
place them there and run the program twice - before and after the new binary are installed:
mysql_upgrade is run after starting the new MariaDB server. Running it before you shut down the old version will not hurt anything and will allow you to make sure it works and figure out authentication for it ahead of time.
|
| Issue Type | Task [ 3 ] | Epic [ 5 ] |
| Priority | Major [ 3 ] | Critical [ 2 ] |
| Summary | Add support for master-info-repository=TABLE | Add warning when postupgrade leftover '*-info-repository=TABLE' exist |
| Link | This issue relates to MDEV-21753 [ MDEV-21753 ] |
| Issue Type | Epic [ 5 ] | Task [ 3 ] |
| Summary | Add warning when postupgrade leftover '*-info-repository=TABLE' exist | table-based master info repository |
| Fix Version/s | 10.5 [ 23123 ] |
| Assignee | Andrei Elkin [ elkin ] | Sujatha Sivakumar [ sujatha.sivakumar ] |
| Fix Version/s | 10.5 [ 23123 ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
Code changes: https://github.com/MariaDB/server/commit/9ae015878f11be3e3033fd1b35357ea5927c6c51
Build Bot testing: http://buildbot.askmonty.org/buildbot/grid?category=main&branch=bb-10.5-sujatha
Changes were reviewed and approved by Andrei.
| Component/s | Replication [ 10100 ] | |
| Fix Version/s | 10.5.2 [ 24030 ] | |
| Fix Version/s | 10.5 [ 23123 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | In Progress [ 3 ] | Closed [ 6 ] |
| Description |
I'd like to see MariaDB support table-based master info repository (see https://dev.mysql.com/doc/refman/5.6/en/replication-options-slave.html#option_mysqld_master-info-repository).
If an InnoDB table were used, it could be encrypted. This would be preferable to having to put the password in plaintext in a text file. |
Upon upgrade from MySQL to MariaDB master-info-repository and relay-log-info-repository are completely ignored without even warning in .err log. This causes troubles when migrating slave servers. There should be at least warning if not error in .err log.
Ideally mysql_upgrade script should take care of that and extract the data from mysql.slave_master_info and mysql.slave_relay_log_info to store them in master.info file. +The ticket description is edited to stress on the missed warnings at or after upgrade to mariadb, the former description text is below. In fact its aim to have _table-based master info_ is addressed through {{mysql.gtid_slave_pos}} which in combination with {{CHANGE MASTER TO ... master_use_gtid = slave_pos }} provides failure tolerance to slave. + ??[I'd like to see MariaDB support table-based master info repository (see https://dev.mysql.com/doc/refman/5.6/en/replication-options-slave.html#option_mysqld_master-info-repository). If an InnoDB table were used, it could be encrypted. This would be preferable to having to put the password in plaintext in a text file.]?? |
| Description |
Upon upgrade from MySQL to MariaDB master-info-repository and relay-log-info-repository are completely ignored without even warning in .err log. This causes troubles when migrating slave servers. There should be at least warning if not error in .err log.
Ideally mysql_upgrade script should take care of that and extract the data from mysql.slave_master_info and mysql.slave_relay_log_info to store them in master.info file. +The ticket description is edited to stress on the missed warnings at or after upgrade to mariadb, the former description text is below. In fact its aim to have _table-based master info_ is addressed through {{mysql.gtid_slave_pos}} which in combination with {{CHANGE MASTER TO ... master_use_gtid = slave_pos }} provides failure tolerance to slave. + ??[I'd like to see MariaDB support table-based master info repository (see https://dev.mysql.com/doc/refman/5.6/en/replication-options-slave.html#option_mysqld_master-info-repository). If an InnoDB table were used, it could be encrypted. This would be preferable to having to put the password in plaintext in a text file.]?? |
Upon upgrade from MySQL to MariaDB master-info-repository and relay-log-info-repository are completely ignored without even warning in .err log. This causes troubles when migrating slave servers. There should be at least warning if not error in .err log.
Ideally mysql_upgrade script should take care of that and extract the data from mysql.slave_master_info and mysql.slave_relay_log_info to store them in master.info file. +The ticket description is edited to stress on the missed warnings at or after upgrade to mariadb, the former description text is below. In fact its aim to have _table-based master info_ is addressed through {{mysql.gtid_slave_pos}} which in combination with {{CHANGE MASTER TO ... master_use_gtid = slave_pos }} provides failure tolerance to slave.+ ??[I'd like to see MariaDB support table-based master info repository (see https://dev.mysql.com/doc/refman/5.6/en/replication-options-slave.html#option_mysqld_master-info-repository). If an InnoDB table were used, it could be encrypted. This would be preferable to having to put the password in plaintext in a text file.]?? |
| Fix Version/s | 10.2.32 [ 24221 ] | |
| Fix Version/s | 10.3.23 [ 24222 ] | |
| Fix Version/s | 10.4.13 [ 24223 ] | |
| Due Date | 2020-04-24 | |
| Labels | need_fixes_in_all_GAs | |
| Priority | Critical [ 2 ] | Major [ 3 ] |
| Resolution | Fixed [ 1 ] | |
| Status | Closed [ 6 ] | Stalled [ 10000 ] |
| Fix Version/s | 10.2.33 [ 24224 ] | |
| Fix Version/s | 10.3.24 [ 24225 ] | |
| Fix Version/s | 10.4.14 [ 24226 ] | |
| Fix Version/s | 10.2.32 [ 24221 ] | |
| Fix Version/s | 10.3.23 [ 24222 ] | |
| Fix Version/s | 10.4.13 [ 24223 ] | |
| Resolution | Fixed [ 1 ] | |
| Status | Stalled [ 10000 ] | Closed [ 6 ] |
| Fix Version/s | 10.4.13 [ 24223 ] |
| Fix Version/s | 10.4.14 [ 24226 ] |
| Fix Version/s | 10.3.23 [ 24222 ] |
| Fix Version/s | 10.3.24 [ 24225 ] |
| Fix Version/s | 10.2.32 [ 24221 ] |
| Fix Version/s | 10.2.33 [ 24224 ] |
| Labels | need_fixes_in_all_GAs |
| Description |
Upon upgrade from MySQL to MariaDB master-info-repository and relay-log-info-repository are completely ignored without even warning in .err log. This causes troubles when migrating slave servers. There should be at least warning if not error in .err log.
Ideally mysql_upgrade script should take care of that and extract the data from mysql.slave_master_info and mysql.slave_relay_log_info to store them in master.info file. +The ticket description is edited to stress on the missed warnings at or after upgrade to mariadb, the former description text is below. In fact its aim to have _table-based master info_ is addressed through {{mysql.gtid_slave_pos}} which in combination with {{CHANGE MASTER TO ... master_use_gtid = slave_pos }} provides failure tolerance to slave.+ ??[I'd like to see MariaDB support table-based master info repository (see https://dev.mysql.com/doc/refman/5.6/en/replication-options-slave.html#option_mysqld_master-info-repository). If an InnoDB table were used, it could be encrypted. This would be preferable to having to put the password in plaintext in a text file.]?? |
Upon upgrade from MySQL to MariaDB master-info-repository and relay-log-info-repository are completely ignored without even warning in .err log. This causes troubles when migrating slave servers. There should be at least warning if not error in .err log.
Ideally mysql_upgrade script should take care of that and extract the data from mysql.slave_master_info and mysql.slave_relay_log_info to store them in master.info file. +The ticket description is edited to stress on the missed warnings at or after upgrade to mariadb, the former description text is below. In fact its aim to have _table-based master info_ is addressed through {{mysql.gtid_slave_pos}} which in combination with {{CHANGE MASTER TO ... master_use_gtid = slave_pos}} provides failure tolerance to slave.+ ??[I'd like to see MariaDB support table-based master info repository (see https://dev.mysql.com/doc/refman/5.6/en/replication-options-slave.html#option_mysqld_master-info-repository). If an InnoDB table were used, it could be encrypted. This would be preferable to having to put the password in plaintext in a text file.]?? |
| Workflow | MariaDB v3 [ 75625 ] | MariaDB v4 [ 132865 ] |
| Summary | table-based master info repository | WAS: table-based master info repository |
| Summary | WAS: table-based master info repository | Upgrade from MySQL to extract data into master.info file WAS: table-based master info repository |
| Zendesk Related Tickets | 201926 201737 127260 | |
| Zendesk active tickets | 201926 201737 |
| Zendesk active tickets | 201737 201926 | 201926 |
| Zendesk active tickets | 201926 | 201926 201737 |
Upon upgrade from MySQL to MariaDB master-info-repository and relay-log-info-repository are completely ignored without even warning in .err log. This causes troubles when migrating slave servers. There should be at least warning if not error in .err log.
Ideally mysql_upgrade script should take care of that and extract the data from mysql.slave_master_info and mysql.slave_relay_log_info to store them in master.info file.