fix: SearchEngine
had num index == num replicas
#3736
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When the instance of
SearchEngine
was created we were passing the value of the attributesettings.es_records_index_shards
to bothes_number_of_shards
andes_number_of_replicas
arguments. This PR fix that and now value of attributesettings.es_records_index_shards
is passed toes_number_of_replicas
argument.Type of change
How Has This Been Tested
In a local development environment:
GET localhost:9200/_cat/shards?v
, two shards are listed for the dataset (one primary started and one replica unassigned)GET localhost:9200/_cat/shards?v
, only one primary shard is listed for the datasetChecklist
CHANGELOG.md
file (See https://keepachangelog.com/)