Hi all, Sajini and I tested the following in a 3 node MB cluster where a mixture of topics, queues and shared topics were used:
An MB node in the cluster was killed when the clients were in the middle of publishing and subscriber. All the publishers and subscribers are connected to the node that is going to get killed. Following are the scenarios that were verified in this test: - Kill a normal node. All the publishers and subscribers fail-over successfully. - The coordinator selection happens successfully. Also, the publishers and subscribers fail-over successfully. - First kill the coordinator node, then kill the newly appointed coordinator node. Fail-over happens successfully. Did not encounter issues: Thus, +1 Stable-go ahead and release Thank you On Sat, Nov 7, 2015 at 3:28 AM, Akalanka Pagoda Arachchi <[email protected] > wrote: > Hi Devs, > > This is the second release candidate of WSO2 Message Broker 3.0.0. > > This release fixes the following issues: > https://wso2.org/jira/issues/?filter=12508 > > <https://wso2.org/jira/issues/?filter=12422> > Please download, test and vote. > > Source & binary distribution files: > https://github.com/wso2/product-mb/releases/tag/v3.0.0-RC2 > > Maven staging repo: > http://maven.wso2.org/nexus/content/repositories/orgwso2mb-118/ > > The tag to be voted upon: > https://github.com/wso2/product-mb/tree/v3.0.0-RC2 > > > [+] Stable - go ahead and release > [-] Broken - do not release (explain why) > > Thanks and Regards, > MB Team. > > -- > *Darshana Akalanka Pagoda Arachchi,* > *Software Engineer* > *078-4721791* > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Sasikala Kottegoda *Software Engineer* WSO2 Inc., http://wso2.com/ lean. enterprise. middleware Mobile: +94 774835928/712792401
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
