Bug 677656

Summary: Replication behaves as a load balancer when more than one destination brokers are configured
Product: Red Hat Enterprise MRG Reporter: Petr Matousek <pematous>
Component: Messaging_Programming_ReferenceAssignee: Alison Young <alyoung>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: unspecified Docs Contact:
Priority: low    
Version: 1.3CC: jneedle, sburgess
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-24 02:55:41 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 660526    
Bug Blocks: 660531    

Description Petr Matousek 2011-02-15 14:02:11 UTC 
Description of problem:
Chapter 9. - Replicated Queues

When using replication with more than one backup broker configured for one replicated queue, the replication mechanism behaves as load balancer.
Documentation does not reflect this behaviour.
  
Example:
one replicated queue created on the source broker
one backup queue created on destination broker1
one backup queue created on destination broker2

sending 10 messages to replicated queue on the source broker results in:
even messages are received by the backup queue on the destination broker1 (msg0,2,4,6,8)
odd messages are received by the backup queue on the destination broker2 (msg1,3,5,7,9)

Version-Release number of selected component (if applicable):
Red Hat Enterprise MRG 1.3 - Messaging User Guide
Revision 3-0

How reproducible:
n/a

Steps to Reproduce:
n/a
  
Actual results:
Documentation does not mention that the replication mechanism acts as a load balancer when more than one destination broker is configured 

Expected results:
Documentation describes that the replication mechanism acts as a load balancer when more than one destination broker is configured 

Additional info:
n/a
Comment 3 Petr Matousek 2011-06-08 13:20:37 UTC 
This issue has been fixed.

Messaging User Guide - Revision 0.1-8

-> VERIFIED