Rotating General Query & Slow Logs - 0 views
Generic Log Parser - 0 views
Creative Programming mysql - 0 views
Debian HA MySQL Servers with Heartbeat - 0 views
Oracle 10g on Debian - 0 views
MySQL Swiss Army Knife - 0 views
Tuning MySQL Server to boost performance - 0 views
MySQL Replication vs DRBD Battles - 0 views
-
The side question about it is of course the fact you have to be picky about storage engines you’re using - DRBD does not work with MyISAM (check required) so you need to have processes to ensure your application does not uses this storage engine which may be hard to guaranty in many environments when development has too much autonomy
-
The state of High Availability Solutions for MySQL these days is - you can’t have it all. There is no OpenSource solution out where which would offer you full redundancy use of both nodes at least for reads no transaction loss and automated fail over. Whenever you’re using MySQL Cluster, DRBD or MySQL Replication you have to have some compromises.
DRBD and MySQL: Just Say Yes - 0 views
-
Now while I concede that some of the points Eric had made were valid at the time (and some continue to be), a lot of what he said then is now outdated, superseded, or has been addressed in DRBD releases made months ago
Performance and High Availability » Blog Archive » Testing InnoDB and MySQL 5... - 0 views
-
Testing InnoDB and MySQL 5.1 performance in real workload conditions
Architectures distribuées - 0 views
Eric Bergen » DRBD in the real world - 0 views
-
Protocol C is really the only one that gives any extra data security over binary log replication so it’s the one I’m focusing my attention on. If an issue on one master causes problems on another then the benefit of having redundant masters is effectively lost.
-
ith DRBD the second master lagging behind because of a degraded raid, network issue, operator error, name your poison causes issues on the primary master because MySQL has to wait for writes to be synced to disk on _both_ machines before continuing
-
When DRBD, the operating system, or hardware crashes it crashes hard. Any corruption on the primary master during a nasty failure gets happily propagated over DRBD. Binary log replication executes queries on the slave the same way they were executed on the master giving a better chance of a tickled kernel/filesystem bug on one master won’t be ticked on the other master. The primary master will simply crash leaving the secondary master in a consistent state waiting to take on live traffic.
« First
‹ Previous
261 - 280 of 281
Next ›
Showing 20▼ items per page