Return-Path: X-Original-To: apmail-qpid-commits-archive@www.apache.org Delivered-To: apmail-qpid-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 79914EFF4 for ; Thu, 31 Jan 2013 15:34:46 +0000 (UTC) Received: (qmail 53501 invoked by uid 500); 31 Jan 2013 15:34:46 -0000 Delivered-To: apmail-qpid-commits-archive@qpid.apache.org Received: (qmail 53398 invoked by uid 500); 31 Jan 2013 15:34:46 -0000 Mailing-List: contact commits-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@qpid.apache.org Delivered-To: mailing list commits@qpid.apache.org Received: (qmail 53380 invoked by uid 99); 31 Jan 2013 15:34:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jan 2013 15:34:45 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 31 Jan 2013 15:34:41 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id E8CB62388978; Thu, 31 Jan 2013 15:34:06 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: svn commit: r1441019 [4/6] - in /qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book: html/ pdf/ Date: Thu, 31 Jan 2013 15:32:51 -0000 To: commits@qpid.apache.org From: aconway@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20130131153406.E8CB62388978@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Modified: qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Broker_Federation.html URL: http://svn.apache.org/viewvc/qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Broker_Federation.html?rev=1441019&r1=1441018&r2=1441019&view=diff ============================================================================== --- qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Broker_Federation.html (original) +++ qpid/site/docs/books/trunk/AMQP-Messaging-Broker-CPP-Book/html/chap-Messaging_User_Guide-Broker_Federation.html Thu Jan 31 15:32:50 2013 @@ -1,40 +1,40 @@ -1.4. Broker Federation

Apache Qpid

Documentation

Community

Developers

About AMQP

About Apache

AMQP Messaging Broker (Implemented in C++) > +1.4. Broker Federation

Apache Qpid

Documentation

Community

Developers

About AMQP

About Apache

AMQP Messaging Broker (Implemented in C++) > Running the AMQP Messaging Broker - > Broker Federation

1.4. Broker Federation

+ > Broker Federation

1.4. Broker Federation

Broker Federation allows messaging networks to be defined by creating message routes, in which messages in one broker (the source broker) are automatically routed to another broker (the destination broker). These routes may be defined between exchanges in the two brokers (the source exchange and the destination exchange), or from a queue in the source broker (the source queue) to an exchange in the destination broker. Message routes are unidirectional; when bidirectional flow is needed, one route is created in each direction. Routes can be durable or transient. A durable route survives broker restarts, restoring a route as soon as both the source broker and the destination are available. If the connection to a destination is lost, messages associated with a durable route continue to accu mulate on the source, so they can be retrieved when the connection is reestablished.

Broker Federation can be used to build large messaging networks, with many brokers, one route at a time. If network connectivity permits, an entire distributed messaging network can be configured from a single location. The rules used for routing can be changed dynamically as servers change, responsibilities change, at different times of day, or to reflect other changing conditions.

Broker Federation is useful in a wide variety of scenarios. Some of these have to do with functional organization; for instance, brokers may be organized by geography, service type, or priority. Here are some use cases for federation: -

  • +

    • Geography: Customer requests may be routed to a processing location close to the customer. -

    • +

    • Service Type: High value customers may be routed to more responsive servers. -

    • +

    • Load balancing: Routing among brokers may be changed dynamically to account for changes in actual or anticipated load. -

    • +

    • High Availability: Routing may be changed to a new broker if an existing broker becomes unavailable. -

    • +

    • WAN Connectivity: Federated routes may connect disparate locations across a wide area network, while clients connect to brokers on their own local area network. Each broker can provide persistent queues that can hold messages even if there are gaps in WAN connectivity. -

    • +

    • Functional Organization: The flow of messages among software subsystems can be configured to mirror the logical structure of a distributed application. -

    • +

    • Replicated Exchanges: High-function exchanges like the XML exchange can be replicated to scale performance. -

    • +

    • Interdepartmental Workflow: The flow of messages among brokers can be configured to mirror interdepartmental workflow at an organization.

    -

    1.4.1. Message Routes

    +

    1.4.1. Message Routes

    Broker Federation is done by creating message routes. The destination for a route is always an exchange on the destination broker. By default, a message route is created by configuring the destination broker, which then contacts the source broker to subscribe to the source queue. This is called a pull route. It is also possible to create a route by configuring the source broker, which then contacts the destination broker in order to send messages. This is called a push route, and is particularly useful when the destination broker may not be available at the time the messaging route is configured, or when a large number of routes are created with the same destination exchange.

    The source for a route can be either an exchange or a queue on the source broker. If a route is between two exchanges, the routing criteria can be given explicitly, or the bindings of the destination exchange can be used to determine the routing criteria. To support this functionality, there are three kinds of message routes: queue routes, exchange routes, and dynamic exchange routes. -

    1.4.1.1. Queue Routes

    +

    1.4.1.1. Queue Routes

    Queue Routes route all messages from a source queue to a destination exchange. If message acknowledgement is enabled, messages are removed from the queue when they have been received by the destination exchange; if message acknowledgement is off, messages are removed from the queue when sent. -

    1.4.1.2. Exchange Routes

    +

    1.4.1.2. Exchange Routes

    Exchange routes route messages from a source exchange to a destination exchange, using a binding key (which is optional for a fanout exchange).

    Internally, creating an exchange route creates a private queue (auto-delete, exclusive) on the source broker to hold messages that are to be routed to the destination broker, binds this private queue to the source broker exchange, and subscribes the destination broker to the queue. -

    1.4.1.3. Dynamic Exchange Routes

    +

    1.4.1.3. Dynamic Exchange Routes

    Dynamic exchange routes allow a client to create bindings to an exchange on one broker, and receive messages that satisfy the conditions of these bindings not only from the exchange to which the client created the binding, but also from other exchanges that are connected to it using dynamic exchange routes. If the client modifies the bindings for a given exchange, they are also modified for dynamic exchange routes associated with that exchange.

    Dynamic exchange routes apply all the bindings of a destination exchange to a source exchange, so that any message that would match one of these bindings is routed to the destination exchange. If bindings are added or removed from the destination exchange, these changes are reflected in the dynamic exchange route -- when the destination broker creates a binding with a given binding key, this is reflected in the route, and when the destination broker drops a binding with a binding key, the route no longer incurs the overhead of transferring messages that match the binding key among brokers. If two exchanges have dynamic exchange routes to each other, then all bindings in each exchange are reflected in the dynamic exchange route of the other. In a dynamic exchange route, the source and destination exchanges must have the same exchange type, and they must have the same name; for instance, if the source exchange is a direct exchange, the destinatio n exchange must also be a direct exchange, and the names must match. @@ -42,17 +42,17 @@ Internally, dynamic exchange routes are implemented in the same way as exchange routes, except that the bindings used to implement dynamic exchange routes are modified if the bindings in the destination exchange change.

    A dynamic exchange route is always a pull route. It can never be a push route. -

    1.4.2. Federation Topologies

    +

    1.4.2. Federation Topologies

    A federated network is generally a tree, star, or line, using bidirectional links (implemented as a pair of unidirectional links) between any two brokers. A ring topology is also possible, if only unidirectional links are used.

    Every message transfer takes time. For better performance, you should minimize the number of brokers between the message origin and final destination. In most cases, tree or star topologies do this best.

    For any pair of nodes A,B in a federated network, there should be only one path from A to B. If there is more than one path, message loops can cause duplicate message transmission and flood the federated network. The topologies discussed above do not have message loops. A ring topology with bidirectional links is one example of a topology that does cause this problem, because a given broker can receive the same message from two different brokers. Mesh topologies can also cause this problem. -

    1.4.3. Federation among High Availability Message Clusters

    +

    1.4.3. Federation among High Availability Message Clusters

    Federation is generally used together with High Availability Message Clusters, using clusters to provide high availability on each LAN, and federation to route messages among the clusters. Because message state is replicated within a cluster, it makes little sense to define message routes between brokers in the same cluster.

    To create a message route between two clusters, simply create a route between any one broker in the first cluster and any one broker in the second cluster. Each broker in a given cluster can use message routes defined for another broker in the same cluster. If the broker for which a message route is defined should fail, another broker in the same cluster can restore the message route. -

    1.4.4. The qpid-route Utility

    +

    1.4.4. The qpid-route Utility

    qpid-route is a command line utility used to configure federated networks of brokers and to view the status and topology of networks. It can be used to configure routes among any brokers that qpid-route can connect to.

    The syntax of qpid-route is as follows: @@ -80,7 +80,7 @@ qpid-route [OPTIONS] list connections [& The following are all valid examples of the above syntax: localhost, 10.1.1.7:10000, broker-host:10000, guest/guest@localhost.

    These are the options for qpid-route: -

    Table 1.2. qpid-route options

    +

    Table 1.2. qpid-route options

    -v Verbose output. @@ -108,15 +108,15 @@ qpid-route [OPTIONS] list connections [& -t <transport> [ --transport <transport>] Transport protocol to be used for the route. -

    • +

      • tcp (default) -

      • +

      • ssl -

      • +

      • rdma

      -

    1.4.4.1. Creating and Deleting Queue Routes

    +


    1.4.4.1. Creating and Deleting Queue Routes

    The syntax for creating and deleting queue routes is as follows: 

     qpid-route [OPTIONS] queue add <dest-broker> <src-broker> <dest-exchange> <src-queue>
@@ -133,7 +133,7 @@ $ qpid-route -d queue add localhost:1000
 				The del command takes the same arguments as the add command. The following command deletes the queue route described above:
 			
     $ qpid-route queue del localhost:10001 localhost:10002 amq.fanout public
-

    1.4.4.2. Creating and Deleting Exchange Routes

    +

    1.4.4.2. Creating and Deleting Exchange Routes

    The syntax for creating and deleting exchange routes is as follows: 

     qpid-route [OPTIONS] route add <dest-broker> <src-broker> <exchange> <routing-key> 
@@ -155,7 +155,7 @@ $ qpid-route -d route add localhost:1000
 				The del command takes the same arguments as the add command. The following command deletes the first exchange route described above:
 			
     $ qpid-route route del localhost:10001 localhost:10002 amq.topic global.#
-

    1.4.4.3. Deleting all routes for a broker

    +

    1.4.4.3. Deleting all routes for a broker

    Use the flush command to delete all routes for a given broker: 

     qpid-route [OPTIONS] flush [<broker>]
@@ -163,7 +163,7 @@ qpid-route [OPTIONS] flush [<broker&g
 				For instance, the following command deletes all routes for the broker localhost:10001:
 			
     $ qpid-route flush localhost:10001
-

    1.4.4.4. Creating and Deleting Dynamic Exchange Routes

    +

    1.4.4.4. Creating and Deleting Dynamic Exchange Routes

    The syntax for creating and deleting dynamic exchange routes is as follows: 

     qpid-route [OPTIONS] dynamic add <dest-broker> <src-broker> <exchange> 
@@ -195,7 +195,7 @@ $ qpid-route -d dynamic add localhost:10
 $ qpid-route dynamic del localhost:10004 localhost:10003 fed.topic

    Internally, this deletes the bindings on the source exchange for the the private queues associated with the message route. -

    1.4.4.5. Viewing Routes

    +

    1.4.4.5. Viewing Routes

    The route list command shows the routes associated with an individual broker. For instance, suppose we have created the following two routes: 

     $ qpid-route dynamic add localhost:10003 localhost:10004 fed.topic
@@ -277,7 +277,7 @@ Dynamic Routes:
 
 Static Routes:
   none found
-

    1.4.4.6. Resilient Connections

    +

    1.4.4.6. Resilient Connections

    When a broker route is created, or when a durable broker route is restored after broker restart, a connection is created between the source broker and the destination broker. The connections used between brokers are called resilient connections; if the connection fails due to a communication error, it attempts to reconnect. The retry interval begins at 2 seconds and, as more attempts are made, grows to 64 seconds, and continues to retry every 64 seconds thereafter. If the connection fails due to an authentication problem, it will not continue to retry.

    The command list connections can be used to show the resilient connections for a broker: --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscribe@qpid.apache.org For additional commands, e-mail: commits-help@qpid.apache.org