dev-db/mariadb-10.2.21 (and possibly other versions) with USE=galera: Forms a cluster, ISTs work, but SSTs do not work with wsrep_sst_xtrabackup-v2 method because xtrabackup fails. wsrep_sst_rsync works, however. XtraBackup SST failure from the receiving side: 2019-02-10 14:11:25 140209339733760 [Note] WSREP: Prepared SST request: xtrabackup-v2|10.24.32.10:4444/xtrabackup_sst//1 2019-02-10 14:11:25 140209339733760 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification. 2019-02-10 14:11:25 140209339733760 [Note] WSREP: REPL Protocols: 8 (3, 2) 2019-02-10 14:11:25 140209339733760 [Note] WSREP: Assign initial position for certification: 4407605, protocol version: 3 2019-02-10 14:11:25 140207103223552 [Note] WSREP: Service thread queue flushed. 2019-02-10 14:11:25 140209339733760 [Warning] WSREP: Failed to prepare for incremental state transfer: Local state seqno is undefined: 1 (Operation not permitted) at galera/src/replicator_str.cpp:prepare_for_IST():491. IST will be unavailable. 2019-02-10 14:11:25 140207038920448 [Note] WSREP: Member 2.0 (babylon5) requested state transfer from 'narn,minbar'. Selected 1.0 (narn)(SYNCED) as donor. 2019-02-10 14:11:25 140207038920448 [Note] WSREP: Shifting PRIMARY -> JOINER (TO: 4407605) 2019-02-10 14:11:25 140209339733760 [Note] WSREP: Requesting state transfer: success, donor: 1 2019-02-10 14:11:25 140209339733760 [Note] WSREP: GCache history reset: c286e09d-1e7e-11e9-8db5-367539f9aa5c:0 -> c286e09d-1e7e-11e9-8db5-367539f9aa5c:4407605 WSREP_SST: [INFO] Evaluating socat -u TCP-LISTEN:4444,reuseaddr stdio | xbstream -x; RC=( ${PIPESTATUS[@]} ) (20190210 14:11:25.995) WSREP_SST: [INFO] Proceeding with SST (20190210 14:11:25.997) encryption: using gcrypt 1.8.3 WSREP_SST: [INFO] Cleaning the existing datadir and innodb-data/log directories (20190210 14:11:26.001) removed '/var/lib/mysql/irssi/carriers.frm' removed '/var/lib/mysql/irssi/carriers.ibd' ... ... ... removed '/var/lib/mysql/aria_log_control' removed '/var/lib/mysql/ib_buffer_pool' my_print_defaults: [ERROR] unknown option '--mysqld' WSREP_SST: [INFO] Waiting for SST streaming to complete! (20190210 14:11:26.258) 2019-02-10 14:11:27 140207055697664 [Note] WSREP: (dc29d710, 'tcp://10.24.32.10:4567') turning message relay requesting off 2019-02-10 14:11:36 140207038920448 [Warning] WSREP: 1.0 (narn): State transfer to 2.0 (babylon5) failed: -22 (Invalid argument) 2019-02-10 14:11:36 140207038920448 [ERROR] WSREP: gcs/src/gcs_group.cpp:gcs_group_handle_join_msg():737: Will never receive state. Need to abort. 2019-02-10 14:11:36 140207038920448 [Note] WSREP: gcomm: terminating thread 2019-02-10 14:11:36 140207038920448 [Note] WSREP: gcomm: joining thread 2019-02-10 14:11:36 140207038920448 [Note] WSREP: gcomm: closing backend 2019-02-10 14:11:36 140207038920448 [Note] WSREP: view(view_id(NON_PRIM,c40c3757,53) memb { dc29d710,0 } joined { } left { } partitioned { c40c3757,0 c4657346,0 }) 2019-02-10 14:11:36 140207038920448 [Note] WSREP: view((empty)) 2019-02-10 14:11:36 140207038920448 [Note] WSREP: gcomm: closed 2019-02-10 14:11:36 140207038920448 [Note] WSREP: /usr/sbin/mysqld: Terminated. WSREP_SST: [ERROR] Parent mysqld process (PID:4711) terminated unexpectedly. (20190210 14:11:36.407) WSREP_SST: [ERROR] Removing /var/lib/mysql//.sst/xtrabackup_galera_info file due to signal (20190210 14:11:36.413) WSREP_SST: [ERROR] Cleanup after exit with status:32 (20190210 14:11:36.418) And from the sending side: 2019-02-10 14:11:25 139910044444416 [Note] WSREP: Member 2.0 (babylon5) requested state transfer from 'narn,minbar'. Selected 1.0 (narn)(SYNCED) as donor. 2019-02-10 14:11:25 139910044444416 [Note] WSREP: Shifting SYNCED -> DONOR/DESYNCED (TO: 4407605) 2019-02-10 14:11:25 139912294303488 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification. 2019-02-10 14:11:25 139904570881792 [Note] WSREP: Running: 'wsrep_sst_xtrabackup-v2 --role 'donor' --address '10.24.32.10:4444/xtrabackup_sst//1' --socket '/var/run/mysqld/mysqld.sock' --datadir '/var/lib/mysql/' --defaults-file '/etc/mysql/my.cnf' '' --gtid 'c286e09d-1e7e-11e9-8db5-367539f9aa5c:4407605' --gtid-domain-id '0'' 2019-02-10 14:11:25 139912294303488 [Note] WSREP: sst_donor_thread signaled with 0 my_print_defaults: [ERROR] unknown option '--mysqld' my_print_defaults: [ERROR] unknown option '--mysqld' my_print_defaults: [ERROR] unknown option '--mysqld' WSREP_SST: [INFO] Streaming with xbstream (20190210 14:11:25.884) WSREP_SST: [INFO] Using socat as streamer (20190210 14:11:25.886) my_print_defaults: [ERROR] unknown option '--mysqld' WSREP_SST: [INFO] Using /tmp/tmp.12b3lCzfjm as xtrabackup temporary directory (20190210 14:11:25.900) WSREP_SST: [INFO] Using /tmp/tmp.ONRNqqs5Gz as innobackupex temporary directory (20190210 14:11:25.902) WSREP_SST: [INFO] Streaming GTID file before SST (20190210 14:11:25.906) WSREP_SST: [INFO] Evaluating xbstream -c ${INFO_FILE} | socat -u stdio TCP:10.24.32.10:4444; RC=( ${PIPESTATUS[@]} ) (20190210 14:11:25.913) encryption: using gcrypt 1.8.3 WSREP_SST: [INFO] Sleeping before data transfer for SST (20190210 14:11:25.979) 2019-02-10 14:11:27 139910052837120 [Note] WSREP: (c4657346, 'tcp://10.24.32.16:4567') turning message relay requesting off WSREP_SST: [INFO] Streaming the backup to joiner at 10.24.32.10 4444 (20190210 14:11:35.981) WSREP_SST: [INFO] Evaluating innobackupex --defaults-file=/etc/mysql/my.cnf --no-version-check $tmpopts $INNOEXTRA --galera-info --stream=$sfmt $itmpdir 2>${DATA}/innobackup.backup.log | socat -u stdio TCP:10.24.32.10:4444; RC=( ${PIPESTATUS[@]} ) (20190210 14:11:35.983) 2019-02-10 14:11:36 139912293381888 [Warning] Aborted connection 15 to db: 'unconnected' user: 'root' host: 'localhost' (Got an error reading communication packets) WSREP_SST: [ERROR] innobackupex finished with error: 1. Check /var/lib/mysql//innobackup.backup.log (20190210 14:11:36.296) WSREP_SST: [ERROR] Cleanup after exit with status:22 (20190210 14:11:36.298) WSREP_SST: [INFO] Cleaning up temporary directories (20190210 14:11:36.300) 2019-02-10 14:11:36 139904570881792 [ERROR] WSREP: Failed to read from: wsrep_sst_xtrabackup-v2 --role 'donor' --address '10.24.32.10:4444/xtrabackup_sst//1' --socket '/var/run/mysqld/mysqld.sock' --datadir '/var/lib/mysql/' --defaults-file '/etc/mysql/my.cnf' '' --gtid 'c286e09d-1e7e-11e9-8db5-367539f9aa5c:4407605' --gtid-domain-id '0' 2019-02-10 14:11:36 139904570881792 [ERROR] WSREP: Process completed with error: wsrep_sst_xtrabackup-v2 --role 'donor' --address '10.24.32.10:4444/xtrabackup_sst//1' --socket '/var/run/mysqld/mysqld.sock' --datadir '/var/lib/mysql/' --defaults-file '/etc/mysql/my.cnf' '' --gtid 'c286e09d-1e7e-11e9-8db5-367539f9aa5c:4407605' --gtid-domain-id '0': 22 (Invalid argument) 2019-02-10 14:11:36 139904570881792 [ERROR] WSREP: Command did not run: wsrep_sst_xtrabackup-v2 --role 'donor' --address '10.24.32.10:4444/xtrabackup_sst//1' --socket '/var/run/mysqld/mysqld.sock' --datadir '/var/lib/mysql/' --defaults-file '/etc/mysql/my.cnf' '' --gtid 'c286e09d-1e7e-11e9-8db5-367539f9aa5c:4407605' --gtid-domain-id '0' 2019-02-10 14:11:36 139910044444416 [Warning] WSREP: 1.0 (narn): State transfer to 2.0 (babylon5) failed: -22 (Invalid argument) 2019-02-10 14:11:36 139910044444416 [Note] WSREP: Shifting DONOR/DESYNCED -> JOINED (TO: 4407605) 2019-02-10 14:11:36 139910044444416 [Note] WSREP: Member 1.0 (narn) synced with group. 2019-02-10 14:11:36 139910044444416 [Note] WSREP: Shifting JOINED -> SYNCED (TO: 4407605) 2019-02-10 14:11:36 139912346994432 [Note] WSREP: Synchronized with group, ready for connections Hypothesis: The problem here MAY be related to the fact that MariaDB's GTIDs are different from, and incompatible with, Community MySQL's and thus Percona's. ALSO SEE: #662566 which declared the --mysqld problem resolved in 10.1.34, but it is still occurring (or has returned) in 10.2.21.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e8f945a697b85889e16706719ecc537cd68b9ab4 commit e8f945a697b85889e16706719ecc537cd68b9ab4 Author: Brian Evans <grknight@gentoo.org> AuthorDate: 2019-03-05 21:05:19 +0000 Commit: Brian Evans <grknight@gentoo.org> CommitDate: 2019-03-05 21:05:19 +0000 dev-db/mariadb: Revbumps to fix galera and mysqld_safe bugs Due to client-libs changes Closes: https://bugs.gentoo.org/672698 Closes: https://bugs.gentoo.org/677674 Package-Manager: Portage-2.3.62, Repoman-2.3.12 Signed-off-by: Brian Evans <grknight@gentoo.org> dev-db/mariadb/Manifest | 2 +- dev-db/mariadb/{mariadb-10.1.38.ebuild => mariadb-10.1.38-r1.ebuild} | 2 +- dev-db/mariadb/{mariadb-10.2.22.ebuild => mariadb-10.2.22-r1.ebuild} | 2 +- dev-db/mariadb/{mariadb-10.3.12.ebuild => mariadb-10.3.12-r1.ebuild} | 4 ++-- 4 files changed, 5 insertions(+), 5 deletions(-)
I am still seeing wsrep_sst_xtrabackup-v2 not working. The error message has changed, but it is still failing. This is with dev-db/mariadb-10.2.22-r1 and dev-db/percona-xtrabackup-2.14.12. I will retest with percona-xtrabackup-2.14.13. Error on joiner: 2019-03-12 12:45:43 140027796379392 [Warning] WSREP: Failed to prepare for incremental state transfer: Local state UUID (00000000-0000-0000-0000-000000000000) does not match group state UUID (c286e09d-1e7e-11e9-8db5-367539f9aa5c): 1 (Operation not permitted) at galera/src/replicator_str.cpp:prepare_for_IST():482. IST will be unavailable. 2019-03-12 12:45:43 140025505244928 [Note] WSREP: Member 1.0 (narn) requested state transfer from 'babylon5,minbar'. Selected 0.0 (babylon5)(SYNCED) as donor. 2019-03-12 12:45:43 140025505244928 [Note] WSREP: Shifting PRIMARY -> JOINER (TO: 16202149) 2019-03-12 12:45:43 140027796379392 [Note] WSREP: Requesting state transfer: success, donor: 0 2019-03-12 12:45:43 140027796379392 [Note] WSREP: GCache history reset: 00000000-0000-0000-0000-000000000000:0 -> c286e09d-1e7e-11e9-8db5-367539f9aa5c:16202149 WSREP_SST: [INFO] Evaluating socat -u TCP-LISTEN:4444,reuseaddr stdio | xbstream -x; RC=( ${PIPESTATUS[@]} ) (20190312 12:45:44.127) WSREP_SST: [INFO] Proceeding with SST (20190312 12:45:44.128) encryption: using gcrypt 1.8.3 WSREP_SST: [INFO] Cleaning the existing datadir and innodb-data/log directories (20190312 12:45:44.131) removed '/var/lib/mysql/irssi/carriers.frm' [...] removed '/var/lib/mysql/multi-master.info' WSREP_SST: [INFO] Waiting for SST streaming to complete! (20190312 12:45:44.673) 2019-03-12 12:45:45 140025513637632 [Note] WSREP: (465574c5, 'tcp://10.24.32.16:4567') turning message relay requesting off 2019-03-12 12:45:54 140025505244928 [Warning] WSREP: 0.0 (babylon5): State transfer to 1.0 (narn) failed: -22 (Invalid argument) 2019-03-12 12:45:54 140025505244928 [ERROR] WSREP: gcs/src/gcs_group.cpp:gcs_group_handle_join_msg():737: Will never receive state. Need to abort. 2019-03-12 12:45:54 140025505244928 [Note] WSREP: gcomm: terminating thread 2019-03-12 12:45:54 140025505244928 [Note] WSREP: gcomm: joining thread 2019-03-12 12:45:54 140025505244928 [Note] WSREP: gcomm: closing backend 2019-03-12 12:45:54 140025505244928 [Note] WSREP: view(view_id(NON_PRIM,08609a15,113) memb { 465574c5,0 } joined { } left { } partitioned { 08609a15,0 f7980c17,0 }) 2019-03-12 12:45:54 140025505244928 [Note] WSREP: view((empty)) 2019-03-12 12:45:54 140025505244928 [Note] WSREP: gcomm: closed 2019-03-12 12:45:54 140025505244928 [Note] WSREP: /usr/sbin/mysqld: Terminated. WSREP_SST: [ERROR] Parent mysqld process (PID:28421) terminated unexpectedly. (20190312 12:45:54.251) WSREP_SST: [ERROR] Removing /var/lib/mysql//.sst/xtrabackup_galera_info file due to signal (20190312 12:45:54.254) WSREP_SST: [ERROR] Cleanup after exit with status:32 (20190312 12:45:54.257) Error on donor: 2019-03-12 12:45:43 140260394657536 [Note] WSREP: Shifting SYNCED -> DONOR/DESYNCED (TO: 16202149) 2019-03-12 12:45:43 140262685484800 [Note] WSREP: wsrep_notify_cmd is not defined, skipping notification. 2019-03-12 12:45:43 140255164364544 [Note] WSREP: Running: 'wsrep_sst_xtrabackup-v2 --role 'donor' --address '10.24.32.16:4444/xtrabackup_sst//1' --socket '/var/run/mysqld/mysqld.sock' --datadir '/var/lib/mysql/' --defaults-file '/etc/mysql/my.cnf' '' --gtid 'c286e09d-1e7e-11e9-8db5-367539f9aa5c:16202149' --gtid-domain-id '0'' 2019-03-12 12:45:43 140262685484800 [Note] WSREP: sst_donor_thread signaled with 0 WSREP_SST: [INFO] Streaming with xbstream (20190312 12:45:44.064) WSREP_SST: [INFO] Using socat as streamer (20190312 12:45:44.067) WSREP_SST: [INFO] Using /tmp/tmp.S47fmBTubD as innobackupex temporary directory (20190312 12:45:44.083) WSREP_SST: [INFO] Streaming GTID file before SST (20190312 12:45:44.088) WSREP_SST: [INFO] Evaluating xbstream -c ${INFO_FILE} | socat -u stdio TCP:10.24.32.16:4444; RC=( ${PIPESTATUS[@]} ) (20190312 12:45:44.098) encryption: using gcrypt 1.8.3 WSREP_SST: [INFO] Sleeping before data transfer for SST (20190312 12:45:44.122) 2019-03-12 12:45:45 140260403050240 [Note] WSREP: (08609a15, 'tcp://10.24.32.10:4567') turning message relay requesting off WSREP_SST: [INFO] Streaming the backup to joiner at 10.24.32.16 4444 (20190312 12:45:54.128) WSREP_SST: [INFO] Evaluating innobackupex --defaults-file=/etc/mysql/my.cnf --no-version-check $tmpopts $INNOEXTRA --galera-info --stream=$sfmt $itmpdir 2>${DATA}/innobackup.backup.log | socat -u stdio TCP:10.24.32.16:4444; RC=( ${PIPESTATUS[@]} ) (20190312 12:45:54.132) 2019-03-12 12:45:54 140262609999616 [Warning] Aborted connection 72 to db: 'unconnected' user: 'root' host: 'localhost' (Got an error reading communication packets) WSREP_SST: [ERROR] innobackupex finished with error: 1. Check /var/lib/mysql//innobackup.backup.log (20190312 12:45:54.208) WSREP_SST: [ERROR] Cleanup after exit with status:22 (20190312 12:45:54.210) WSREP_SST: [INFO] Cleaning up temporary directories (20190312 12:45:54.214) 2019-03-12 12:45:54 140255164364544 [ERROR] WSREP: Failed to read from: wsrep_sst_xtrabackup-v2 --role 'donor' --address '10.24.32.16:4444/xtrabackup_sst//1' --socket '/var/run/mysqld/mysqld.sock' --datadir '/var/lib/mysql/' --defaults-file '/etc/mysql/my.cnf' '' --gtid 'c286e09d-1e7e-11e9-8db5-367539f9aa5c:16202149' --gtid-domain-id '0' 2019-03-12 12:45:54 140255164364544 [ERROR] WSREP: Process completed with error: wsrep_sst_xtrabackup-v2 --role 'donor' --address '10.24.32.16:4444/xtrabackup_sst//1' --socket '/var/run/mysqld/mysqld.sock' --datadir '/var/lib/mysql/' --defaults-file '/etc/mysql/my.cnf' '' --gtid 'c286e09d-1e7e-11e9-8db5-367539f9aa5c:16202149' --gtid-domain-id '0': 22 (Invalid argument) 2019-03-12 12:45:54 140255164364544 [ERROR] WSREP: Command did not run: wsrep_sst_xtrabackup-v2 --role 'donor' --address '10.24.32.16:4444/xtrabackup_sst//1' --socket '/var/run/mysqld/mysqld.sock' --datadir '/var/lib/mysql/' --defaults-file '/etc/mysql/my.cnf' '' --gtid 'c286e09d-1e7e-11e9-8db5-367539f9aa5c:16202149' --gtid-domain-id '0' 2019-03-12 12:45:54 140260394657536 [Warning] WSREP: 0.0 (babylon5): State transfer to 1.0 (narn) failed: -22 (Invalid argument) 2019-03-12 12:45:54 140260394657536 [Note] WSREP: Shifting DONOR/DESYNCED -> JOINED (TO: 16202149)
Wait a moment, I may have found a contributing factor, POSSIBLY the cause...
...Nope. Just noticed that the node serving as donor had percona-xtrabackup-2.4.12 while the other two had ~2.4.13, but just updated that and it did not change the behavior. wsrep_sst_xtrabackup-v2 is still not working on a 10.2.22-r1 cluster. wsrep_xtrabackup_rsync continues to work.
(In reply to Phil Stracchino (Unix Ronin) from comment #4) > ...Nope. Just noticed that the node serving as donor had > percona-xtrabackup-2.4.12 while the other two had ~2.4.13, but just updated > that and it did not change the behavior. wsrep_sst_xtrabackup-v2 is still > not working on a 10.2.22-r1 cluster. wsrep_xtrabackup_rsync continues to > work. Does it work with wsrep_sst_mariabackup ? This is a xtrabackup replacement made specifically for MariaDB
I don't know, but I will try it. Of course I'm only running MariaDB in the first place because there is no maintained Percona XtraDB Cluster package for Gentoo and I have been unable to create one.
Hmm. I don't see an ebuild for mariabackup...
Oh, wait, it's included in the package. Never mind, I will try it.
And the answer is yes, wsrep_sst_mariabackup works. I wasn't aware it existed.
(In reply to Phil Stracchino (Unix Ronin) from comment #9) > And the answer is yes, wsrep_sst_mariabackup works. I wasn't aware it > existed. OK.. From the documentation [1], > Percona XtraBackup does not work with MariaDB 10.1 or greater if encryption > or compression is used, or when innodb_page_size is set to some value other > than 16K. It also does not work with MariaDB 10.2 or greater if > innodb_safe_truncate=ON is set. It also does not work with MariaDB 10.3 or > greater. For the cases where Percona XtraBackup is not supported, see > Mariabackup instead. It looks as if we should consider dropping XtraBackup as an SST or give a big warning in 10.2 and above since the incompatiblies are only growing. innodb_safe_truncate is ON by default in 10.2 (and forced in 10.3 and above) [1] https://mariadb.com/kb/en/meta/xtrabackup_warning/
(In reply to Brian Evans from comment #10) > (In reply to Phil Stracchino (Unix Ronin) from comment #9) > > And the answer is yes, wsrep_sst_mariabackup works. I wasn't aware it > > existed. > > OK.. From the documentation [1], > > > [...] It also does not work with MariaDB 10.2 or greater if > > innodb_safe_truncate=ON is set. [...] > innodb_safe_truncate is ON by default in 10.2 (and forced in 10.3 and above) AHA. Well THAT would most likely be the problem, then. > It looks as if we should consider dropping XtraBackup as an SST or give a > big warning in 10.2 and above since the incompatiblies are only growing. That sounds like a good move. BTW -- am I correct in assuming this means that dev-db/percona-xtrabackup is no longer needed (or even useful) at all with dev-db/mariadb >=10.2? Currently dev-db/mariadb still has dev-db/percona-xtrabackup as a dependency IF USE=sst-xtrabackup. Should USE=sst-xtrabackup be removed from 10.2 and later? I have considerable cause for concern about the growing scope of incompatibilities between MariaDB and MySQL. Whatever he intended, when Monty forked MariaDB he fractured the MySQL ecosystem, and I don't think he did anyone any favors by doing so.
Hmm. Interesting. Even if compiled WITHOUT USE=sst-xtrabackup, dev-db/mariadb still installs /usr/bin/wsrep_sst_xtrabackup and /usr/bin/wsrep_sst_xtrabackup-v2.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8865ff87d9240332171bd9b5da6a7af16fe57e62 commit 8865ff87d9240332171bd9b5da6a7af16fe57e62 Author: Brian Evans <grknight@gentoo.org> AuthorDate: 2019-03-12 22:41:38 +0000 Commit: Brian Evans <grknight@gentoo.org> CommitDate: 2019-03-12 22:42:39 +0000 dev-db/mariadb: Alert users to the deprecation of sst-xtrabackup sst-xtrabackup is broken by default in >=10.2.19 and incompatible in >=10.3 Issue ewarns for those on 10.2 to move to sst-mariabackup instead Closes: https://bugs.gentoo.org/677674 Package-Manager: Portage-2.3.62, Repoman-2.3.12 Signed-off-by: Brian Evans <grknight@gentoo.org> dev-db/mariadb/mariadb-10.2.22-r1.ebuild | 6 ++++++ 1 file changed, 6 insertions(+) Additionally, it has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f77e0ce5149a541c908e8e8950785f329f647238 commit f77e0ce5149a541c908e8e8950785f329f647238 Author: Brian Evans <grknight@gentoo.org> AuthorDate: 2019-03-12 22:32:16 +0000 Commit: Brian Evans <grknight@gentoo.org> CommitDate: 2019-03-12 22:42:38 +0000 profiles: package.use.mask - disable sst-xtrabackup from mariadb This is broken on 10.3 and higher as per upstream Bug: https://bugs.gentoo.org/show_bug.cgi?id=677674 Signed-off-by: Brian Evans <grknight@gentoo.org> profiles/base/package.use.mask | 5 +++++ 1 file changed, 5 insertions(+)
(In reply to comment #13) > https://gitweb.gentoo.org/repo/gentoo.git/commit/ > ?id=f77e0ce5149a541c908e8e8950785f329f647238 > > commit f77e0ce5149a541c908e8e8950785f329f647238 > Author: Brian Evans <grknight@gentoo.org> > AuthorDate: 2019-03-12 22:32:16 +0000 > Commit: Brian Evans <grknight@gentoo.org> > CommitDate: 2019-03-12 22:42:38 +0000 > > profiles: package.use.mask - disable sst-xtrabackup from mariadb > > This is broken on 10.3 and higher as per upstream > > Bug: https://bugs.gentoo.org/show_bug.cgi?id=677674 > Signed-off-by: Brian Evans <grknight@gentoo.org> > > profiles/base/package.use.mask | 5 +++++ This does not work, because this USE flag is unmasked in later profiles. # grep sst-xtrabackup profiles/**/package.use.mask profiles/arch/amd64/package.use.mask:>=dev-db/mariadb-10.1.0 -mroonga -sst-xtrabackup -galera profiles/arch/base/package.use.mask:>=dev-db/mariadb-10.1.0 mroonga sst-xtrabackup galera profiles/arch/x86/package.use.mask:>=dev-db/mariadb-10.1.0 -sst-xtrabackup -galera profiles/base/package.use.mask:>=dev-db/mariadb-10.3.0 sst-xtrabackup
(In reply to Phil Stracchino (Unix Ronin) from comment #12) > Hmm. Interesting. Even if compiled WITHOUT USE=sst-xtrabackup, > dev-db/mariadb still installs /usr/bin/wsrep_sst_xtrabackup and > /usr/bin/wsrep_sst_xtrabackup-v2. These are just the scripts by MariaDB to support SST, but if you don't configure wsrep_sst_method = xtrabackup(-v2), they are not used. The sst-xtrabackup flag just pull in the dependencies so you can actually use it.
(In reply to Phil Stracchino (Unix Ronin) from comment #11) > BTW -- am I correct in assuming this means that dev-db/percona-xtrabackup is > no longer needed (or even useful) at all with dev-db/mariadb >=10.2? > Currently dev-db/mariadb still has dev-db/percona-xtrabackup as a dependency > IF USE=sst-xtrabackup. Should USE=sst-xtrabackup be removed from 10.2 and > later? > > > I have considerable cause for concern about the growing scope of > incompatibilities between MariaDB and MySQL. Whatever he intended, when > Monty forked MariaDB he fractured the MySQL ecosystem, and I don't think he > did anyone any favors by doing so. Mariabackup is a fork of xtrabackup to support features only present in MariaDB like for example innodb page compression. If you don't use those features, you can use xtrabackup with MariaDB 10.2. But once you migrate to Mariabackup, you can remove the percona-xtrabackup(-bin) package, yes.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f5b77e77b2b050172c66999091c41b8b1fdf7065 commit f5b77e77b2b050172c66999091c41b8b1fdf7065 Author: Brian Evans <grknight@gentoo.org> AuthorDate: 2019-03-13 13:32:35 +0000 Commit: Brian Evans <grknight@gentoo.org> CommitDate: 2019-03-13 13:32:35 +0000 dev-db/mariadb: Drop sst-xtrabackup from 10.3 Closes: https://bugs.gentoo.org/677674 Package-Manager: Portage-2.3.62, Repoman-2.3.12 Signed-off-by: Brian Evans <grknight@gentoo.org> dev-db/mariadb/mariadb-10.3.13.ebuild | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-)
