-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Do not use auto_expand_replicas #3580
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,9 +6,8 @@ script: | |
indexed: on | ||
|
||
index: | ||
number_of_shards: 1 | ||
number_of_replicas: 0 | ||
auto_expand_replicas: 0-2 | ||
number_of_shards: {{ es_number_of_shards | default ('1') }} | ||
number_of_replicas: {{ es_number_of_replicas | default ('0') }} | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. not exactly sure why, but because of the way we use this template, the values have to be quoted. Please change this to be:
You'll have to submit a new PR since this one was merged. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. |
||
unassigned.node_left.delayed_timeout: 2m | ||
translog: | ||
flush_threshold_size: 256mb | ||
|
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.
Should this be
openshift_logging_es_recover_after_time
? Or should that beopenshift_logging_es_ops_recover_after_time
?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.
@portante It can make sense, I will look at this tomorrow.
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.
@portante I think it is correct.
There is
{{openshift_logging_es_recover_after_time}}
value set to${RECOVER_AFTER_TIME}
env variable inroles/openshift_logging/templates/es.j2
which is then used inelasticsearch.yml.j2
template.//cc @ewolinetz (Erik see below please)
However, I do not understand why this value is set only for DeploymentConfig for Ops in
tasks/install_elasticsearch.yaml
script. Please comparevars
sections for Ops vsvars
section for Non-Ops.Why the following four
vars
are set only for Ops DeploymentConfig?es_node_quorum
es_recover_after_nodes
es_recover_expected_nodes
openshift_logging_es_recover_after_time
Apart from this if there is any issue with
openshift_logging_es_recover_after_time
usage and configuration then I suggest to address it in separated ticket/PR.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.
Per my IRC comment, the difference is when running the 'ops' tasks, we update the variables to be the 'ops' variables. Technically, we should have written these tasks to run twice with a single set of tasks: once with non-ops and the other with ops. The four variables in question are found in the vars/main.yaml