digitalpoint
Well-known member
Support is offered over here: https://forums.digitalpoint.com/forums/support-feedback.3/
If my master server is using mariadb then my slave server must be using mariadb also?Allows for SQL read scalability.
You probably could use different forks/versions, but not sure why you would want to. Probably would want to check the documentation of whatever you are using to make sure... It's just normal MySQL replication that's used.If my master server is using mariadb then my slave server must be using mariadb also?
Or any mysql distru will do?
Like percona.
Nah... if people want to change their master server, it really should be handled at the server level, not the application level.Interesting.....
Have you considered implementing a system to disallow write actions on the forums when the master goes down?
That way you can have a truly redundant XenForo setup.
Won't every node being write capable lead to a tonne of race conditions, similar to why you need to stick requests using this addon?Nah... if people want to change their master server, it really should be handled at the server level, not the application level.
Also, tossing the system into read-only mode definitely is not a redundant setup.
If you want a truly redundant setup, you would be using something like MySQL Cluster (every node is fully write capable):
MySQL Cluster is actually what I use now for my site.
Nope, MySQL Cluster is designed to do be fully write capable on all nodes (with full ACID compliance).Won't every node being write capable lead to a tonne of race conditions, similar to why you need to stick requests using this addon?
There is a SQL node on every web server, so the MySQL IP/hostname is just "localhost". If there's a PHP fatal error of any sort (including being unable to connect to the DB server), Nginx routes around it and just automatically tries again on a different PHP-FPM server.EDIT: Also, how are you managing XenForo connecting to this cluster? HAProxy?
Nope, MySQL Cluster is designed to do be fully write capable on all nodes (with full ACID compliance). There is a SQL node on every web server, so the MySQL IP/hostname is just "localhost". If there's a PHP fatal error of any sort (including being unable to connect to the DB server), Nginx routes around it and just automatically tries again on a different PHP-FPM server.
I must then ask how you personally handle the data and internal_data directories.Nope, MySQL Cluster is designed to do be fully write capable on all nodes (with full ACID compliance). There is a SQL node on every web server, so the MySQL IP/hostname is just "localhost". If there's a PHP fatal error of any sort (including being unable to connect to the DB server), Nginx routes around it and just automatically tries again on a different PHP-FPM server.
Yep... just hasn't needed anything lately... still working fine with the latest versions of XenForo.Is this still being maintained?
Yep... hasn't been updated recently because nothing is broken and there really isn't much to add feature-wise.I'm interested in this. Still good to go?
We use essential cookies to make this site work, and optional cookies to enhance your experience.