Re: [RDD] InnoDB Support
On Dec 14, 2020, at 09:41, t...@tomdawson.co.uk wrote: > In the changelog, I see: "2.15.0 (2016-07-29) Bug fix: complete support for > the MySQL/MariaDB InnoDB database engine" - however after looking at the > engine in use on my Rivendell 3.5.0 test box all tables are still MyISAM. > > Is this just a case of changing the running engine myself, or are there plans > for Paravel to push out some changes to move to InnoDB? And if I do change to > InnoDB will any future schema changes break because of this? > > The reason I ask is that I'm looking to try running the database on MariaDB > with Galera Cluster as a potential option for cross-WAN database access. It’s been supported for some time. It’s mostly a matter of setting ‘Engine=InnoDB’ in the ‘[mySQL]’ section of ‘/etc/rd.conf’. You will have to convert any prior existing tables by hand. That said, the default is still MyISAM, mostly because the Aman clustering system requires it. Cheers! |-| | Frederick F. Gleason, Jr. | Chief Developer | | | Paravel Systems | |-| | A room without books is like a body without a soul. | | | | -- Cicero | |-|___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
Re: [RDD] InnoDB Support
Hi Tom, On 12/14/20 8:41 AM, you wrote: > > Hi all, > > Just wondering what the state of play is for InnoDB? > > In the changelog, I see: "2.15.0 (2016-07-29) Bug fix: complete support > for the MySQL/MariaDB InnoDB database engine" - however after looking at > the engine in use on my Rivendell 3.5.0 test box all tables are still > MyISAM. > > Is this just a case of changing the running engine myself, or are there > plans for Paravel to push out some changes to move to InnoDB? And if I > do change to InnoDB will any future schema changes break because of > this? > > The reason I ask is that I'm looking to try running the database on > MariaDB with Galera Cluster as a potential option for cross-WAN database > access. > > Many thanks, > Tom > Disclaimer: I am not a database expert or an educated DBA. I can't say what the formal plans are regarding switching the database engine, but I *can* tell you that I have successfully converted a few Rivendell databases to InnoDB (on MariaDB server). I have also implemented a multi-node WAN cluster using Galera. It's a lot more work (initial setup and on-going maintenance) than I had expected, but it has been worth the effort for this specific use case. I have not figured out a way to consistently maintain a (Galera) quorum when one site loses Internet connectivity for an extended period. Usually things work and the cluster recovers from the outage, but there are still times when the cluster goes "split brain" and I have to initialize it from scratch. Would love to continue this conversation off list (or on list) if you're interested. ~David Klann Broadcast Tool & Die broadcasttool.com / btd.support ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
[RDD] InnoDB Support
Hi all, Just wondering what the state of play is for InnoDB? In the changelog, I see: "2.15.0 (2016-07-29) Bug fix: complete support for the MySQL/MariaDB InnoDB database engine" - however after looking at the engine in use on my Rivendell 3.5.0 test box all tables are still MyISAM. Is this just a case of changing the running engine myself, or are there plans for Paravel to push out some changes to move to InnoDB? And if I do change to InnoDB will any future schema changes break because of this? The reason I ask is that I'm looking to try running the database on MariaDB with Galera Cluster as a potential option for cross-WAN database access. Many thanks, Tom ___ Rivendell-dev mailing list Rivendell-dev@lists.rivendellaudio.org http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
