Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specifying more than 3 nodes on Cluster Logging CR creates invalid Elasticsearch CR #14795

Merged
merged 1 commit into from
May 13, 2019

Conversation

mburke5678
Copy link
Contributor

@mburke5678 mburke5678 added this to the Future Release milestone May 9, 2019
@openshift-ci-robot openshift-ci-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label May 9, 2019
<4> Settings for configuring Kibana. Using the CR, you can scale Kibana for redundancy and configure the CPU and memory for your Kibana nodes. For more information, see *Configuring Kibana*.
<5> Settings for configuring Curator. Using the CR, you can set the Curator schedule. For more information, see *Configuring Curator*.
<6> Settings for configuring Fluentd. Using the CR, you can configure Fluentd CPU and memory limits. For more information, see *Configuring Fluentd*.
<4> 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.
Copy link

@anpingli anpingli May 10, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The nodeCount can >3 now. The maximum Elasticsearch master nodes(pods) number is 3. That means: when the size >3, 3 elasticsearch nodes(pods) are created as Master-eligible node (using roles: master,client,data) , the other ES nodes(pods) will be created as Data only node ( using roles: client,data).
Refer to https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-node.html

For example: when nodeCount=4,

[anli@preserve-anli-slave 41]$oc get elasticsearch -o yaml
<---snip--->
nodes:
- genUUID: x6kdekli
  nodeCount: 1
  resources: {}
  roles:
  - client
  - data
  storage: {}
- genUUID: x6kdekli
  nodeCount: 3
  resources: {}
  roles:
  - client
  - data
  - master
  storage: {}
redundancyPolicy: ZeroRedundancy
<---snip--->
[anli@preserve-anli-slave 41]$ oc get deployment
cluster-logging-operator       1/1     1            1           18h
elasticsearch-cd-x6kdekli-1    0/1     1            0           6m54s
elasticsearch-cdm-x6kdekli-1   1/1     1            1           18h
elasticsearch-cdm-x6kdekli-2   0/1     1            0           6m49s
elasticsearch-cdm-x6kdekli-3   0/1     1            0           6m44s

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@anpingli Thank you. I misread the BZ. How is this:

The maximum number of Elasticsearch master nodes is three. If you specify a nodeCount greater than 3, {product-title} creates three Elasticsearch nodes that are Master-eligible nodes, with the master, client, and data roles. The additional Elasticsearch nodes are created as Data only node, using client and data roles. Master nodes perform cluster-wide actions such as creating or deleting an index, shard allocation, and tracking nodes. Data nodes hold the shards and perform data-related operations such as CRUD, search, and aggregations. Data-related operations are I/O-, memory-, and CPU-intensive. It is important to monitor these resources and to add more Data nodes if the current nodes are overloaded.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@openshift-ci-robot openshift-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels May 10, 2019
@mburke5678
Copy link
Contributor Author

/ok-to-test

@openshift-ci-robot openshift-ci-robot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label May 10, 2019
@mburke5678 mburke5678 removed the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label May 13, 2019
@mburke5678 mburke5678 merged commit 206f5bf into openshift:enterprise-4.1 May 13, 2019
@mburke5678 mburke5678 deleted the BZ-1706134 branch May 13, 2019 13:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-4.1 size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants