> -----Original Message----- > From: [email protected] [mailto:u2-users- > [email protected]] On Behalf Of Baker Hughes > Sent: Monday, July 26, 2010 12:14 PM > To: 'U2 Users List' > Subject: Re: [U2] 24 X 7 MV systems > > Glen, > > Thank you for the good observations, and suggestion to ping Ross, which I > will do. It is the MV db paradigm which in this case is hampering us, > which drives the solution to either the OS level or some middle ware > solution. Pausing the db to flush memory is what keeps us just seconds > from a full solution. > > Thank you. > -Baker
Baker, Triggers may be the only sane option to tie into all of the services that modify the data. If you only had WRITE() to deal with then it'd be a no-brainer to just replace it with a custom write control and replication output routine. I know a small amount about U2, so I won't make any guesses on what's possible. As far as network failover, just rely on a local DNS service. You can use one local domain name and assign multiple A records. The resolver on the client machine should do the heavy lifting and resolve to the first IP that works. Just make sure that the failed node drops off of the network or you could run into latency issue with the resolver. Regards, ---------------------------------------- Glen Batchelor IT Director/CIO/CTO All-Spec Industries phone: (910) 332-0424 fax: (910) 763-5664 E-mail: [email protected] Web: http://www.all-spec.com Blog: http://blog.all-spec.com ---------------------------------------- _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
