A primary objective of MHA is automating master failover and slave promotion within short (usually 10-30 seconds) downtime, without suffering from replication consistency problems, without spending money for lots of new servers, without performance penalty, without complexity (easy-to-install), and without changing existing deployments. MHA also provides a way for scheduled online master switch: changing currently running master to a new master safely, within a few seconds (normally 0.5-2 seconds) of downtime (blocking writes only).
Group items matching
in title, tags, annotations or urlYoshinori Matsunobu's blog: Announcing MySQL-MHA: "MySQL Master High Availability manager and tools" - 2 views
Shop2market | Sell more, spend less - 1 views
-
Manage All You Online Campaigns With Shop2market
‹ Previous
21 - 28 of 28
Showing 20▼ items per page