[
https://issues.apache.org/activemq/browse/AMQ-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44221#action_44221
]
Dmitry Tsigelnik commented on AMQ-1832:
---------------------------------------
I think your solution is bad. How can I stop Master? Stopping working master
means that my business process will crashed... What's the problem if it is just
a network problem, not server crashing? In this case slave must automaticaly
reconnect to master and replicate state, it mustn't shutdown.
Data replication must be independent from Command architecture... Propogating
commands to slave is bad architecture. In fact, absense of command means
absence of data replication.
> Pure Master/Slave to allow shutdownOnSlaveFailure to be configured on master
> ----------------------------------------------------------------------------
>
> Key: AMQ-1832
> URL: https://issues.apache.org/activemq/browse/AMQ-1832
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: ying
> Attachments: AMQ1832-596-1820Patch.txt
>
>
> It is related to AMQ-596 in terms that it is desirable that master and slave
> are in synch and when both are down, failover can direct the job to other
> pair of master/slave. So pure master/slave can be used for replication while
> a network of pair (master/slave) will provide a HA service.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
