Bug 1042887 - 5.8.4. Configuring Redundancy
Summary: 5.8.4. Configuring Redundancy
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Documentation
Version: 2.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Bilhar
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-13 14:56 UTC by Luke Meyer
Modified: 2017-03-08 17:35 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-09 01:04:02 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Luke Meyer 2013-12-13 14:56:51 UTC
https://access.redhat.com/site/documentation/en-US/OpenShift_Enterprise/2/html-single/Deployment_Guide/index.html#sect-Configuring_Redundancy
5.8.4. Configuring Redundancy
---
Alternatively, consider the following options to configure redundancy:
[...]
Install broker on its own host, and combine broker, ActiveMQ, MongoDB, and name server on a single host
==> This doesn't really make sense. Not quite sure what it was meant to be. I suggest the following replacement:
Here are some redundant topologies to consider:
[...]
Install broker and MongoDB together on multiple hosts and ActiveMQ separately on multiple hosts.
===


Note You need to log in before you can comment on or make changes to this bug.