Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1565394 - ElasticSearch pods are not failure domain aware
Summary: ElasticSearch pods are not failure domain aware
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: RFE
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: 3.10.0
Assignee: Paul Weil
QA Contact: Xiaoli Tian
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-04-10 00:19 UTC by raffaele spazzoli
Modified: 2019-06-12 11:57 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-12 11:57:26 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description raffaele spazzoli 2018-04-10 00:19:33 UTC
Description of problem:
when installing logging in a cluster that has failure domains, the ElasticSearch pods should be failure domain aware and distributing themselves across those domains.

The conventional label that identifies the failure domains are:
failure-domain.beta.kubernetes.io/region=us-central1,failure-domain.beta.kubernetes.io/zone=us-central1-a

These labels are set automatically when running in a cloud environment, but can be manually set also for on premise deployments.


Version-Release number of selected component (if applicable):
logging-elasticsearch:v3.9.14


How reproducible:
100%


Steps to Reproduce:
1. deploy a elasticsearch cluster in a multi-AZ OCP cluster 



Actual results:

the multiple elasticsearch rc ignore the failure domain.
They may actually accidentally distribute themselves correctly, but there is no directive for creating an anti affinity behavior based on the failure domain.



Additional info:
If stateful set was used to deploy the elasticsearch cluster this behavior would be easier to configure.

Comment 2 Kirsten Newcomer 2019-06-12 11:57:26 UTC
With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers.  Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant.

This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. 

If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new 

Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new 

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.


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