[
https://issues.apache.org/jira/browse/AMQ-7506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Himanshu Mishra updated AMQ-7506:
---------------------------------
Description:
Hi,
I am using Activemq 5.15.4 and building an application which needs Activemq
highly available. As per the link given below, it is clear that if I choose
master/slave topology it will give me high availability
[https://activemq.apache.org/clustering.html]
The problem with this topology is, I will have to use a shared file system for
data folder of KahaDB. In case the shared file system fails, high availability
of Activemq goes on toss meaning there is no actual replication of the messages
taking place.
On the contrary, the link I have shared, is confirming that
"_The idea behind [MasterSlave|https://activemq.apache.org/masterslave] is
that messages are replicated to a slave broker so that even if you have a
catastrophic hardware failure of the master’s machine, file system or data
centre, you get immediate failover to the slave with no message loss._"
Please help me understand if Activemq really supports high availability mode
with required replications.
Thanks in advance!!!
Regards,
Himanshu Mishra
was:
Hi,
I am using Activemq 5.15.4 and building an application which needs Activemq
highly available. As per the link given below, it is clear that if I choose
master/slave topology it will give me high availability
[https://activemq.apache.org/clustering.html]
The problem with this topology is, I will have to use a shared file system for
data folder of KahaDB. In case the shared file system fails, high availability
of Activemq goes on toss meaning there is no actual replication of the messages
taking place.
On the contrary, the link I have shared, is confirming that
"_The idea behind [MasterSlave|https://activemq.apache.org/masterslave] is that
messages are replicated to a slave broker so that even if you have a
catastrophic hardware failure of the master’s machine, file system or data
centre, you get immediate failover to the slave with no message loss._"
Please help me understand if Activemq really supports high availability mode
with required replications.
Regards,
Himanshu Mishra
> Activemq - High availability when shared file system fails
> ----------------------------------------------------------
>
> Key: AMQ-7506
> URL: https://issues.apache.org/jira/browse/AMQ-7506
> Project: ActiveMQ
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 5.15.4
> Reporter: Himanshu Mishra
> Priority: Major
>
> Hi,
>
> I am using Activemq 5.15.4 and building an application which needs Activemq
> highly available. As per the link given below, it is clear that if I choose
> master/slave topology it will give me high availability
> [https://activemq.apache.org/clustering.html]
>
> The problem with this topology is, I will have to use a shared file system
> for data folder of KahaDB. In case the shared file system fails, high
> availability of Activemq goes on toss meaning there is no actual replication
> of the messages taking place.
>
> On the contrary, the link I have shared, is confirming that
> "_The idea behind [MasterSlave|https://activemq.apache.org/masterslave] is
> that messages are replicated to a slave broker so that even if you have a
> catastrophic hardware failure of the master’s machine, file system or data
> centre, you get immediate failover to the slave with no message loss._"
>
> Please help me understand if Activemq really supports high availability mode
> with required replications.
> Thanks in advance!!!
>
> Regards,
> Himanshu Mishra
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
