Add Elasticsearch settings #36
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
These were buried in pelias/schema (https://github.com/pelias/schema/blob/f28002db187f1685abc3688b141e0bfdd5cdd01a/settings.js#L289-L296), so by moving them here it's more obvious they can be overridden. We use 1 shard as a default in development where scalability isn't required. Also, because we use the [dfs_query_then_fetch](https://www.elastic.co/guide/en/elasticsearch/reference/current/search-request-search-type.html#dfs-query-then-fetch) search mode, having one shard eliminates any possibility of queries run _without_ that setting having confusing results due to TF/IDF The `index_concurrency` setting is set to 10 as an attempt to increase indexing performance as well. Reference: https://github.com/pelias/api/blob/9ff383cc2b4a690fa05a88e70c598bfdc28751f4/controller/search.js#L44 https://www.elastic.co/guide/en/elasticsearch/guide/current/relevance-is-broken.html Connects pelias/schema#178
This default was buried in our private chef configuration. Because Pelias is generally run with a bulk indexin phase before any queries are run, a higher refresh interval makes sense to improve indexing performance. Reference links: https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-update-settings.html#bulk https://sematext.com/blog/2013/07/08/elasticsearch-refresh-interval-vs-indexing-performance/
trescube
approved these changes
Oct 17, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
These were buried in pelias/schema and will be removed in another PR.
Note that both commits have nice big friendly commit messages with information about these settings. Because JSON doesn't have any support for comments, hopefully people will look at
git blamewhen trying to find information on these settings, so I tried to include as much as possible.Connects pelias/schema#178