[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] [Commented] (AMQ-3815) Hybrid Master Slave Architecture
From:       "Bhanu (JIRA)" <jira () apache ! org>
Date:       2012-04-26 11:43:18
Message-ID: 1416423549.4859.1335440598330.JavaMail.tomcat () hel ! zones ! apache ! org
[Download RAW message or body]


    [ https://issues.apache.org/jira/browse/AMQ-3815?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13262534#comment-13262534 \
] 

Bhanu commented on AMQ-3815:
----------------------------

Hello, Any updates here please !
                
> Hybrid Master Slave Architecture
> --------------------------------
> 
> Key: AMQ-3815
> URL: https://issues.apache.org/jira/browse/AMQ-3815
> Project: ActiveMQ
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 5.5.1
> Environment: solaris, linux
> Reporter: Bhanu
> 
> Hi,
> Can we have a Hybrid Master Slave Architecture where in we can merge the \
> functionalities of pure master slave and shared file system master slave. \
> Basically, we have a disaster recovery requirement wherein we want to \
> simulataneously run three brokers. A master broker will serve all the client \
> requests, a slave broker at the same site on a different host will try to acquire \
> the lock on kahadb(a typical slave). And we need a third broker to run at a \
> *different site* which should fully replicate the state of the current master. This \
> slave host should only be started when both the master and first slave are down. \
> Can we do it with the current ActiveMQ transports/configurations or this will need \
> enhancements. Please let me know if you have any queries regarding this.
> Thanks,
> Bhanu

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: \
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more \
information on JIRA, see: http://www.atlassian.com/software/jira

        


[prev in list] [next in list] [prev in thread] [next in thread]