local-infile is both a client and a server flag - both must be enabled
or you'll get an error. mysql --local-infile=1 only enables the
client support for this feature. Your MariaDB server likely has this
disabled - perhaps as a security concern.
I would inspect your my.cnf and update the value if
Per the MySQL documentation, it is noted that replicate-*-table
options do only apply to tables, and replicate-*-db options are
suggested to filter stored procedures, functions and events. I
imagine that applies similarly to MariaDB.
The various *-db filters can be problematic[1], but perhaps wil
This looks curiously similar to this xtrabackup bug:
https://bugs.launchpad.net/percona-xtrabackup/+bug/1552416
Are you defining a datadir explicitly in your config? You might check
if it's being picked up right in "xtrabackup --help | grep ^datadir"
output.
~Andrew
On Fri, May 6, 2016 at 9:5
I don't think that this problem relates to wsrep_gtid_mode. That just
forces a particular gtid_domain_id for Galera transactions if I
understand right but I suspect it doesn't solve this case.
xtrabackup-v2 attempts to blow away all the existing binary logs on
the joiner during SST and attempts t
13, 2016 at 11:50 PM, Igor Mazur wrote:
> Sorry, I've forgotten to say that I use xtrabackup.
>
> 2016-04-14 2:04 GMT+03:00 Andrew Garner :
>>
>> What SST method are you using? Based on this I expect you are using rsync.
>>
>> I imagine someone knows more detaile
What SST method are you using? Based on this I expect you are using rsync.
I imagine someone knows more detailed answers here, but from my understanding:
Internally the bin/wsrep_sst_rsync script indicates it needs "flush
tables" to the server and the server runs this "sst_flush_tables()"
functio
6 matches
Mail list logo
