Tag Info

New answers tagged

0

I got this error after a clean installation. Somehow i think something messed up the MariaDB data directory (/var/lib/mysql). The solution was to delete the content of /var/lib/mysql on all nodes and run mysql_install_db --user=mysql. Be aware that this will delete all your existing data.


0

Well this is quite simple. Due to the fact that you have SQL Server you have more solutions than you need. ;-) You can create a replication which will replicate the data records to many different nodes. If you just want one active mode which automatically fails over to anther node, you're able to make a mirror with a witness which runs in a high safety ...


1

Do you shut the system down overnight to back up? The reason I ask is that you may have cold caches in the morning (due to shutdown) which warm back up and start to function properly by 11:00. Does the resource utilisation on the DB server go down after 11:00? When you say "resources" - what, exactly, are you talking about? CPU, RAM or Disk? How is the ...


0

Another topology would be a 3-node Galera cluster, plus 2 ordinary readonly slaves hanging off each Galera node. Send non-critical-read requests to any of the 6 slaves; send writes to any of the 3 cluster nodes. The reason for failure to scale writes is that all writes must be written to all nodes. Row Based Replication (required by Galera) helps lighten ...


0

PXC and Galera Cluster do not write scale very well. I mentioned this in my answer to the old post Transaction speed benchmarks for mySQL v5.6 replication - seems very slow where I said the following: Please keep in mind that Percona XtraDB Cluster does not write scale very well to begin with. Note what the Documentation says under its drawbacks (Second ...



Top 50 recent answers are included