-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Conversation
<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. |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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 than3
, {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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/ok-to-test |
https://bugzilla.redhat.com/show_bug.cgi?id=1706134