On Thursday, September 2, 2010, Hodchenkov, Paul <[email protected]> wrote: > > > > > > > > > > > > > > It seems that one of the possible solution is to use JDBC base > configuration model and specify database cluster url in dbconfig. So registry > database will be accessible even when registry node is down. Please comment > this solution.
This us in sync with my understanding > > Is it possible to achieve failover in Atom based configuration > model? Not really I think, as it is a simple REST based model. JDBC based model should be more suited for this. > > Thx. > > > > > > From: Krishantha > Samaraweera [mailto:[email protected]] > Sent: Wednesday, September 01, 2010 3:18 PM > To: [email protected] > Cc: Hodchenkov, Paul > Subject: Fwd: [Registry-user] Failover of registry > > > > > > Forwarding to carbon-dev for > wider community (ESB) attention. > > Thanks, > Krishantha. > > > > ---------- Forwarded message > ---------- > From: Hodchenkov, Paul <[email protected]> > Date: Wed, Sep 1, 2010 at 3:35 PM > Subject: [Registry-user] Failover of registry > To: "[email protected]" > <[email protected]> > > > > > > > > Hi! > > > > I have read nice article > http://wso2.org/library/tutorials/2010/04/sharing-registry-space-across-multiple-product-instances > > The problem is that all nodes of esb cluster refers one registry > instance (Atom based configuration). Is it possible to setup multiply registry > instances for failover purposes? So if one registry node dies esb should use > the second one. > > > > Thx. > > > > > > > _______________________________________________ > Registry-user mailing list > [email protected] > https://wso2.org/cgi-bin/mailman/listinfo/registry-user > > > > > > > > > > > _______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
