[mv] failover setup for minivend

[cfm@maine.com]

******    message to minivend-users from cfm@maine.com     ******


Re failover setups for minivend

How are people configuring minivend for failover and high availability?

We're not seeing any issues with minivend itself, but we are running into
issues with our overall system.  I understand mySQL is working with RH 
to build in some sort of redundancy/replication but that is not here 
today.  Still, if the reason our db server goes down is operator 
failure (often me) then it's not clear how much that will help.  Using a 
staging mySQL server as well as a staging site for minivend might help some.

Our implementation currently is one primary big mySQL server with two
hot spares serving 4 active catalog machines and a development machine.  
We can bring the **active** mySQL server up and down with ipalias.  
Then we have to restart all our hammered minivend daemons.  That's 
less than satisfactory and not automatic.

What solutions are others using for this?  I've been thinking of keeping
a couple slave/read-only db servers and a separate master/write-only server.
The writes are always single table INSERT or UPDATE and relatively very
infrequent compared to the SELECTs which might be multi-db-multi-table 
JOINs and do sometimes jam the machine, usually during backups; there would
be no reason to back up the slaves, either.

Ideas?

cfm

-- 

Christopher F. Miller, Publisher                             cfm@maine.com
MaineStreet Communications, Inc         208 Portland Road, Gray, ME  04039
1.207.657.5078                                       http://www.maine.com/
Database publishing, e-commerce, office/internet integration, Debian linux.
-
To unsubscribe from the list, DO NOT REPLY to this message.  Instead, send
email with 'UNSUBSCRIBE minivend-users' in the body to Majordomo@minivend.com.
Archive of past messages: http://www.minivend.com/minivend/minivend-list