Hide Forgot
Description of problem: Currently, if you specify more than three nodes for the Cluster Logging Operator to create/manage it creates an Elasticsearch CR with a data master client node of X replicas. In the Elasticsearch Operator any configuration with more than three (3) master nodes is considered invalid and will not create any nodes. Version-Release number of selected component (if applicable): 4.1.0 How reproducible: Always Steps to Reproduce: 1. With Logging operators installed -- create an ClusterLogging CR with more than 3 nodes of type Elasticsearch (Logstore spec) 2. Observe no Elasticsearch nodes created and condition in Elasticsearch CR stating that it is invalid. Actual results: Condition in Elasticsearch CR status that the configuration is invalid for more than 3 masters. No Elasticsearch nodes are created. Expected results: A configuration is provided that allows for X data nodes to be created. Additional info:
https://github.com/openshift/cluster-logging-operator/pull/168
https://github.com/openshift/cluster-logging-operator/pull/170
Verified with openshift/ose-cluster-logging-operator:v4.1.0-201905071513
@Michael, The document should be updated accordingly.
Eric and Anping -- Is it the Elasticsearch Operator that must be 1 or 3 nodes? I seem to recall that requirement somewhere.
PR: https://github.com/openshift/openshift-docs/pull/14795 Added: Specify `1` or `3` Elasticsearch nodes. Any configuration with more than three Elasticsearch nodes is considered invalid and no nodes are created.
Michael, I believe you're thinking of the number of master nodes that there should be in the cluster for a quorum. The elasticsearch operator handles that
Changed to "Specify the number of Elasticsearch nodes, maximum of `3`. Any configuration with more than three Elasticsearch nodes is considered invalid and no nodes are created."
@Michael that is incorrect though, this bug resolved that.