Bug 1472096 - [RFE] zone anti affinity for MongoDB replica sets
[RFE] zone anti affinity for MongoDB replica sets
Status: NEW
Product: Red Hat Software Collections
Classification: Red Hat
Component: rh-mongodb34-docker (Show other bugs)
rh-mongodb34
Unspecified Unspecified
medium Severity medium
: ---
: 3.1
Assigned To: Marek Skalický
Lukas Zachar
Lenka Spackova
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-18 01:45 EDT by Jaspreet Kaur
Modified: 2017-08-08 12:07 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jaspreet Kaur 2017-07-18 01:45:21 EDT
1. Proposed title of this feature request

 zone anti affinity for MongoDB replica sets


3. What is the nature and description of the request?

This request is for extending the provided template to take this into account. 
 https://docs.openshift.com/container-platform/3.5/using_images/db_images/mongodb.html#creating-the-final-replication-set
mentions that (in tech preview) we can create a replica set.
It seems to us that this approach is ignoring an important aspect of reality


 4. Why does the customer need this? (List the business requirements here)

 In most multi data center environments, replica sets should be provisioned to a 2nd/3rd DC site / Availability Zone (to compensate for the loss of an AZ).
Comment 2 Ben Parees 2017-07-18 12:45:11 EDT
Fixing this entails making a change to the mongo templates that reside here:
https://github.com/openshift/origin/tree/master/examples/db-templates

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