RE: Replication question...

-----Original Message----- From: owner-informix-list@iiug.org [mailto:owner-informix-list@iiug.org] On Behalf Of mosserp@wellsfargo.com Sent: 19 April 2005 11:42 PM To: informix-list@iiug.org Cc: mpruet@comcast.net Subject: RE: Replication question... > > > > --- Madison Pruet <mpruet@comcast.net> wrote: > > > Just a quick question. > > > > > > What would be some really cool things for us to > add > > > to IDS replication? > > > > > > > > > > > > >Madison, > >(Note: All of the following is in the context of HDR) > >Cool features are OK (multiple secondarys strikes me as a feature that >would be useful in several situations), but I think that what would >**REALLY** be cool is to make some coding / design changes to make HDR >more "bullet-proof". > >We ran into a bad situation last year / earlier this year that was very >detrimental to production: if a big report / query is running on the >secondary, consuming a lot of cpu, memory, and/or disk space, then the >primary can "hang" while trying to replicate to the secondary; it comes >.in the form of a very long checkpoint on the primary. Our workaround on >this is to not allow any big queries or reports to be run on the >secondary during peak txn traffic times. :-( > >We also ran into another problem this last weekend: After a disconnect >between primary / secondary, just after they got re-connected and were >starting the handshake process, the secondary went back down again. >Normally, this is not a problem, as the primary just gets another "DR: >Cannot connect to secondary server" and everything is OK until the >secondary once again becomes available. This time, tho, when the second >disconnect happened, the primary hung (so much so that I had to do a >kill -9 to bounce it -- Yuck!!). > >These are just a couple of examples of some "holes" in HDR. By and >large, I think that HDR is GREAT!! But when we run into situations like >the above, it only encourages those naysayers that keep insisting, "See, >we need to get off of Informix, and switch to another DBMS." [snip] I totally second this one - had similar issues on an HDR system on my site, where the network kept crashing the secondary, and each time I had to rebuild the secondary from scratch. sending to informix-list