Re: [Maria-discuss] MariaDB master-slave chained replication and parallelism

2021-08-06 Thread Kristian Nielsen
andrei.el...@pp.inet.fi writes: > And the above transition can be explained by > MDEV-24654 GTID event falsely marked transactional, its patch is under > review. Oh, yes, this bug sounds like it could result in what Jan described. It was not clear to me from the bug description exactly under what

Re: [Maria-discuss] MariaDB master-slave chained replication and parallelism

2021-08-06 Thread andrei . elkin
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, t

Re: [Maria-discuss] MariaDB master-slave chained replication and parallelism

2021-08-05 Thread Jan Křístek
We don't use read-only compressed MyISAM tables, but I found out, that by using PACK_KEYS I can save a significant amount of disk space. With some small data, the index size can be the same as the data file size, with PACK_KEYS we saved about 4/5 of the index volume (if I am right). On Thu, 5 Aug

Re: [Maria-discuss] MariaDB master-slave chained replication and parallelism

2021-08-05 Thread Gordan Bobic
InnoDB is faster even on a read-only workload now and has been for over a decade. One of very, very few cases for use of MyISAM is if you use compressed read-only MyISAM tables. On Thu, Aug 5, 2021 at 11:39 AM Jan Křístek wrote: > It's used as an archive of events and data. The data are written

Re: [Maria-discuss] MariaDB master-slave chained replication and parallelism

2021-08-05 Thread Jan Křístek
It's used as an archive of events and data. The data are written just once and then read multiple times. I think that the response times are limited by the disk speed and that indexing for lookups works in a similar way on both MyISAM and InnoDB. We were considering upgrading it to Aria storage en

Re: [Maria-discuss] MariaDB master-slave chained replication and parallelism

2021-08-05 Thread Gordan Bobic
I think you are going to have to bite the bullet on conversion to InnoDB sooner rather than later. The performance improvement you are going to see will likely be orders of magnitude. The longer you leave it, the more painful it is going to become. You could do it on a slave and then promote it, or

Re: [Maria-discuss] MariaDB master-slave chained replication and parallelism

2021-08-05 Thread Jan Křístek
Hi Kristian, Thank you for your answer. On Thu, 5 Aug 2021 at 09:44, Kristian Nielsen wrote: > > Interesting. Where do you see these counts? My guess is that these are > counting the "transactional" status flag on each GTID event in the binlog. > I see these counts almost at the end of 'mysql

Re: [Maria-discuss] MariaDB master-slave chained replication and parallelism

2021-08-05 Thread Kristian Nielsen
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, that the first slave in the chai

[Maria-discuss] MariaDB master-slave chained replication and parallelism

2021-08-04 Thread Jan Křístek
Hi, 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, that the first slave in the chain counts replicated statem