Adjust Elasticsearch cluster setup #3
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
This adds a number of configuration settings to all Elasticsearch containers, for example rack awareness and a few node properties useful in a hot / warm architecture. * re-enable elasticsearch02 and elasticsearch03 containers * set `path.repo` to a shared volume for snapshots * add rack awareness properties
This is not supported by the used Elasticsearch versions yet.
These Curation action files can be used to demonstrate a number of index management tasks, e.g. delete indices, take snapshots, index rollover etc. * change Dockerfile to install config files
This moves some of the configuration settings into the `elasticsearch.yml` file. * set node attributes for rack awareness * disable nodes 02 and 03 not to be master
* set `discovery.seed_hosts` in containers `elasticsearch02` and `elasticsearch03`
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.
This adjusts the Elasticsearch cluster to only have a single
master-eligiblenode (for now). The main reason is most examples / exercises only require a single node running, a few require all three nodes. If all nodes aremaster-eligiblethe minimum master nodes setting is increased from1to2. Starting a single node cluster again does not boot correctly afterwards, because the cluster assumes then a minimum of 2 nodes. To avoid this issue for now and allow both setups to run both containerselasticsearch02andelasticsearch03are notmaster-eligible.Another way to solve this would to delete all mounted data folders from these containers in order to remove this information, but this seems a bit more destructive then necessary for any presentation.
Dockerfilesettings to assign roles, master nodes and seeds correctlyelasticsearch02andelasticsearch03indocker-compose.ymlDockerfileto build correctlycuratorcontainerpath.reposetting to all Elasticsearch containers, it's a shared mounted folder for backups