|
On Tue, 2003-11-04 at 23:11, John Barrett wrote:
> nfs directory naming has not been an issue for me in the least -- I always
> mount nfs volumes as /nfs[n] with subdirs in each volume for specific
> data -- then symlink from where the data should be to the nfs volume -- same
> thing you will have to do with coda -- in either case the key is planning
> your nfs/coda setup in advance so that you dont have issues with directory
> layouts, by keeping the mountpoints and symlinks consistent across all the
> machines.
>
> based on my current understanding of the art with mysql, your best bet is to
> use mysql replication and have a failover server used primarily for read
> only until the read/write server fails (if you need additional query
> capacity) (ldirectord solution), or do strict failover (heartbeat solution),
> only one server active at a time, both writing replication logs, with the
> inactive reading the logs from the active whenever both machines are up
> (some jumping through hoops needed to get mysql to startup both ways --
> possibly different my.cnf files based on which server is active)
...deleted...
I'm sorry for this late answer. Frankly, I need quite enough time to
digest your posting, John :) I never tried failover yet. That's why. I'm
sorry. So far, all I know is just building LVS-NAT, for single and multi
ports. (There's still many things to catch up then. Yeah! Keep
fighting!)
Anyway, thank you for your suggestion, John. I'll refer it back again,
whenever I figure out those 'advanced' terms :)
Regards,
Ariyo
p.s.
Yes, we're too far off topic, John. Let's stop it now :)
|
