With static configuration, are you using the ‘masterslave’ transport prefix to specify the brokers in each of the leveDB replication cluster? I am getting errors using that. If I just use the ‘static’ transport prefix, it works, but I do get exceptions in the brokers. I am using the latest distribution (5.11-1) running on Mac, and I am seeing brokers been shutdown by itself with the replication cluster just sitting idle, doing nothing. This is with a small cluster of 3 brokers talking to a zookeeper running on the same box.
Do you have a sample activemq.xml configuration file you could share for your 3 x 3 cluster? I am trying to do the same, with everything running on my Mac initially. Thanks. Kevin From: "James A. Robinson-2 [via ActiveMQ]" <ml-node+s2283324n4694084...@n4.nabble.com<mailto:ml-node+s2283324n4694084...@n4.nabble.com>> Date: Monday, March 30, 2015 at 2:43 PM To: SNEI <kevin...@am.sony.com<mailto:kevin...@am.sony.com>> Subject: Re: Creating a Network of Replicated LevelDB broker clusters On Mon, Mar 30, 2015 at 2:09 PM, wonderkind <[hidden email]</user/SendEmail.jtp?type=node&node=4694084&i=0>> wrote: > How big is your network? Do you see any significant degradation with a > network of replicated levelDB brokers? I haven't started stress testing the configuration yet, the current plan is to have network two clusters of three. So six machines in all, only two active as the master at a time. > [ksu] How are you planning on discover the brokers? Via multi-cast > auto-discovery, or by specifying URLs statically? The later gets harder to > maintain as the the fabric’s membership grows. However, I am not sure if > there is any timing issue associated with the auto-discovery of masters, and > the auto-discvoery of brokers for the network. I don't see any reason why auto-discovery wouldn't work if you wanted to go that route. From the rest of the codes perspective there's one active broker per cluster, so I would think it would work just like networking stand-alone brokers. I'm not using auto-discovery myself, I'm planning on following naming conventions and having my cfengine system maintain the configuration, building a complete graph of the network. I've no idea how well, or poorly, that will work. You can see some of my configuration details by looking at a previous email I sent to the list: http://mail-archives.apache.org/mod_mbox/activemq-users/201503.mbox/%3CCAPd04b7106shHXUR+1VUddBmPUH+=mp414xOxnNpEuOuKwfo5g@...%3E<http://mail-archives.apache.org/mod_mbox/activemq-users/201503.mbox/%3CCAPd04b7106shHXUR+1VUddBmPUH+=mp414xoxnnpeuoukwf...@mail.gmail.com%3E> > [ksu] Could you share the patch? Which version of ActiveMQ are you using? The patch is listed in the ticket. One of the maintainers did respond to the ticket, indicating he was going to look it over and incorporate it if it passed muster. Jim ________________________________ If you reply to this email, your message will be added to the discussion below: http://activemq.2283324.n4.nabble.com/Creating-a-Network-of-Replicated-LevelDB-broker-clusters-tp4693979p4694084.html To unsubscribe from Creating a Network of Replicated LevelDB broker clusters, click here<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=4693979&code=a2V2aW4uc3VAYW0uc29ueS5jb218NDY5Mzk3OXw5MzA0MDE1ODU=>. NAML<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> -- View this message in context: http://activemq.2283324.n4.nabble.com/Creating-a-Network-of-Replicated-LevelDB-broker-clusters-tp4693979p4694091.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
