Added: incubator/activemq/site/MasterSlave URL: http://svn.apache.org/viewcvs/incubator/activemq/site/MasterSlave?rev=376314&view=auto ============================================================================== --- incubator/activemq/site/MasterSlave (added) +++ incubator/activemq/site/MasterSlave Thu Feb 9 07:12:56 2006 @@ -0,0 +1,286 @@ + + + + + + + + ActiveMQ - MasterSlave + + + + + + + + + + + + + + + + - +
+ + + + + + +
+

Overview

+ +

Community

+ +

Using ActiveMQ

+ +

Features

+ +

Connectivitiy

+ +

Utilities

+ +

External Tools

+ +

Related Projects

+ +

Support

+ +

Developers

+ +

Tools we use

+ +

Feeds

+ + + + + + + + + +
+
+
+ Site +
+ + + News +
+
+ +
+ + + + + +
+ MasterSlave + + +
+
+ + +
+
+

+ + + + + + + + + +
Apache ActiveMQ 4.0 Feature
+

The Master/Slave functionality is only available in the Apache ActiveMQ 4.0 m5 release and above

+
+

+

 

+

Introduction

+

Master/Slave is now the recommended way for providing high availabilty and fault tolerance for Apache ActiveMQ.
A Master/Slave configuration is ideal for a shared nothing, fully replicated toplogy.

+

How it works

+
    +
  • A slave of a master broker consumes all message states from the master - messages, acknowledgements and transactional states.
    Whilst a Slave is actively connected to the Master - it does not allow or start any network or transport connectors, it's sole purpose is to duplicate the state of the master.
  • +
+
    +
  • The master broker will only respond to a client when a message exchange has been successfully passed to the slave. For example, a commit
    in a clients transaction will not complete until the master and the slave have processed the commit.
  • +
+
    +
  • In the event the master fails (e.g. hardware failure) the slave has optionally two modes of operation
      +
    1. starts all it's network and transport connectors - allowing clients connected to the master to resume on the slave.
    2. +
    3. or can be configured to close down. In this mode, the slave is simply used to duplicate state for the master.
    4. +
    +
  • +
+
    +
  • clients should only use a failover transport for connecting to the master broker - e.g. failover://(tcp://masterhost:62001)
    The master informs the failover transport on the client the URI of the slave broker, so in the event of failure the client will automatically
    re-connect to the slave.
  • +
+

Configuring MasterSlave

+

A master broker doesn't need any special configuration - it's a normal broker until a slave broker attaches itself.
To identify a broker as a slave - there is just one property to set (see below) and an option - so configuration is nice and easy.

+

+ + + + + + + + + + + + + + + + + + +
Broker Property default Description
masterConnectorURI null URI to the master broker e.g. tcp://masterhost:62001
shutdownOnMasterFailure false if true, the slave will shut down if the master fails
+

+
+
+ +   +
+ + +
@@ -67,6 +70,8 @@
  • Building
  • Running a Broker
  • Examples
  • +
  • Web Samples
  • +
  • Hello World
  • Monitoring the Broker
  • Xml Configuration
  • Xml Reference
  • @@ -75,8 +80,7 @@
  • Configuring Transports
  • Embedded Brokers
  • Performance Testing
  • -
  • Web Samples
  • -
  • Hello World
  • +
  • Command Line Tools Reference
  • Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy

    Features

    Connectivitiy