activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <>
Subject [jira] [Resolved] (AMQ-3815) Hybrid Master Slave Architecture
Date Sat, 08 Sep 2012 09:58:07 GMT


Claus Ibsen resolved AMQ-3815.

       Resolution: Invalid
    Fix Version/s: 5.7.0
         Assignee: Claus Ibsen

Use the mailing list for asking questions like this.

> Hybrid Master Slave Architecture
> --------------------------------
>                 Key: AMQ-3815
>                 URL:
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 5.5.1
>         Environment: solaris, linux
>            Reporter: Bhanu
>            Assignee: Claus Ibsen
>             Fix For: 5.7.0
> 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
For more information on JIRA, see:

View raw message