NETWAYS / NETWAYS/ansible-collection-elasticstack
Elasticsearch 7 can't work without initial_master_nodes
Nobody has claimed this yet.
- Dominant language
- Jinja
- Stars
- 14
- Forks
- 11
- Avg merge
- 1d 47m
- Merged PRs (30d)
- 6
Description
The check in https://github.com/NETWAYS/ansible-collection-elasticstack/blob/main/roles/elasticsearch/templates/elasticsearch.yml.j2#L31 is wrong at least for Elasticsearch 7. Even a single node cluster needs this to be set.
If I remember correctly, we had to remove it on Elasticsearch 8 single node clusters to not get error messages. So either we live with the message or we introduce yet another check and set it always on 7 and only on multinode cluster on 8.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in roles/elasticsearch/templates/elasticsearch.yml.j2 around line 31 and inspect how the current check handles Elasticsearch 7 and 8, single-node and multinode clusters. Compare the reported startup behavior for those combinations and confirm the desired configuration for each version. Done means the template no longer prevents a valid Elasticsearch 7 single-node cluster from starting while preserving the Elasticsearch 8 behavior described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, elasticsearch
- Domain
- infrastructure, search
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100