activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Tsigelnik (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (AMQ-1832) Pure Master/Slave to allow shutdownOnSlaveFailure to be configured on master
Date Mon, 14 Jul 2008 19:58:00 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=44280#action_44280
] 

tsigelnik edited comment on AMQ-1832 at 7/14/08 12:57 PM:
-----------------------------------------------------------------

No. I want to use the same configuration as yours: Datacenter1 (Master A / Slave B) <=>
Datacenter2(Master B / Slave A)
But if you shutdown master which loose connection to slave that means some messages which
is contained by current master  won't relocated to another master in time.

I think better solution is full replication of master's sate  at the moment of attaching slave
to master. Also slave musn't shutdown on loosing connection to master, becasue it's possible
network problem. Slave must retry to reconnect to master fo example in current of hour and
then shutdown.

It's too hard to our operations team restart ActiveMQ server each time when network is down.
Unfortunely, network problems happen very quikly. Sometimes electricity is down in all datacenter...


I think master must keep working when slave is disconnected. I derrived slave BrokerService
and added reconnection logic. Problem for me is master state is not fully replicated on attaching
slave. 
I think, shutdowning master is bad solution



      was (Author: tsigelnik):
    No. I want to use the same configuration as yours: Datacenter1 (Master A / Slave B) <=>
Datacenter2(Master B / Slave A)
But if you shutdown master which loose connection to slave that means some messages which
is contained by current master  won't relocated to another master in time.

I think better solution is full replication of master's sate  at the moment of attaching slave
to master. Also slave musn't shutdown on loosing connection to master, becasue it's possible
network solution. Slave must retry to reconnect to master fo example in current of hour and
then shutdown.

It's too hard to our operations team restart ActiveMQ server each time when network is down.
Unfortunely, network problems happen very quikly. Sometimes electricity is down in all datacenter...


I think master must keep working when slave is disconnected. I derrived slave BrokerService
and added reconnection logic. Problem for me is master state is not fully replicated on attaching
slave. 
I think, shutdowning master is bad solution


  
> 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.


Mime
View raw message