Howdy Ragul,
> Hi Andrei,
>
> Do we have any procedures to reproduce the issue MDEV-30780?
Thanks for posting the gdb bt:s. They rule out 30780 yet not
suggesting to me enough about the hang reason. This is something new to
me and does deserve filing an MDEV ticket.
Still I'd defer that until
Howyd Ragul,
> Hi team,
>
> I have facing a replication issue in my DB setup where we have a master-slave
> server and replication is ON between
> the servers.
>
> Environment: MariaDB 10.6.11
> DB size: approx. 1TB
>
> While taking mariabackup, at the stage of preparing backup I see some
>
But I hope I am not terminally late :-).
There are two projects that I think are of interest to the public:
MDEV-21117 recovery for semisync
by Andrei Elkin and Sujatha Sivakumar;
This work is already done for 10.6
MDEV-11675 Lag Free Alter replication
by Sachin Satja and Andrei Elkin
This w
Jan, Kristian, howdy.
> Jan Křístek writes:
>
>> We have a MariaDB 10.3 replication setup with one master and a few chained
>> slaves (each has log_slave_updates switched on). Master uses mainly MyISAM
>> tables, slaves have about 10 or 40 threads for parallel replication.
>>
>> Interesting is,
Dajka Tamás writes:
> Hi All,
>
> I’m facing a weird error. We’re migrating our old 10.1 multi-master setup to
> a new 10.3 cluster
> (everything is running on Debian). New-node01 is connected as a slave to the
> old cluster’s master.
>
> When I tried to set up the replication between the 2
Thomas writes:
> Hello,
>
> I changed to "slave-parallel-mode = conservative" from "optimistic" and now
> it is applying all the updates since friday.
> Hope this was the problemI will write again when it finishes if all is ok.
>
> Many thanks for your help.
And you too! Now having the
Thomas writes:
> Hello,
Howdy, Tomas.
> we have upgraded our MySQL Master/Slave server vom 10.1.24 to 10.1.48
> on 25.01. Backups worked as usual, but since friday (29.01.) our
> backups do not work anymore. I have seen that entering a 'stop slave;'
> on mysql cli hangs forever, while in the
Martin, howdy.
> Hi,
>
> I've got a bit of a different question regarding MariaDB replication.
>
> But first, let me say that I'm familiar with both master-master and
> master-slave replication.
>
> What I'm after advice on is how to replicate tables from a number of single
> host instances of
>
> Also I did make a dump of just the table in question and nothing
> changed in my results. So I did
> mysqldump -u username -pPassword -h remote_hosts my_remote_database
> my_table > table_dump.sql
>
That's better take for analysis. Could you bisect table_dump.sql INSERT's
row list to find out
Elliot, howdy.
Thanks for narrating it pretty verbose!
I can only suggest to trace or bisect the 600 rows insertion to catch where it
fails.
Cheers,
Andrei
> H Andrei,
>
> Thanks for the reply. To answer your question when I import the my_dump.sql
> (yes it does contain
> all 600 rows in
> When I use mysqldump to backup a MySQL 5.7.8 database then import that
> database into a MariaDB
> 10.4.8 database, at least one (maybe more) of the imported tables is
> missing rows. This is a
> WordPress database and the table in question is the wp_options table. I'm
> only
Hello there, Bapt.
> Hello,
>
> On Ubuntu 19.04, which uses packages mariadb-server 10.3.17 and
> mysql-server 5.7.27, I noticed that if I wanted to switch from MySQL to
> MariaDB, the database is corrupted and there is a complete data loss
> even if I switch back to MySQL.
> I noticed that if
Hello.
> mari...@biblestuph.com writes:
>
>> I have four servers all running 10.3 as follows:
>>
>>A <=> B => C => D
>
>> and C is a master to D. In addition to their actual replicating DBs,
>> all four servers also have a "norep" DB that is used to create
>> temporary tables for local report
Hello.
> Nope, all three were MyISAM.
>
> After I sorted out the issue with all of the session's statements
> becoming RBL until I dropped the temp tables, I was left with two
> statements that were still giving me trouble. One was the one below,
> the other another statement against t1.
>
> The
Benoit, hello.
> Hi,
>
> Yes we are currently using mixed replication, we switched from statement two
> years ago.
>
> I had read mixed return about row based replication with some queries, so
> mixed looked like a good
> compromise.
> Reading current mysql (8.0) it look like RBR is the defaut
Hello, everybody.
Let me offer a bunch of ideas for further improvements in replication,
and the parallel one specifically.
Your comments, thoughts and critical notes are most welcome!
Thank you for your time.
Andrei
Slave balanced parallel applier
There are
Kristian,
> andrei.el...@pp.inet.fi writes:
>
>> Mike,
>>
>>> Hello,
>>>
>>> I realize that in general replication from a newer master to an older
>>> slave is typically not recommended. This said, does anyone have an
>>> experience replicating from MariaDB 10.2 to MySQL 5.6?
>>
>> A problem
Mike,
> Hello,
>
> I realize that in general replication from a newer master to an older
> slave is typically not recommended. This said, does anyone have an
> experience replicating from MariaDB 10.2 to MySQL 5.6?
A problem that is evident at once is 10.2 GTID events can not be handled
by 5.6.
18 matches
Mail list logo
